RFC 6319: Issues Associated with Designating Additional Private IPv4 Address Space
In plain English — editorial summary, not part of the RFC
When a private network or internetwork grows very large, it is sometimes not possible to address all interfaces using private IPv4 address space because there are not enough addresses. This document describes the problems faced by those networks, the available options, and the issues involved in assigning a new block of private IPv4 address space. While this informational document does not make a recommendation for action, it documents the issues surrounding the various options that have been considered. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6319
- Published
- July 2011
- Authors
- M. Azinger; L. Vegoda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
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?