RFC 1526: Assignment of System Identifiers for TUBA/CLNP Hosts
In plain English — editorial summary, not part of the RFC
This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1526
- Published
- September 1993
- Authors
- D. Piscitello
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
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 2225Classical IP and ARP over ATMUpdated
April 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2290Mobile-IPv4 Configuration Option for PPP IPCPUpdated
February 1998
- RFC 2320Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB)Current
April 1998
- RFC 2332NBMA Next Hop Resolution Protocol (NHRP)Current
April 1998
- RFC 2374An IPv6 Aggregatable Global Unicast Address FormatObsoleted
July 1998
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?