Browse Prior Art Database

Assignment of System Identifiers for TUBA/CLNP Hosts (RFC1526)

IP.com Disclosure Number: IPCOM000002357D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 7 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Piscitello: AUTHOR

Abstract

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 text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 17% of the total text.

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.

Abstract

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.

Introduction

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" [1], 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 [2]. The guidelines in this paper also establish

an initial framework within which globally unique system identifiers,

also called endpoint identifiers, may be assigned.

Acknowledgments

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.

1. Background

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 Se...