Schedule for IP Address Space Management Guidelines
A timeline for rolling out new Internet address allocation rules.
Topolcic, C., "Schedule for IP Address Space Management Guidelines", RFC 1367, DOI 10.17487/RFC1367, October 1992, <https://www.rfc-editor.org/info/rfc1367>.
@misc{rfc1367,
series = {Request for Comments},
number = 1367,
howpublished = {RFC 1367},
publisher = {RFC Editor},
doi = {10.17487/RFC1367},
url = {https://www.rfc-editor.org/info/rfc1367},
author = {C. Topolcic},
title = {{Schedule for IP Address Space Management Guidelines}},
pagetotal = 3,
year = 1992,
month = oct,
} RFC text
Contents
Network Working Group C. Topolcic
Request for Comments: 1367 CNRI
October 1992
Schedule for IP Address Space Management Guidelines
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
Introduction
This memo suggests a schedule for the implementation of the IP
network number allocation plan described in RFC 1366. This schedule
is meant to support the implementation and deployment of an address
aggregation mechanism for the Internet by proposing an achievable
target for which we can all aim. The timely deployment of that
aggregation mechanism and the IP addressing plan will help the the
size of the Internet router forwarding tables and management of the
IP address space. By doing so, it will help the current Internet
addressing and routing technology operate during the interim period
until the next generation technology is deployed. This interim
solution in no way constrains the selection of the next generation
addressing and routing technology.
This draft schedule was put together by the FNC Engineering and
Planning Group (FEPG) based on the IP addressing plan BOF of the July
1992 IETF meeting, as well as discussions with a number (though, of
course, not all) of knowledgeable and interested parties, including
the IANA and IR. This draft schedule assumes that the address
aggregation mechanism will be available in the Internet by mid-1993.
The activities described in this schedule are the precursors to that
deployment, and will promote the efficient operation of that
mechanism. We feel that our assumptions are realistic and that this
schedule can be met. We encourage its open discussion as we move
toward community consensus.
Please send comments to topolcic@nri.reston.va.us, or to the
mailing list ipalloc@nri.reston.va.us. To be added to this
mailing list, send a request to ipalloc-request@nri.reston.va.us.
Note that the references below to an addressing plan and to criteria
for regional address registries refer to RFC 1366.
Draft Implementation Schedule for IP Network Number Allocation Plan:
1) 31 October 92:
The following address allocation procedures are continued:
a) Initial set of criteria for selecting regional address
registries will be put into place, and requests from
prospective regional registries will be accepted by the
IANA.
b) Class A network numbers are practically impossible to
obtain.
c) Class B network numbers will continue to be issued only when
reasonably justified. If possible, a block of C's will be
issued rather than a B. The requirements for allocating a
Class B will become progressively more constrained until the
date in step (3).
d) Class C network numbers will be allocated according to the
addressing plan. Allocation will be performed by the
Internet Registry (IR) if an appropriate regional registry
has not yet been designated by the IANA.
2) 14 February 93:
Re-evaluate and readjust the schedule if necessary.
3) 15 April 93:
a) The IR begins to allocate all networks according to the
addressing plan in appropriately sized blocks of Class C
numbers.
b) Class B network numbers will be difficult to obtain,
following the recommendation of the addressing plan and only
issued when justified.
4) 6 June 93:
Expected date that an address aggregation mechanism is
available in the Internet.
References
[1] Gerich, E., "Guidelines for Management of IP Address Space", RFC
1366, Merit, October 1992.
Security Considerations
Security issues are not discussed in this memo.
Author's Address
Claudio Topolcic
Corporation for National Research Initiatives
895 Preston White Drive
Suite 100
Reston, VA 22091
Phone: (703) 620-8990
EMail: topolcic@NRI.Reston.VA.US
AI ELI5
On this page
§1The Address Crisis
By 1992, the Internet's address space allocation system was straining. Class A addresses were essentially unavailable, Class B addresses were depleting rapidly, and the resulting large number of routing table entries threatened the Internet's routing infrastructure. RFC 1366 proposed new guidelines for managing IP address allocation, including moving toward block allocation of Class C addresses and developing address aggregation mechanisms to reduce routing table size.
This RFC proposes a realistic schedule for implementing those guidelines. It was drafted by the Federal Networking Council Engineering and Planning Group based on discussions with IANA, the Internet Registry, and the broader Internet community, with the assumption that address aggregation mechanisms would be available by mid-1993.
The Internet ran out of big address blocks. New rules were needed for handing them out more carefully. This says when each step would happen.
§2Early Phases
Phase 1 (October 31, 1992): Regional address registry criteria take effect. Class A remains unavailable. Class B allocation continues only when justified, with preference for blocks of Class C addresses instead. Class C allocation follows the new plan, administered by the Internet Registry or regional registries.
Phase 2 (February 14, 1993): Re-evaluation of the schedule if necessary.
October 1992: start saying no to Class B. February: check if the plan is working.
§3Transition to Block Allocation
Phase 3 (April 15, 1993): The Internet Registry begins allocating all networks in appropriately sized blocks of Class C numbers according to the addressing plan. Class B becomes difficult to obtain and is issued only when carefully justified.
Phase 4 (June 6, 1993): Address aggregation mechanisms are expected to be available in the Internet, allowing the transition to Classless Interdomain Routing (CIDR). This endpoint of the schedule represents the moment when the Internet's routing infrastructure could reliably use CIDR to compress routing tables and prevent the exhaustion of router memory.
April 1993: fully switch to giving out Class C blocks. June: the new routing system (CIDR) is ready.