RFC 7600: IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)
In plain English — editorial summary, not part of the RFC
This document specifies a stateless solution for service providers to progressively deploy IPv6-only network domains while still offering IPv4 service to customers. The solution's distinctive properties are that TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during domain traversal and that IPv4 fragmentation rules are fully preserved end to end. Each customer can be assigned one public IPv4 address, several public IPv4 addresses, or a shared address with a restricted port set.
Document record
- Document ID
- RFC7600
- Published
- July 2015
- Authors
- R. Despres; S. Jiang; R. Penno; Y. Lee; G. Chen; M. Chen
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 45
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6751Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)Current
October 2012
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 6970Universal Plug and Play (UPnP) Internet Gateway Device - Port Control Protocol Interworking Function (IGD-PCP IWF)Current
July 2013
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
January 2010
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 4392IP over InfiniBand (IPoIB) ArchitectureCurrent
April 2006
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 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?