RFC 7618: Dynamic Allocation of Shared IPv4 Addresses
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7618
- Published
- August 2015
- Authors
- Y. Cui; Q. Sun; I. Farrer; Y. Lee; Q. Sun; M. Boucadair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7626DNS Privacy ConsiderationsObsoleted
August 2015
- RFC 7629Flow-Binding Support for Mobile IPCurrent
August 2015
- RFC 7600IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)Current
July 2015
- RFC 7599Mapping of Address and Port using Translation (MAP-T)Current
July 2015
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 7597Mapping of Address and Port with Encapsulation (MAP-E)Current
July 2015
- RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent
July 2015
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
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?