Framework for IPv4/IPv6 Translation
RFC 6144
|
| Document |
Type |
|
RFC - Informational
(April 2011; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-baker-behave-v4v6-framework
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6144 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
David Harrington
|
|
IESG note |
|
Dan Wing (dwing@cisco.com) is the document shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) F. Baker
Request for Comments: 6144 Cisco Systems
Category: Informational X. Li
ISSN: 2070-1721 C. Bao
CERNET Center/Tsinghua University
K. Yin
Cisco Systems
April 2011
Framework for IPv4/IPv6 Translation
Abstract
This note describes a framework for IPv4/IPv6 translation. This is
in the context of replacing Network Address Translation - Protocol
Translation (NAT-PT), which was deprecated by RFC 4966, and to enable
networks to have IPv4 and IPv6 coexist in a somewhat rational manner
while transitioning to an IPv6 network.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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). Not all documents
approved by the IESG are 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/rfc6144.
Copyright Notice
Copyright (c) 2011 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. Code Components extracted from this document must
Baker, et al. Informational [Page 1]
RFC 6144 Framework for IPv4/IPv6 Translation April 2011
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Why Translation? . . . . . . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Translation Objectives . . . . . . . . . . . . . . . . . . 7
1.4. Transition Plan . . . . . . . . . . . . . . . . . . . . . 9
2. Scenarios for IPv4/IPv6 Translation . . . . . . . . . . . . . 11
2.1. Scenario 1: An IPv6 Network to the IPv4 Internet . . . . . 12
2.2. Scenario 2: The IPv4 Internet to an IPv6 Network . . . . . 13
2.3. Scenario 3: The IPv6 Internet to an IPv4 Network . . . . . 14
2.4. Scenario 4: An IPv4 Network to the IPv6 Internet . . . . . 15
2.5. Scenario 5: An IPv6 Network to an IPv4 Network . . . . . . 16
2.6. Scenario 6: An IPv4 Network to an IPv6 Network . . . . . . 17
2.7. Scenario 7: The IPv6 Internet to the IPv4 Internet . . . . 18
2.8. Scenario 8: The IPv4 Internet to the IPv6 Internet . . . . 19
3. Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1. Translation Components . . . . . . . . . . . . . . . . . . 19
3.1.1. Address Translation . . . . . . . . . . . . . . . . . 19
3.1.2. IP and ICMP Translation . . . . . . . . . . . . . . . 21
3.1.3. Maintaining Translation State . . . . . . . . . . . . 21
3.1.4. DNS64 and DNS46 . . . . . . . . . . . . . . . . . . . 22
3.1.5. ALGs for Other Applications Layer Protocols . . . . . 22
3.2. Operation Mode for Specific Scenarios . . . . . . . . . . 22
3.2.1. Stateless Translation . . . . . . . . . . . . . . . . 23
3.2.2. Stateful Translation . . . . . . . . . . . . . . . . . 24
3.3. Layout of the Related Documents . . . . . . . . . . . . . 26
4. Translation in Operation . . . . . . . . . . . . . . . . . . . 27
5. Unsolved Problems . . . . . . . . . . . . . . . . . . . . . . 28
6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8.1. Normative References . . . . . . . . . . . . . . . . . . . 29
8.2. Informative References . . . . . . . . . . . . . . . . . . 29
Baker, et al. Informational [Page 2]
RFC 6144 Framework for IPv4/IPv6 Translation April 2011
Show full document text