Assignment of System Identifiers for TUBA/CLNP Hosts (RFC1526)
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2019-Feb-13
Internet Society Requests For Comment (RFCs)
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.
Network Working Group D. Piscitello Request for Comments: 1526 Bellcore Category: Informational September 1993
Assignment of System Identifiers for TUBA/CLNP Hosts
Status of this Memo
This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.
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. The mechanism is extensible and can provide a basis for assigning system identifiers in a globally unique fashion.
This memo specifies methods for assigning a 6 octet system identifier portion of the OSI NSAP address formats described in "Guidelines for OSI NSAP Allocation in the Internet" , in a fashion that ensures that the ID is unique within a routing domain. It also recommends methods for assigning system identifiers having lengths other than 6 octets. The 6 octet system identifiers recommended in this RFC are assigned from 2 globally administered spaces (IEEE 802 or "Ethernet", and IP numbers, administered by the Internet Assigned Numbers Authority, IANA).
At this time, the primary purpose for assuring uniqueness of system identifiers is to aid in autoconfiguration of NSAP addresses in TUBA/CLNP internets . The guidelines in this paper also establish an initial framework within which globally unique system identifiers, also called endpoint identifiers, may be assigned.
Many thanks to Radia Perlman, Allison Mankin, and Ross Callon of for their insights and assistance. Thanks also to the Ethernet connector to my MAC, which conveniently and quite inobtrusively fell out, enabling me to get an entire day’s worth of work done without email interruptions.
Piscitello [Page 1]
RFC 1526 System Identifiers for TUBA September 1993
The general format of OSI network service access point (NSAP) addresses is illustrated in Figure 1.
_______________________________________________ |____IDP_____|_______________DSP______________| |__AFI_|_IDI_|_____HO-DSP______|___ID___|_SEL_|
IDP Initial Domain Part AFI Authority and Format Identifier IDI Initial Domain Identifier DSP Domain Specific Part HO-DSP High-order DSP ID System Identifier SEL NSAP Selector
Figure 1: OSI NSAP Address Structure.
The recommended encoding and allocation of NSAP addresses in the Internet is specified in RFC 1237. RFC 1237 makes the following statements regarding the system identifier (ID) field of the NSAPA:
1. the ID field may be from one to eight octets in length
2. the ID must have a single known length in any particular routing domain
3. the ID field must be unique within an area for ESs and level 1 ISs, and unique within the routing domain for level 2 ISs.
4. the ID field is assumed to be flat
RFC 1237 further indicates that, within a routing domain that conforms to the OSI intradomain...