RFC 6269: Issues with IP Address Sharing
In plain English — editorial summary, not part of the RFC
The completion of IPv4 address allocations from IANA and the Regional Internet Registries (RIRs) is causing service providers around the world to question how they will continue providing IPv4 connectivity service to their subscribers when there are no longer sufficient IPv4 addresses to allocate them one per subscriber. Several possible solutions to this problem are now emerging based around the idea of shared IPv4 addressing. These solutions give rise to a number of issues, and this memo identifies those common to all such address sharing approaches. Such issues include application failures, additional service monitoring complexity, new security vulnerabilities, and so on. Solution-specific discussions are out of scope. Deploying IPv6 is the only perennial way to ease pressure on the public IPv4 address pool without the need for address sharing mechanisms that give rise to the issues identified herein. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6269
- Published
- June 2011
- Authors
- M. Ford; M. Boucadair; A. Durand; P. Levis; P. Roberts
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8513A YANG Data Model for Dual-Stack Lite (DS-Lite)Current
January 2019
- RFC 6273The Secure Neighbor Discovery (SEND) Hash Threat AnalysisCurrent
June 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6261Encrypted Signaling Transport Modes for the Host Identity ProtocolCurrent
May 2011
- RFC 6279Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem StatementCurrent
June 2011
- RFC 6282Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based NetworksUpdated
September 2011
- RFC 6253Host Identity Protocol CertificatesObsoleted
May 2011
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?