Recommendations for OSI NSAP usage in IP6
draft-carpenter-ip6-nsap-map-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Brian E. Carpenter , Jim Bound | ||
Last updated | 1994-08-30 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 IP6, should redesign a native IP6 addressing plan to meet their needs. However, in the event that network implementors prefer to keep their OSI addressing plan intact, this document defines a mapping of OSI NSAP addresses into IP6 addresses. This mapping is restricted by the 16 byte size of IP6 addresses. This document also defines a mapping of IP6 addresses within the OSI address format, should this be required for any reason.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)