RFC 6654: Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
In plain English — editorial summary, not part of the RFC
This document proposes an alternative IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) deployment model to that of RFC 5969. The basic 6rd model allows IPv6 hosts to gain access to IPv6 networks across an IPv4 access network using 6-in-4 tunnels. 6rd requires support by a device (the 6rd customer edge, or 6rd-CE) on the customer site, which must also be assigned an IPv4 address. The alternative model described in this document initiates the 6-in-4 tunnels from an operator-owned Gateway collocated with the operator's IPv4 network edge rather than from customer equipment, and hence is termed "Gateway-initiated 6rd" (GI 6rd). The advantages of this approach are that it requires no modification to customer equipment and avoids assignment of IPv4 addresses to customer equipment. The latter point means less pressure on IPv4 addresses in a high-growth environment. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6654
- Published
- July 2012
- Authors
- T. Tsou; C. Zhou; T. Taylor; Q. Chen
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7849An IPv6 Profile for 3GPP Mobile DevicesCurrent
May 2016
- RFC 6782Wireline Incremental IPv6Current
November 2012
- RFC 7040Public IPv4-over-IPv6 Access NetworkCurrent
November 2013
- RFC 5969IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol SpecificationCurrent
August 2010
- RFC 7755SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center EnvironmentsCurrent
February 2016
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7757Explicit Address Mappings for Stateless IP/ICMP TranslationCurrent
February 2016
- RFC 8215Local-Use IPv4/IPv6 Translation PrefixCurrent
August 2017
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?