RFC 1888: OSI NSAPs and IPv6
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4048.
Current version: RFC 4048 — RFC 1888 Is Obsolete
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC1888
- Published
- August 1996
- Authors
- J. Bound; B. Carpenter; D. Harrington; J. Houldsworth; A. Lloyd
- Status
- HISTORIC
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1377The PPP OSI Network Layer Control Protocol (OSINLCP)Current
November 1992
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 1897IPv6 Testing Address AllocationObsoleted
January 1996
- RFC 1970Neighbor Discovery for IP Version 6 (IPv6)Obsoleted
August 1996
- RFC 1972A Method for the Transmission of IPv6 Packets over Ethernet NetworksObsoleted
August 1996
- RFC 1981Path MTU Discovery for IP version 6Obsoleted
August 1996
- RFC 2002IP Mobility SupportObsoleted
October 1996
- RFC 2003IP Encapsulation within IPUpdated
October 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?