| |
| | RFC 1629 (rfc1629) |
 | | Colella, Callon, Gardner & Rekhter [Page 17] RFC 1629 NSAP Guidelines May 1994 In the Internet, however, it should be possible to exploit the existing hierarchical routing structure interconnections, as discussed in Section 5. |
 | | Colella, Callon, Gardner & Rekhter [Page 33] RFC 1629 NSAP Guidelines May 1994 Because of the rapid growth and increased commercialization of the Internet, it is possible that the topology may be relatively volatile. |
 | | Colella, Callon, Gardner & Rekhter [Page 37] RFC 1629 NSAP Guidelines May 1994 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. |
| www.cse.ohio-state.edu /cgi-bin/rfc/rfc1629.html (15727 words) |
|