Minutes of the 20th July 2017 Teleconference Austin-829 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 22nd July 2017 Attendees: Mark Ziegast, SHware Systems Joerg Schilling, FOKUS Fraunhofer Don Cragun, IEEE PASC OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Richard Hansen, Google David Clissold, IBM Eric Blake, Red Hat Apologies: Martin Rehak, Oracle, The Open Group OR Andrew Josey, The Open Group * General news Draft 1 has completed its IEEE MEC review, and we should be able to open the ballot after the ballot invitation period closes (on July 23rd). We noted that Mantis had been down for maintenance and that Mark B expects further maintenance will be needed. * Outstanding actions ( Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 28 Jan 2016) Bug 0000249: Add standard support for $'...' in shell Reopened http://austingroupbugs.net/bug_view_page.php?bug_id=249 We will return to bug 249 on a future call. Bug 0000953: Alias expansion is under-specified Was Accepted as Marked http://austingroupbugs.net/view.php?id=953 Richard has an action to propose new wording to discuss in a future telecon. * Current Business Bug 1056: CMSG_NXTHDR(): under what criteria may NULL be returned? Accepted as Marked http://austingroupbugs.net/bug_view_page.php?bug_id=1056 Suggested changes that would explicitly allow either behaviour and also add the RFC 2292 feature where CMSG_NXTHDR(mhdr, NULL) is equivalent to CMSG_FIRSTHDR(mhdr). All page and line numbers are for the 2016 edition. On page xlvii of the frontmatter, add a new second paragraph (after RFC 2181): IETF RFC 2292 Advanced Sockets API for IPv6, W. Stevens, M. Thomas, February 1998 (available at: www.ietf.org/rfc/rfc2292.txt). On page 387 line 13153 section change: this macro shall return a pointer to the next cmsghdr structure, or a null pointer if this structure is the last cmsghdr in the ancillary data. to: this macro shall return a pointer to the next cmsghdr structure, or a null pointer if the second argument points to the last cmsghdr and data array pair in the ancillary data. If the ancillary data contains another cmsghdr structure after this one but the cmsg_len value in that structure is such that the data array following that structure would extend beyond the end of the ancilliary data, it is unspecified whether this macro returns a pointer to that cmsghdr structure or returns a null pointer. If the first argument is a pointer to a msghdr structure and the second argument is a null pointer, this macro shall be equivalent to CMSG_FIRSTHDR() called with the first argument. On page 387 line 13157 section change: or a null pointer if there is no ancillary data associated with the msghdr structure. to: or a null pointer if either there is no ancillary data associated with the msghdr structure (msg_controllen is zero) or there is insufficient room in the ancilliary data for a complete cmsghdr structure (msg_controllen is non-zero but less than sizeof(struct cmsghdr)). On page 390 line 13289 section add a new paragraph to APPLICATION USAGE: Portable applications need to account for the alternative behaviors of the CMSG_NXTHDR() macro as follows: When constructing ancilliary data in a msghdr structure, ensure that all locations within the ancilliary data that might be returned by CMSG_NXTHDR() contain a cmsg_len value of zero (typically this is achieved by using memset() to initialise the entire msg_control buffer to null bytes before populating the first cmsghdr structure). When extracting ancilliary data from a received msghdr structure, check that the data array following the last cmsghdr structure does not extend beyond the end of the ancilliary data. Bug 1041: Encourage implementations to include better integrity checksum, compression and decompression utilities if possible. OPEN http://austingroupbugs.net/view.php?id=1041 The bug has its own page in the etherpad: http://posix.rhansen.org:9001/p/bug1041 Discussion continued on this item. We will pick up on this next week. Bug 1053: Add a "size" mode to stty(1) OPEN http://austingroupbugs.net/view.php?id=1053 This remains open. Next Steps ---------- The next call is on July 27th, 2017 (a Thursday) We have also scheduled August 3 in advance. Apologies in advance from Andrew for the next two weeks. Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix@posix.rhansen.org/p/201x-mm-dd password=2115756#