RFC 1629:Guidelines for OSI NSAP Allocation in the...
RFC-Ref

Addressing


Click on the red underlined text to get to the source

... NSAP allocation in this paper, providers are treated as composing a mesh having no fixed hierarchy. Addressing solutions which require substantial changes or constraints on the current topology ...
... services. The requirements for addressing for these future services is outside of the scope of this document. ...
... The anticipated need for additional levels of hierarchy in Internet addressing to support network growth and use of the Routing ...
... subscribers) and OSI addressing and routing components, such as areas, domains and ...
... method of deciding on a particular topology or internal addressing plan is not; and, ...


... NSAP addresses provide a flexible, variable length addressing format, which allows for multi-level hierarchical address assignment ...
... address. The DSP is assigned by whatever addressing authority is specified by the IDP ...
... discussion on the top level NSAP addressing authorities). It is expected that the authority ...
... Since the addressing explicitly identifies the area, it is very easy for level 1 routers to identify packets going to destinations ...
... routing domain which contains a mix of systems which use NSAP addresses assigned by several different addressing authorities. ...


... Internet grows, further levels of hierarchy may become necessary. Again, this requires considerable flexibility in the addressing scheme, such as is provided by NSAP addresses. ...


... reasonable that this relationship also extend to include a common NSAP addressing authority. Thus, the areas within the subscriber RD ...
... Note that the relationship between routing and NSAP addressing described in other sections of this paper is concerned with problems in scaling caused by large, essentially public transit routing ...
... subscribes to the global OSI addressing plan (i.e., ISO 8348). This RD must be able to ...


... presented below are consistent with the technical requirements for scaling of addressing and routing presented in this RFC. ...
... However, the total number of such providers is expected to remain (for the foreseeable future) small enough to allow addressing of this set of providers via a flat address space. These providers will be ...


... OSI Network Layer Addressing Scheme, Its Implications, and Considerations for Implementation", NTIA Report 85186, U.S. Department of Commerce, National Telecommunications and Information Administration, 1985. ...
... Network Service Definition Covering Network Layer Addressing," RFC 941, ISO, April 1985. ...
... ISO/IEC, "Information Processing Systems - OSI Reference Model - Part3: Naming and Addressing", Draft International Standard 7498-3, ISO/IEC JTC 1, Switzerland, March 1989. ...
... Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing", RFC 1347, DEC, June 1992. ...


... IDI, the network addressing authority responsible for allocating values of the IDI ...
... DSP. The IDI specifies the addressing subdomain from which values of the DSP are allocated and the network ...
... DSP are allocated and the network addressing authority responsible for allocating values of the DSP ...
... The global network addressing domain consists of all the NSAP addresses in the OSI ...
... NSAP addresses in the OSI environment. Within that environment, seven second-level addressing domains and corresponding IDI formats are ...
... OSI network addressing schemes. ...
... GOSIP Version 2 makes available for government use an NSAP addressing subdomain with a corresponding address format as illustrated in ...
... The main responsibility of a registration authority at any level of the addressing hierarchy is to assure that names of entities are unambiguous, i.e., no two entities have the same name. The registration authority ...



Google
Web
RFC-Ref