As per Relevance of the word statement, we have this rfc below:
Network Working Group Internet Engineering Steering
Request for Comments: 1517 R. Hinden,
Category: Standards Track September 1993
Applicability Statement for the Implementation
Classless Inter-Domain Routing (CIDR
Status of this
This RFC specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" for the standardization state and
of this protocol. Distribution of this memo is unlimited
1.
As the Internet has evolved and grown in recent years, it has
clear that it will soon face several serious scaling problems.
include
- Exhaustion of the class-B network address space.
fundamental cause of this problem is the lack of a
class of a size that is appropriate for a mid-
organization. Class-C, with a maximum of 254 host addresses,
too small, while class-B, which allows up to 65534 addresses
is too large to be densely populated. The result is
utilization of class-B network numbers
- Routing information overload. The size and rate of growth of
routing tables in Internet routers is beyond the ability
current software (and people) to effectively manage
- Eventual exhaustion of IP network numbers
It has become clear that the first two of these problems are
to become critical in the near term. Classless Inter-Domain
(CIDR) ttempts to deal with these problems by defining a mechanism
slow the growth of routing tables and reduce the need to allocate
IP network numbers. It does not attempt to solve the third problem
which is of a more long-term nature, but instead endeavors to
enough of the short to mid-term difficulties to allow the Internet
continue to function efficiently while progress is made on a longer
term solution
The IESG, after a thorough discussion in the IETF, in June 1992
selected CIDR as the solution for the short term routing
IESG [Page 1]
RFC 1517 CIDR Applicability Statement September 1993
explosion problem [1].
2. Components of the
The CIDR architecture is described in the following documents
- "An Architecture for IP Address Allocation with CIDR" [2]
- "Classless Inter-Domain Routing (CIDR): An Address
and Aggregation Strategy" [3]
The first of these documents presents the overall architecture
CIDR; the second describes the specific address allocation scheme
be used
In addition to these two documents, "Guidelines for Management of
Address Space" [4] provides specific recommendations for assigning
addresses that are consistent with [2] and [3], and "Status of
Deployment in the Internet" [5] describes the timetable for
[4] in the Internet. Both [4] and [5] should be viewed
supporting, rather than defining, documents
In addition to the documents mentioned above, CIDR requires
inter-domain routing protocols be capable of handling
information that is expressed solely in terms of IP address prefixes
While several inter-domain routing protocols are capable
supporting such functionality, this Applicability Statement does
mandate the use of a particular one
Although Internet routing domains are not required to use
protocols capable of propagating CIDR routes, the topology
routing domains can support will be somewhat limited. In particular
the non-CIDR-capable parts of the Internet will need to
towards the CIDR-capable parts of the Internet for routes which
been aggregated to non-network boundaries
3. Applicability of
The CIDR architecture is applicable to any group of connected
that supports IP version 4 [6] [7]. CIDR does not require all of
domains in the Internet to be converted to use CIDR. It assumes
some of the existing domains in the Internet will never be able
convert. Despite this, CIDR will still provide connectivity to
places, although the optimality of routes to these places may
impacted
This Applicability Statement requires Internet domains
backbone and/or transit service to fully implement CIDR in order
IESG [Page 2]
RFC 1517 CIDR Applicability Statement September 1993
ensure that the growth of the resources required by routers
provide Internet-wide connectivity will be significantly slower
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
reduce the amount of routing information inside of these domains
Individual domains are free to choose whatever inter-domain
intra-domain routing architectures best meet their requirements
Specifically, this Applicability Statement does not prevent a
or a group of domains from using addressing schemes which do
conform to CIDR. Subject to the available resources in routers,
should be able to co-exist with other addressing schemes
adversely impacting overall connectivity
4.
[1] Gross, P., and P. Almquist, "IESG Deliberations on Routing
Addressing", RFC 1380, IESG Chair, IESG Internet AD,
1992.
[2] Rekhter, Y., and T. Li, "An Architecture for IP
Allocation with CIDR", RFC 1518, T.J. Watson Research Center,
Corp., cisco Systems, September 1993.
[3] Fuller, V., Li, T., Yu, J., and K. Varadhan, "Classless Inter
Domain Routing (CIDR): An Address Assignment and
Strategy", RFC 1519, BARRNet, cisco, Merit, and OARnet,
1993.
[4] Gerich, E., "Guidelines for Management of IP Address Space",
1466, Merit, May 1993.
[5] Topolcic, C., "Status of CIDR Deployment in the Internet",
1467, CNRI, August 1993.
[6] Postel, J., "Internet Protocol - DARPA Internet Program
Specification", STD 5, RFC 791, USC/Information
Institute, September 1981.
[7] Braden, R., Editor, "Requirements for Internet Hosts --
Communication Layers", STD 3, RFC 1122, IETF, October 1989.
5. Security
Security issues are not discussed in this memo
IESG [Page 3]
RFC 1517 CIDR Applicability Statement September 1993
6. Author's
Robert M.
Sun
2550 Garcia Ave, MS MTV5-44
Mt. View, CA 94043
Phone: (415) 336-2082
Fax: (415) 336-6015
EMail: hinden@eng.sun.
IESG [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
