RFC 1517 (rfc1517) - Page 3 of 4

Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)

RFC 1517              CIDR Applicability Statement        September 1993


   ensure that the growth of the resources required by routers to
   provide Internet-wide connectivity will be significantly slower than
   the growth of the number of assigned networks.

   This Applicability Statement strongly recommends that all non-
   backbone/transit Internet domains also implement CIDR because it will
   reduce the amount of routing information inside of these domains.

   Individual domains are free to choose whatever inter-domain and
   intra-domain routing architectures best meet their requirements.
   Specifically, this Applicability Statement does not prevent a domain
   or a group of domains from using addressing schemes which do not
   conform to CIDR.  Subject to the available resources in routers, CIDR
   should be able to co-exist with other addressing schemes without
   adversely impacting overall connectivity.

4. References

   [1] Gross, P., and P. Almquist, "IESG Deliberations on Routing and
       Addressing", RFC 1380, IESG Chair, IESG Internet AD, November
       1992.

   [2] Rekhter, Y., and T. Li, "An Architecture for IP Address
       Allocation with CIDR", RFC 1518, T.J. Watson Research Center, IBM
       Corp., cisco Systems, September 1993.

   [3] Fuller, V., Li, T., Yu, J., and K. Varadhan, "Classless Inter-
       Domain Routing (CIDR): An Address Assignment and Aggregation
       Strategy", RFC 1519, BARRNet, cisco, Merit, and OARnet, September
       1993.

   [4] Gerich, E., "Guidelines for Management of IP Address Space", RFC
       1466, Merit, May 1993.

   [5] Topolcic, C., "Status of CIDR Deployment in the Internet", RFC
       1467, CNRI, August 1993.

   [6] Postel, J., "Internet Protocol - DARPA Internet Program Protocol
       Specification", STD 5, RFC 791, USC/Information Sciences
       Institute, September 1981.

   [7] Braden, R., Editor, "Requirements for Internet Hosts --
       Communication Layers", STD 3, RFC 1122, IETF, October 1989.

5. Security Considerations

   Security issues are not discussed in this memo.




IESG