From sacadmin Thu Apr 8 11:43:29 2004 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 8 Apr 2004 14:37:55 -0400 From: James Carlson To: psarc@sac.sfbay.sun.com cc: Jim Paugh Subject: 2004/288 Remove Unused BIND Flags Content-Length: 3213 I'm sponsoring this fast-track case for Jim Paugh. The timer is set to 04/15/2004. (I believe this is intended for an S9 patch only and will not be delivered on S10 at all.) RELEASE BINDING: patch/micro BACKGROUND This case addresses the following bug: 5006623 BIND 8.3 broke getnameinfo() The original case was "BIND 8.3.3" (PSARC 2001/638). PROBLEM With the introduction of BIND 8.3 into Solaris 9 update 4, a flag was introduced into , NI_WITHSCOPEID. This flag is not defined in any standard and is considered experimental at this time. This flag came along with the BIND 8.3 source from ISC and was released in this header file. The problem results from applications that use this flag as an indication of support for scoped IPv6 addresses (#ifdef NI_WITHSCOPEID). If this flag is defined, an application will pass it into calls to getnameinfo(), with the expectation of a returned scoped IPv6 address on return. Sun's implementation of getnameinfo() does not support scoped addresses until S10. But as a result of this flag being released in S9U4, applications are compiling code that passes this flag into getnameinfo(). This causes an error return (EAI_BADFLAGS), from getnameinfo(). Were it not defined, application code would compile without attempting to use the flag and thus would avoid the error. As of S10, support for scoped addresses was integrated, so fixing this bug in S10 is simply a matter of including this flag in the list of valid flags for getnameinfo(). But for S9, scoped addresses are not supported, so adding it to the list of valid flags will cause a different error code to be returned (EAI_NODATA). Another flag was also released with BIND 8.3, in . The flag, NI_NUMERICSCOPE, is used to request numeric scopes from getnameinfo. This functionality was introduced in S10, but is not supported in S9. It should also be removed from in S9. SOLUTION The two flags are removed. If the flag were not defined, the code in applications would compile without attempting to use this flag. The solution to fixing this bug in the latest S9 update release will be to remove it from . There have been no reported problems with the presence of NI_NUMERICSCOPE in S9, but since there is no support for this functionality in S9, it should also be removed from . INTERFACES ____________________________________________________________________ | Interfaces Exported | |_____________________|_________________|___________________________| |Interface |Former Stability |Proposed Stability | |_____________________|_________________|___________________________| |NI_WITHSCOPEID |Project Private |Removed | |NI_NUMERICSCOPE |Project Private |Removed | |_____________________|_________________|___________________________| Note that NI_NUMERICSCOPE is part of SUSv3, but S9 does not implement that standard, and no documentation of the flag was ever given to customers. It is assumed to be an implementation artifact. From sacadmin Wed Apr 14 10:41:10 2004 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 2004 13:35:32 -0400 From: James Carlson To: psarc@sac.sfbay.sun.com cc: Jim Paugh Subject: Re: 2004/288 Remove Unused BIND Flags Content-Length: 301 This fast-track request was approved during ARC business at today's meeting. -- James Carlson, IP Systems Group Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677