View Issue Details

IDProjectCategoryView StatusLast Update
0001685Issue 8 draftsFront Matterpublic2024-06-11 09:12
Reportergeoffclare Assigned To 
PrioritynormalSeverityObjectionTypeError
Status ClosedResolutionAccepted 
Product VersionDraft 3 
NameGeoff Clare
OrganizationThe Open Group
User Reference
SectionReferenced Documents
Page Numberxxxvi-xxxvii
Line NumberN/A
Final Accepted Text
Summary0001685: RFC references need updating
DescriptionSome of the RFCs we reference have been superseded. We should change to refer to the new ones.

We list RFCs 791, 2292, and 2460 in the Referenced Documents section, but there are no references to them. I have found suitable places to reference 791 and 2460 (actually 8200 which obsoletes 2460), but I don't see the need for a reference to 2292 since it concerns the use of raw sockets over IPv6 and XSH 2.10.6 says of raw socket datagrams that "the formats are protocol-specific and implementation-defined." So application writers need to refer to an implementation's documentation to see how to use raw sockets anyway (which might well say it supports RFC 2292, but on the other hand it might not). Without an actual reference to it, 2292 should be deleted from the list (otherwise the introductory text "The following documents are referenced in POSIX.1-202x" will be untrue).

We have also added references to RFC 6557 within the text but not added it to the Referenced Documents section.
Desired ActionOn page xxxvi para 6, delete:
IETF RFC 822
Standard for the Format of ARPA Internet Text Messages, D.H. Crocker, August 1982 (available at: www.ietf.org/rfc/rfc0822.txt).
and delete the "Notes to Reviewers" below it.

On page xxxvi last para, delete:
IETF RFC 1886
DNS Extensions to Support Internet Protocol, Version 6 (IPv6), C. Huitema, S. Thomson, December 1995 (available at: www.ietf.org/rfc/rfc1886.txt).

On page xxxvii para 5-7, delete:
IETF RFC 2292
Advanced Sockets API for IPv6, W. Stevens, M. Thomas, February 1998 (available at: www.ietf.org/rfc/rfc2292.txt).
IETF RFC 2373
Internet Protocol, Version 6 (IPv6) Addressing Architecture, S. Deering, R. Hinden, July 1998 (available at: www.ietf.org/rfc/rfc2373.txt).
IETF RFC 2460
Internet Protocol, Version 6 (IPv6), S. Deering, R. Hinden, December 1998 (available at: www.ietf.org/rfc/rfc2460.txt).

On page xxxvii para 8, insert:
IETF RFC 3596
DNS Extensions to Support IP Version 6, S. Thomson, C. Huitema, V. Ksinant, M. Souissi, October 2003 (available at: www.ietf.org/rfc/rfc3596.txt).
IETF RFC 4291
IP Version 6 Addressing Architecture, R. Hinden, S. Deering, February 2006 (available at: www.ietf.org/rfc/rfc4291.txt).
IETF RFC 5322
Internet Message Format, P. Resnick, October 2008 (available at: www.ietf.org/rfc/rfc5322.txt).
IETF RFC 6557
Procedures for Maintaining the Time Zone Database, E. Lear, P. Eggert, February 2012 (available at: www.ietf.org/rfc/rfc6557.txt).
IETF RFC 8200
Internet Protocol, Version 6 (IPv6) Specification, S. Deering, R. Hinden, July 2017 (available at: www.ietf.org/rfc/rfc8200.txt).
before:
Internationalisation Guide

On page 555 line 19952 section 2.10.19, after:
Support for sockets over Internet protocols based on IPv4 is mandatory.
add:
IPv4 is described in RFC 791.

After page 555 line 19966 section 2.10.20, add a new paragraph:
IPv6 is described in RFC 8200.

On page 555 line 19971 section 2.10.20.1, and
page 1235 line 42213 section inet_ntop(), change:
RFC 2373
to:
RFC 4291

On page 840 line 28773 section endhostent(), and
page 1018 line 34929 section freeaddrinfo(), change:
RFC 1886
to:
RFC 3596

On page 3099 line 104305 section mailx, change:
RFC 5322 (which succeeded RFC 822)
to:
RFC 5322

Tagsapplied_after_i8d3, issue8

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2023-04-25 09:38 geoffclare New Issue
2023-04-25 09:38 geoffclare Name => Geoff Clare
2023-04-25 09:38 geoffclare Organization => The Open Group
2023-04-25 09:38 geoffclare Section => Referenced Documents
2023-04-25 09:38 geoffclare Page Number => xxxvi-xxxvii
2023-04-25 09:38 geoffclare Line Number => N/A
2023-06-15 15:35 Don Cragun Status New => Resolved
2023-06-15 15:35 Don Cragun Resolution Open => Accepted
2023-06-15 15:35 Don Cragun Tag Attached: issue8
2023-07-06 10:31 geoffclare Status Resolved => Applied
2023-07-06 10:31 geoffclare Tag Attached: applied_after_i8d3
2024-06-11 09:12 agadmin Status Applied => Closed