Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
RFC 6654
| Document | Type |
RFC - Informational
(July 2012; No errata)
Was draft-tsou-softwire-gwinit-6rd (individual)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | ISE | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | ISE state | (None) | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6654 (Informational) | |
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note |
The IESG has concluded that this work is related to IETF work done in the softwire WG, but this relationship does not prevent publishing. |
||
| Send notices to | (None) | ||
Independent Submission T. Tsou
Request for Comments: 6654 Huawei Technologies (USA)
Category: Informational C. Zhou
ISSN: 2070-1721 T. Taylor
Huawei Technologies
Q. Chen
China Telecom
July 2012
Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
Abstract
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see 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
http://www.rfc-editor.org/info/rfc6654.
Tsou, et al. Informational [Page 1]
RFC 6654 Gateway-Initiated 6rd July 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Table of Contents
1. Introduction ....................................................2
2. Problem Statement ...............................................3
3. Proposed Solution ...............................................4
3.1. Prefix Delegation ..........................................5
3.2. Relevant Differences from Basic 6rd ........................6
4. Security Considerations .........................................7
5. Acknowledgements ................................................7
6. References ......................................................7
6.1. Normative References .......................................7
6.2. Informative References .....................................7
1. Introduction
6rd [RFC5969] provides a transition tool for connecting IPv6 devices
across an IPv4 network to an IPv6 network, at which point the packets
can be routed natively. The network topology is shown in Figure 1.
+--------------+ +-----------------+ +---------+
| | | | | |
+-----+ +-----+ | Provider +--------+ | |
|IPv6 | | 6rd |__| IPv4 | Border |__| IPv6 |
|Host | | CE | | Network | Router | | Network |
+-----+ +-----+ | +--------+ | |
| Customer LAN | | | | |
+--------------+ +-----------------+ +---------+
Figure 1: 6rd Deployment Topology
In Figure 1, the CE is the customer edge router. It is provisioned
with a delegated IPv6 prefix, but it is also configured with an IPv4
address so that it is reachable through the IPv4 network. If a
public IPv4 address is provisioned to every customer, it will
aggravate the pressure due to the IPv4 address shortage for operators
Tsou, et al. Informational [Page 2]
RFC 6654 Gateway-Initiated 6rd July 2012
faced with a high rate of growth in the number of broadband
Show full document text