Austin Group Minutes of the 26 May Teleconference Austin-257 Page 1 of 1 Submitted by Andrew Josey, The Open Group. May 27, 2005 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Nick Stoughton, USENIX, ISO/IEC OR Mark Brown, IBM, TOG OR Ulrich Drepper, Red Hat Apologies: Mats Wichmann We also had an IRC channel open for this call irc://irc.freestandards.org/austin Action item review --------------------- Just the updates on Austin/240r1 are noted here. ACTION AI-2005-01-09 Andrew Josey & Mats Wichmann to propose a time and place for a joint Austin group/LSB Workgroup meeting to consider LSB/POSIX conflicts, to be held as soon as conveniently possible. Status: OPEN LSB 3.0 still in 30 day review which will end on June 1st. There are still a number of issues to resolve but expect to close on time. Nick still has an action to prepare an agenda for a teleconference. ACTION AI-2005-01-06: AJ to contact Jack McCann at HP for views on getnameinfo document, and for any other networking issues that may concern us. Status: OPEN, looking for a volunteer to acts as a liaison to the networking folks at IETF Nick reported that he might have some possible candidates. Defect Report Processing ------------------------- The group picked up on the latest batch of defect reports, which are available at the following URL: http://www.opengroup.org/austin/aardvark/latest/ XSH ERN 89 setpgrp OPEN The text is straight from the SVID. We expect to deprecate the interface in the next revision and to extend the rationale (based on wording proposed -- to be completed after we close this item). Recollection is that the description was short since that was all that could be agreed to when this was brought into the standard. Andrew has the action (completed) to contact the requestor and request more information on the problem that has been encountered with the current wording. Also ask whether he believes the wording of setsid() needs to be changed. XSH ERN 91 bind Reject The reporter has found that many/most implementations do not honour SO_REUSEADDR on a unix domain socket. The standard does not address under what circumstances this should or should not occur, if this were being treated as an interpretation request then the response would be that the standard is silent on this issue and as such no conformance distinction can be made between different implementations. We realize that this may be an issue, and that the whole network interface area is probably underspecified and needs more work than just this one aardvark. So dealing with this single point would be incomplete , we need a complete proposal for dealing with address families and protocol families in sockets XSH ERN 92 SEEK_ namespace Accept as marked below There was concern about extending the namespace. It was felt that an alternative could be to use an alternative name beginning the posix_ or POSIX_ prefix.For this reason an interpretation allowing its use in the current standard would state that this was nonconforming. However it was felt that this should be considered in a future revision Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next call is Thursday June 2 2005 irc://irc.freestandards.org/austin