This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2005).
This document recommends that RFC 1888, on Open Systems Interconnection (OSI) Network Service Access Points (NSAPs) and IPv6, be reclassified as Historic, as most of it has no further value, apart from one section, which is faulty.
[RFC1888] was published as an Experimental RFC in 1996, at an early stage in the development of IPv6, when it appeared important to consider usage of Open Systems Interconnection (OSI) addressing for IPv6. In Sections 3 through 5, it defines mappings of certain OSI Network Service Access Point (NSAP) addresses inside IPv6 addresses, and how to carry arbitrary NSAP addresses as IPv6 destination options. However, it also contains significant "health warnings" about the difficulty of routing packets in the global Internet using such addresses. As far as is known to the IETF, these address mappings have never been seriously used and are not supported by IPv6 implementations. Furthermore, the deployment of OSI solutions is not
sufficiently widespread that any change in this situation can be expected.
Additionally, Section 6 of [RFC1888] specifies a mapping of IPv6 addresses inside OSI NSAP addresses. This mapping has recently aroused some interest: for example, to allow IP addresses to be expressed in an Asynchronous Transfer Mode (ATM) context. Unfortunately, Section 6 of [RFC1888] contains two errors in its usage of OSI Initial Domain Part (IDP) format:
* first, the text refers to the Internet Code Point (ICP) as a single octet, whereas it is correctly a 16-bit field;
* second, the text states that "[t]he first three octets are an IDP in binary format", but [NSAP] states in section A.5.2.1 that "[t]he abstract syntax for the IDI is decimal digits" and specifies a preferred binary encoding in section A.5.3 "using a semi-octet to represent the value of each decimal digit ... , yielding a value in the range 0000-1001".
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- firstname.lastname@example.org.
Funding for the RFC Editor function is currently provided by the Internet Society.