Report 1647 Actions
Problem Report Number |
1647 |
Submitter's Classification |
Specification problem |
State |
Resolved |
Resolution |
Permanent Interpretation (PIN) |
Problem Resolution ID |
PIN.X.0204 |
Raised |
2002-05-23 08:00 |
Updated |
2003-03-13 08:00 |
Published |
2002-06-20 08:00 |
Product Standard |
OTHER including specifications not referenced in a Product Standard |
Certification Program |
The Open Brand certification program |
Test Suite |
Unknown version N/A |
Test Identification |
N/A |
Specification |
N/A (use location field) |
Location in Spec |
See Problem Text |
Problem Summary |
PIN4U.00070 Grey area in the XNS5.2 specification wrt type of getnameinfo() flags argument |
Problem Text |
CAE specification:
C808 Networking Services (XNS) Issue 5.2
Request Summary:
The data type of the flags argument of the getnameinfo() function should be 'int'. The data type is currently specified as 'unsigned int'.
Supporting Information:
The getnameinfo() function was originally specified by the IETF IPv6 working group in RFC 2133 (April 1997) and RFC 2553 (March 1999). Both of these RFCs specified the data type of the flags argument of the getnameinfo() function to be 'int'.
Although these IETF documents are informational only, they were the basis for most implementations of the getnameinfo() function. The following implementations use type 'int' for the flags argument of getnameinfo():
Solaris 9 Solaris 8 IBM AIX HP-UX Windows XP FreeBSD OpenBSD NetBSD Tru64 UNIX OpenVMS
Type 'int' is also documented in the book "UNIX Network Programming", Volume 1, second edition, 1998, by W. Richard Stevens.
When the getnameinfo() function was incorporated into the Networking Services (XNS) Issue 5.2 (January 2000) specification, the data type of the flags argument of the getnameinfo() function was changed to be 'unsigned int'. We believe this was an oversight, and that the XNS 5.2 specification should be modified to specify the data type to be 'int'.
Requested Changes:
On page 89 getnameinfo() in the SYNOPSIS section, change "unsigned int flags" to "int flags".
On page 100 <netdb.h> in the prototype for the getnameinfo() function, change "unsigned int" to "int". Note: the prototype for getnameinfo() was added by Corrigendum U050.
|
Test Output |
n/a
|
Review Information
Review Type |
TSMA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Recommendation |
No Resolution Given |
Review Response |
This matter should be referred to the Base Working Group for consideration. .br The interface definition is the same in the Base Specifications Issue 6, which have been approved as an Open Group technical standard and IEEE Std. .br Procedurally an interpretation can widen the allowed behavior allowed for conformance but cannot prohibit systems that have implemented the published definition. .br The Base Working Group should assess the impact on application portability of allowing behavior other than as stated in the specification.
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
This matter is forwarded to the Base Working Group for consideration
|
Review Type |
Expert Group Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
Base WG response:
The group recommends in a future revision the following changes to XNS 5.2:
On page 89 getnameinfo() in the SYNOPSIS section, change "unsigned int flags" to "int flags".
On page 100 <netdb.h> in the prototype for the getnameinfo() function, change "unsigned int" to "int". Note: the prototype for getnameinfo() was added by Corrigendum U050.
For this revision of the specification either behavior is acceptable.
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
Permanent Interpretation (PIN) |
Review Conclusion |
A Permanent Interpretation is granted.
|
Problem Reporting System Options:
|