RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links
In plain English — editorial summary, not part of the RFC
With ever-increasing pressure to conserve IP address space on the Internet, it makes sense to consider where relatively minor changes can be made to fielded practice to improve numbering efficiency. One such change, proposed by this document, is to halve the amount of address space assigned to point-to-point links (common throughout the Internet infrastructure) by allowing the use of 31-bit subnet masks in a very limited way. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3021
- Published
- December 2000
- Authors
- A. Retana; R. White; V. Fuller; D. McPherson
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3011The IPv4 Subnet Selection Option for DHCPCurrent
November 2000
- RFC 3056Connection of IPv6 Domains via IPv4 CloudsCurrent
February 2001
- RFC 2932IPv4 Multicast Routing MIBObsoleted
October 2000
- RFC 2794Mobile IP Network Access Identifier Extension for IPv4Current
March 2000
- RFC 2765Stateless IP/ICMP Translation Algorithm (SIIT)Obsoleted
February 2000
- RFC 2734IPv4 over IEEE 1394Current
December 1999
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
- RFC 2663IP Network Address Translator (NAT) Terminology and ConsiderationsCurrent
August 1999
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?