Issues Associated with Designating Additional Private IPv4 Address Space
RFC 6319, “Issues Associated with Designating Additional Private IPv4 Address Space”, is an Informational document published in July 2011 by M. Azinger, L. Vegoda. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6319 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6318 Suite B in Secure/Multipurpose Internet Mail Extensions
- RFC 6320 Protocol for Access Node Control Mechanism in Broadband Networks
- RFC 6317 Basic Socket Interface Extensions for the Host Identity Protocol
- RFC 6321 xCal: The XML Format for iCalendar
- RFC 6316 Sockets Application Program Interface for Multihoming Shim
- RFC 6322 Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams
- RFC 6315 IANA Registration for Enumservice 'iax'
- RFC 6323 Sender RTT Estimate Option for the Datagram Congestion Control Protocol