RFC 1629: Guidelines for OSI NSAP Allocation in the Internet
In plain English — editorial summary, not part of the RFC
This paper provides guidelines for allocating NSAP addresses in the Internet. The guidelines provided in this paper have been the basis for initial deployment of CLNP in the Internet, and have proven very valuable both as an aid to scaling of CLNP routing, and for address administration. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1629
- Published
- May 1994
- Authors
- R. Colella; R. Callon; E. Gardner; Y. Rekhter
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- osi
- Pages
- 52
- Also known as
- —
- Obsoletes:
- RFC 1237
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 1577Classical IP and ARP over ATMObsoleted
January 1994
- RFC 1574Essential Tools for the OSI InternetCurrent
February 1994
- RFC 1526Assignment of System Identifiers for TUBA/CLNP HostsCurrent
September 1993
- RFC 1735NBMA Address Resolution Protocol (NARP)Current
December 1994
- RFC 1517Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)Current
September 1993
- RFC 1798Connection-less Lightweight X.500 Directory Access ProtocolObsoleted
June 1995
- RFC 1917An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANACurrent
February 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?