As per Relevance of the word deployment, we have this rfc below:
Network Working Group C.
Request for Comments: 1467
Obsoletes: 1367 August 1993
Status of CIDR Deployment in the
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
This document describes the current status of the development
deployment of CIDR technology into the Internet. This
replaces RFC 1367, which was a schedule for the deployment of
address space management procedures to support route aggregation
Since all the milestones proposed in RFC 1367 except for the
and installation of CIDR software were met, it does not
appropriate to issue an updated schedule. Rather, this document
intended to provide information about how this effort is proceeding
which may be of interest to the community
1.
The Internet's exponential growth has led to a number of
relating to the management of IP network numbers. The
overhead of allocating ever increasing volumes of IP network
for global users has stressed the organizations that perform
function. The volume of IP network numbers that are
through the Internet has taxed a number of routers' ability to
their forwarding tables. The poor utilization of allocated
network numbers has threatened to deplete the Class A and Class
address space
During the past few years, a consensus has emerged among the
community in favor of a number of mechanisms to relieve
problems for the mid-term. These mechanisms are expected to be
into place in the short term and to provide relief for the mid-term
Fundamental changes to the Internet protocols to ensure
Internet's continued long term growth and well being are
explored and are expected to succeed the mid-term mechanisms
The global Internet community have been cooperating closely in
forums as the IETF and its working groups, the IEPG, the NSF
Techs Meetings, INET, INTEROP, FNC, FEPG, and other assemblies
Topolcic [Page 1]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
order to ensure the continued stable operation of the Internet
Recognizing the need for the mid-term mechanisms and
support from the Internet community, the US Federal Agencies
procedures to assist the deployment of these mid-term mechanisms
These procedures were originally described in RFC 1366 [1], which
recently made obsolete by RFC 1466 [2]. In October 1992, a
was proposed for the implementation of the procedures, described
RFC 1367 [3].
2. Milestones that have been
Most of the milestones of the proposed schedule were implemented
time. These milestones are shown below, essentially as they appear
[3], but with further comment where appropriate
1) 31 October 92:
The following address allocation procedures were continued
a) Initial set of criteria for selecting regional
registries were put into place, and requests
prospective regional registries were accepted by
IANA
The Reseaux IP Europeens Network Coordination
(RIPE NCC) requested to become a regional registry
As per the addressing plan of RFC 1366, the RIPE
was given the block 194.0.0.0 to 195.255.255.255
administer for the European Internet community. The
NCC had previously and independently obtained the
193.0.0.0 to 193.255.255.255. Although this block had
allocated before RFC 1366, the RIPE NCC was able to
it according to the guidelines in RFC 1366.
b) Class A network numbers were put on reserve for
future use. The unreserved Class A numbers became
difficult to obtain
c) Class B network numbers were issued only
reasonably justified. Whenever possible, a block of C'
was issued rather than a B. The requirements
allocating a Class B became progressively more
until the date in step (3).
Topolcic [Page 2]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
d) Class C network numbers were allocated according to
addressing plan of [1], now obsoleted by [2].
continued to be performed by the Internet Registry (IR
for regions of the world where an appropriate
registry had not yet been designated by the IANA
2) 14 February 93:
The schedule in [3] was re-evaluated, and there appeared
be no reason to readjust it, so it was continued
originally set out
3) 15 April 93:
a) The IR began to allocate all networks according to
addressing plan of [1], now obsoleted by [2],
appropriately sized blocks of Class C numbers
b) Class B network numbers became difficult to obtain
following the recommendation of the addressing plan
were only issued when justified
Furthermore, throughout this time period, network service
have requested blocks of network numbers from the Class C
space for the purpose of further allocating them to their clients
The network service providers were allocated such space by the
NCC or the IR, acting for North America and the Pacific Rim.
process has started to distribute the function of
registration to a more regional level, closer to the end users.
process has operated as hoped for, with no major problems
3. Milestone that has not been
The proposed schedule of [3] stated that 6 June 1993 was the
when an address aggregation mechanism would be generally available
the Internet. Although this target date was based on the plans
stated by the router vendors and was reasonable at the time
schedule in [3] was formulated, it has slipped. Nevertheless,
continuation of that schedule has so far not added significantly
the problems of the Internet. The rest of this document looks at
current situation and what can be expected in the near future
4. Current status of address aggregation mechanisms in
Although RFCs 1366, 1466, and 1367 do not depend on any
address aggregation technology, there is consensus in the
community to use Classless Inter-Domain Routing (CIDR) [4]. CIDR
Topolcic [Page 3]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
supported by BGP-4 and IDRP. Most router vendors are working on BGP
4, first, and there is a consensus to use BGP-4 to support
initial deployment of CIDR in the Internet
The following paragraphs describe the implementation status and
of software to support CIDR in various router vendors' products
listed in alphabetical order. Some speculation is
involved in deriving these projections. See also the minutes of
July 1993 meeting of the BGP Deployment Working Group of the
[5].
3Com's BGP-4 code has been tested internally. They have code
accepts, forwards and manages aggregated routes properly, and
are ready to test it for interoperability with other vendors.
have yet to implement the code that forms the route aggregates.
expect to have Beta code done by September, and full release
shortly thereafter. The initial implementation will not support de
aggregation. Their plans here are not yet formulated. They
support de-aggregation if necessary
ANS has a BGP-4 implementation that is being tested internally.
is stable enough to begin testing for interoperability with
vendors' implementations. Depending of the results
interoperability testing, this code could be deployed into the
by August. This delay is primarily because some routers are
older code, and they all need to be upgraded to GATED before they
all support BGP-4 internally. So the ability to support CIDR
like it is about one to two months away. This code will not
controlled de-aggregation, but de-aggregation will be supported
necessary
BBN plans to complete it's development of BGP-4 by early Summer 1994.
Initial plans are to implement both aggregation and controlled de
aggregation with an early release of the software
Cisco's BGP-4 implementation is under development at this time
There is pre-Beta code available for people to begin testing. It
expected that the code will be stable sometime during the summer
1993 and will be made available for limited deployment at that time
This BGP-4 code will implement aggregation. It will not be part
the normal release cycle at this time. It will be available in
special software release based on the 9.21 release. This
BGP-4 code will not implement controlled de-aggregation, but
plans on implementing de-aggregation
Proteon's BGP-4 code has been tested internally. They are ready
test it for interoperability with other vendors. If this works
reasonably well, then it is reasonable to expect that they can
Topolcic [Page 4]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
to deploy this as Beta code by August, with a target of full
in the fall. This initial implementation will not support
or de-aggregation. Aggregation will be implemented soon thereafter
but their plans for de-aggregation are not yet formulated. They
implement de-aggregation if necessary
Wellfleet is aiming at having beta code implementing BGP-4 roughly
early 1994. This code will include controlled de-aggregation
5. Rate of
MERIT periodically publishes the number of networks in
NSFNET/ANSNET policy routing database. Analysis of this
suggests that the number of entries in this database is growing
approximately 8% per month, or doubling every nine or ten months [6].
Although there are currently over 13K networks in the NSFNET/
policy routing database, a number of them are not active. That is
they are not announced to the NSFNET/ANSNET Backbone. The 10K
network point was passed in late June. Assuming that the number
active networks continues to grow at the same rate as in the past,
can be projected that the 12K active network point will be
sometime in approximately late September 1993 and that the 25K
network point will be reached sometime in mid-94 (two high
marks whose relevance will become apparent below).
The NSFNET/ANSNET routing database includes only those networks
meet the NSF Acceptable Use Policy (AUP) or the ANSNET CO+RE AUP
There are a number of networks connected to the Internet that do
meet these criteria. Although they are not in the NSFNET/
routing database, they are in the forwarding tables of a number
network providers. Currently, the number of networks that
connected to other known service providers but are not in
NSFNET/ANSNET routing database is significantly smaller than (
than 25% of) the number that are in the NSFNET/ANSNET database.
is no estimate available for the rate of growth of the number of
non-NSFNET/ANSNET networks. It is assumed here that the growth
of these networks is approximately the same as that of AUP
in the NSFNET/ANSNET routing database
Analysis of the more than 13K networks in the NSFNET/ANSNET
database, as well as the allocated but unconnected networks,
that CIDR deployment should have a significant impact on the
of forwarding table entries that any router needs to maintain,
its rate of growth. However, an in-depth study was begun at the
1993 meeting of the BGP Deployment Working Group of the IETF [5]
(among other goals) evaluate the impact of CIDR on the growth rate
router forwarding tables
Topolcic [Page 5]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
6. Capacity of deployed
The following paragraphs describe the current occupancy of
forwarding tables of the routers of several transit network
and their expected capacities and an estimate of the time when
capacity would be reached if the growth rate were to continue
today. This list is a subset of all relevant providers, but
considered approximately representative of the situation of
network providers. It is shown in alphabetical order
ALTERNET nodes are Cisco routers, and currently carry
11K to 12K routes, both AUP and non-AUP. With their
configuration, they have enough memory so that they are expected
support up to approximately 35K routes. If the rate at which
number of these routes is expected to grow is approximately the
as the rate that the NSFNET/ANSNET policy routing database
growing, then this number may be reached in late 1994. However,
the growth rate continues unchecked, it is expected that
processing capacity of the routers will be surpassed before
memory is exhausted. It is expected that CIDR will be in place
before this point is reached
All ANSNET routers have recently been upgraded to AIX 3.2.
version supports up to 12K networks. These routers currently
only the active networks in the NSFNET/ANSNET routing database.
is anticipated that the next version of router code will be
before September 1993, the projected date for when there will be 12
active networks. This version will support 25K active networks
Although there are no current plans for a version of router code
supports more than 25K networks, it is believed that CIDR will
this situation
EBONE nodes are Cisco routers. They currently carry approximately 10
to 11K routes. With their current configuration, they may be able
support approximately 40K routes. However, the number of paths may
very relevant. The memory required for the BGP table (rather than
forwarding table) is a function of the number of paths. If a
transatlantic link were to be added, EBONE could receive all
North American routes through it. This would add a new set of paths
Each such transatlantic link would increase the memory required
approximately 20%. Due to the network topology between North
and Europe, new transatlantic links tend to result in new paths,
therefore significant memory requirements. It is very difficult
predict the addition of future transatlantic links because
result from business or political requirements, not
requirements
Topolcic [Page 6]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
ESNET uses Cisco routers. However, it is already in trouble, but
because of the size of the forwarding tables. The problem is its
to maintain considerable configuration information describing
networks it should or should not accept from its neighbors, and
fact that this information must be stored in a non-volatile memory
limited size. CIDR aggregation is expected to help this problem
Also, ESNET plans to deploy BGP-4 and CIDR only after it is in a
release, so does not plan to participate in the initial BGP-4
deployment. ESNET will upgrade their nodes to Cisco CSC-4's in
meantime
All SPRINTLINK and ICM nodes have recently been upgraded to
CSC-4 routers with 16MB of memory. They will carry full routing
including not only the routes that the NSFNET/ANSNET carries,
also routes to networks that do not comply with the NSF or CO+
AUPs. The SPRINT routers currently carry approximately 11K to 12
routes, and it is expected that they will be able to support up
approximately 25K routes, as currently configured. The 25K
network point may be reached in approximately mid-1994. Again, it
expected that CIDR deployment will have a significant impact on
growth rate, well before this time
7.
This report contains information from a number of sources,
vendors, operators, researchers, and organizations that
cooperation in the Internet community. Specific organizations
the Intercontinental Engineering and Planning Group (IEPG), the BGP-4
Deployment Working Group of the IETF, the Federal Networking
(FNC), and the FNC Engineering and Planning Group (FEPG).
individuals include, in alphabetical order, Arun Arunkumar,
Bates, Mary Byrne, Bob Collet, Mike Craren, Dennis Ferguson,
Hain, Elise Gerich, Mark Knopper, John Krawczyk, Tony Li,
Lothberg, Andrew Partan, Gary Rucinski, Frank Solensky, and
Yu. This report would not have been possible without the
of these people to make their information public for the good of
community
8.
[1] Gerich, E., "Guidelines for Management of IP Address Space",
RFC 1366, Merit, October 1992.
[2] Gerich, E., "Guidelines for Management of IP Address Space",
RFC 1466, Merit, May 1993.
[3] Topolcic, C., "Schedule for IP Address Space
Guidelines", RFC 1367, CNRI, October 1992.
Topolcic [Page 7]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
[4] Fuller, V. et al, "Classless Inter-Domain Routing (CIDR):
Address Assignment and Aggregation Strategy", working
obsoleting RFC 1338, BARRNet, February 1993.
[5] Yu, J., "Minutes of the BGP Deployment Working
(BGPDEPL)", MERIT, July 1993.
[6] Solensky, F., Internet Growth Charts, "big-internet"
list, munnari.oz.au:big-internet/nsf-netnumbers-.
9. Other relevant
Huitema, C., "IAB Recommendation for an Intermediate
to Address the Issue of Scaling", RFC 1481,
Architecture Board, July 1993.
Knopper, M., "Minutes of the NSFNET Regional Techs Meeting",
working draft, MERIT, June 1993.
Knopper, M., and Richardson, S., " Aggregation Support in
NSFNET Policy-Based Routing Database", RFC 1482, MERIT,
1993.
Topolcic, C., "Notes of BGP-4/CIDR Coordination Meeting of 11
March 93", working draft, CNRI, March 1993.
Rekhter, Y., and Topolcic, C., "Exchanging Routing
Across Provider/Subscriber Boundaries in the CIDR Environment",
working draft, IBM Corp., CNRI, April 1993.
Rekhter, Y., and Li, T., "An Architecture for IP
Allocation with CIDR", working draft, IBM Corp., cisco Systems
February 1993.
Gross, P., and P. Almquist, "IESG Deliberations on Routing
Addressing", RFC 1380, IESG, November 1992.
Topolcic [Page 8]
RFC 1467 Status of CIDR Deployment in the Internet August 1993
10. Security
Security issues are not discussed in this memo
11. Author's
Claudio
Corporation for National Research
895 Preston White Drive, Suite 100
Reston, VA 22091
Phone: (703) 620-8990
EMail: topolcic@CNRI.Reston.VA.
Topolcic [Page 9]
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
