Minutes of the 29 August 2012 Teleconference Austin-576 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 30 August, 2012 Attendees Mark Brown, IBM, TOG OR Don Cragun, PASC OR Andrew Josey, The Open Group Jim Pugsley, Oracle Geoff Clare, The Open Group Apologies Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat Joerg Schilling, Fraunhofer Society * General News The IEEE recirculation ballot has just started, lasts for 10 days and will close on September 7. Balloters need only ballot if they wish to change their current vote. The Open Group ballot closes on August 31st. Action: Andrew to remind The Open Group balloters to vote, and also to make available the recirculation draft to them. (Closed, completed after the meeting) For ISO balloting, we need to ensure that the project editor response to the comments from the ISO ballot detail the final set of changes post the ballot. * Old Business +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +mbsnrtowcs() discussion OPEN Nick filed a defect report in Mantis during the meeting. http://austingroupbugs.net/view.php?id=601 +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 This item needs further investigation of existing implementations. Mark reported that AIX does not have a problem with this. Jim notes he is still looking at this. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. Bug 0000576: No format specifiers for several types OPEN http://austingroupbugs.net/view.php?id=576 Bug 0000599: Reserved "no thread" value for pthread_t A/M Issue 8 * Current Business Bug 0000509: make's INPUT FILES section not updated when include lines were added Accepted http://austingroupbugs.net/view.php?id=509 This item is marked for TC2-2008. Action: Andrew to close out intepretations that completed their review on August 16, and start the next batch of intepretations for review. CLOSED - completed after the meeting. Bug 0000599: Reserved "no thread" value for pthread_t Accepted as Marked http://austingroupbugs.net/view.php?id=599 This item is tagged for Issue 8 After line 10403 on page 311 of Issue 7 append: The header shall define the following compile-time constant expression, valid as an initializer for pthread_t, representing a value that shall not compare equal to the thread ID of any existing thread: PTHREAD_NULL On page 314 line 10548 replace "None." with: Since pthread_t is an opaque type, a definition of PTHREAD_NULL was added to allow for a null value of that type. Some conforming definitions of PTHREAD_NULL could be: For a pointer type: #define PTHREAD_NULL ((pthread_t)NULL) For an integer type: #define PTHREAD_NULL ((pthread_t)-42) For a struct type: #define PTHREAD_NULL ((const pthread_t){ .foo = -1 }) On line 51624 on page 1606 of Issue 7 replace: If either t1 or t2 are not valid thread IDs, the behavior is undefined. with If either t1 or t2 is not a valid thread ID and is not equal to PTHREAD_NULL, the behavior is undefined. Bug 0000565: Please standartize netcat Rejected http://austingroupbugs.net/view.php?id=565 (Don took an action to write up the bug after the meeting as a rejection - CLOSED - completed after meeting) Several criteria must be met before a new feature can be added to the standard. These include, but might not be limited to: 1. one of the three member organizations of The Austin Group (The Open Group, IEEE PASC, and ISO/IEC JTC1/SC22) must sponsor the addition, 2. the feature must have already been implemented, 3. the feature must fit into the scope of the standard, 4. copyright release for documentation of the feature to The Austin Group's member organizations must be available, 5. the feature to be added must not be controversial (i.e., likely to generate negative votes when trying to ballot a draft of the standard that contains the new feature), and 6. must include documentation giving explicit editing instructions describing all of the changes that would need to be made to the current standard to add the new feature. Since there are multiple, incompatible versions of netcat, any proposal adding netcat would have to either just standardize the common subset of netcat features that are supported by all current versions of netcat or you would need to get the current maintainers of the various versons of netcat to agree to a new common set of options, implement that new utility, and document it. The proposal as presented in this bug report implies that a new utility should be created with features from various existing implementations of netcat. If this implication is true, there is no existing implementation of the netcat that you want to appear in the standard. The proposal given in this bug report doesn't even come close to specifying text changes needed to add this utility to the standard. Since netcat is most frequently used when debugging system or network administration problems (and system administration is out of scope for this standard), it does not appear that this request meets point 3 above. Since netcat has been used to hack into systems, there are concerns that making this available on all standards conforming implementations could create a security hole. Whether this is true or not, it is likely raise objections to including netcat into a revision of the standard. For all of the reasons above, this request is being rejected. Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 This bug was filed against onlinepubs and has been moved to Issue 7. It was agreed that we need Joerg's input on this item and have left it open for now. Next Steps ---------- There are some homework items that need completing before the next call so that is pushed out to two weeks time. The next call is on September 12. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.org/austingroupbugs