| |
RFC 1237 (rfc1237) - Guidelines for OSI NSAP Allocation in the Internet |
 | | Colella, Gardner, and Callon [Page 12] RFC 1237 Guidelines for OSI NSAP Allocation in the Internet July 1991 For those destinations which are in the domain, level 2 routing treats the entire area address (i.e., all of the NSAP address except the ID and SEL fields) as if it were a flat field. |
 | | Colella, Gardner, and Callon [Page 21] RFC 1237 Guidelines for OSI NSAP Allocation in the Internet July 1991 5.3.1 Regionals It is interesting to consider whether regional routing domains should be the common authority for assigning NSAPs from a unique prefix to the leaf routing domains that they serve. |
 | | Colella, Gardner, and Callon [Page 31] RFC 1237 Guidelines for OSI NSAP Allocation in the Internet July 1991 Also note that the possible requirement to transition addresses based on changes in topology imply that it is valuable to anticipate the future topology changes before finalizing a plan for address allocation. |
| www.faqs.org /rfcs/rfc1237.html (13432 words) |