OSI NSAPs and IPv6
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 16
- Abstract
- This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. This memo defines an Experimental Protocol for the Internet community.
- Publication Date
- 1996-08-01
- Status Note
- Historic
- DOI
10.17487/RFC1888- Link
- https://doi.org/10.17487/RFC1888
- Author(s)
- Jim BoundBrian E. CarpenterDan HarringtonJack HouldsworthAlan Lloyd
- Keyword(s)
- IP, OSI
Latest version of IETF RFC 1888
Document Versions — IETF RFC 1888
-
▶ IETF RFC 1888 (1996-08-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- RFC4048 NOT IN REGISTRY
Amended by:
- RFC4548 NOT IN REGISTRY
Bibliographic Reference(s)
- ISO.8473 — 37 EXTERNAL
- IETF RFC 1006 [Active*]
- IETF RFC 1326 [Active*]
- IETF RFC 1629 [Active*]
- IETF RFC 1825 [Superseded*]
- IETF RFC 1883 [Superseded*]
- IETF RFC 1884 [Superseded*]
- IETF RFC 1970 [Superseded*]
- IETF RFC 1971 [Superseded*]
- T-REC-X.213.1993 — IS8348 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1888.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1888, OSI NSAPs and IPv6. Available at https://doi.org/10.17487/RFC1888
Snippet:
IETF RFC 1888, OSI NSAPs and IPv6. Available at https://doi.org/10.17487/RFC1888
HTML (ISO 690 compliant)
Preview:
IETF RFC 1888, OSI NSAPs and IPv6. Available at https://doi.org/10.17487/RFC1888
Snippet:
<span class="citation"><cite>IETF RFC 1888</cite>, OSI NSAPs and IPv6. Available at <a href="https://doi.org/10.17487/RFC1888" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1888</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc1888">IETF RFC 1888</cite>, OSI NSAPs and IPv6 <span class="doi">10.17487/RFC1888</span> </li>
Referenced By
- IETF RFC 2373 [Superseded*]
- IETF RFC 3513 [Superseded*]