Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

M. Ford, Ed.
M. Boucadair
A. Durand
P. Levis
P. Roberts

Stream:

IETF

Source:

intarea (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6269

Discuss this RFC: Send questions or comments to the mailing listint-area@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6269

Abstract

The completion of IPv4 address allocations from IANA and the RegionalInternet Registries (RIRs) is causing service providers around theworld to question how they will continue providing IPv4 connectivityservice to their subscribers when there are no longer sufficient IPv4addresses to allocate them one per subscriber. Several possiblesolutions to this problem are now emerging based around the idea ofshared IPv4 addressing. These solutions give rise to a number ofissues, and this memo identifies those common to all such addresssharing approaches. Such issues include application failures,additional service monitoring complexity, new securityvulnerabilities, and so on. Solution-specific discussions are out ofscope.

Deploying IPv6 is the only perennial way to ease pressure on thepublic IPv4 address pool without the need for address sharingmechanisms that give rise to the issues identified herein. This document is not an Internet Standards Track specification; it ispublished for informational purposes.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.