Browse Prior Art Database

Dynamic Allocation of Shared IPv4 Addresses (RFC7618) Disclosure Number: IPCOM000242785D
Original Publication Date: 2015-Aug-01
Included in the Prior Art Database: 2015-Aug-15
Document File: 30 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Y. Cui: AUTHOR [+5]


The shortage of available public IPv4 addresses means that it is not always possible for operators to allocate a full IPv4 address to every connected device. This problem is particularly acute while an operator is migrating from their existing, native IPv4 network to a native IPv6 network with IPv4 provided as an overlay service. During this phase, public IPv4 addresses are needed to provide for both existing and transition networks.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                            Y. Cui Request for Comments: 7618                                        Q. Sun Category: Standards Track                            Tsinghua University ISSN: 2070-1721                                                I. Farrer                                                      Deutsche Telekom AG                                                                   Y. Lee                                                                  Comcast                                                                   Q. Sun                                                            China Telecom                                                             M. Boucadair                                                           France Telecom                                                              August 2015

               Dynamic Allocation of Shared IPv4 Addresses


   This memo describes the dynamic allocation of shared IPv4 addresses    to clients using DHCPv4.  Address sharing allows a single IPv4    address to be allocated to multiple active clients simultaneously,    with each client being differentiated by a unique set of transport-    layer source port numbers.  The necessary changes to existing DHCPv4    client and server behavior are described, and a new DHCPv4 option for    provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its    applicability are necessary.  This memo describes these limitations    and recommends suitable architectures and technologies where address    sharing may be utilized.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Cui, et al.                ...