CurrentBEST CURRENT PRACTICEIETF streamBCP122

RFC 4632: Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

In plain English — editorial summary, not part of the RFC

This memo discusses the strategy for address assignment of the existing 32-bit IPv4 address space with a view toward conserving the address space and limiting the growth rate of global routing state. This document obsoletes the original Classless Inter-domain Routing (CIDR) spec in RFC 1519, with changes made both to clarify the concepts it introduced and, after more than twelve years, to update the Internet community on the results of deploying the technology described. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC4632
Published
August 2006
Authors
V. Fuller; T. Li
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
27
Also known as
BCP122
Obsoletes:
RFC 1519

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1338 (1992)
  2. RFC 1519 (1993)
  3. RFC 4632 (2006)

Read the full history of Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4632-classless-inter-domain-routing-cidr-the-internet-address-assignment-and-aggregat