Skip to main content

Issues Associated with Designating Additional Private IPv4 Address Space
RFC 6319

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'When a private network or internetwork grows very large, it is sometimes not possible to address …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from leo.vegoda@icann.org, marla.azinger@frontiercorp.com, draft-azinger-additional-private-ipv4-space-issues@ietf.org to (None)
2011-07-19
Cindy Morgan State changed to RFC Published from Approved-announcement sent.
RFC 6319
2011-07-19
(System) RFC published