Explicit Address Mappings for Stateless IP/ICMP Translation
RFC 7757
| Document | Type |
RFC - Proposed Standard
(February 2016; No errata)
Updates RFC 6145
|
|
|---|---|---|---|
| Last updated | 2016-02-17 | ||
| Replaces | draft-anderson-v6ops-siit-eam | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Fred Baker | ||
| Shepherd write-up | Show (last changed 2015-08-11) | ||
| IESG | IESG state | RFC 7757 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - No Actions Needed | |
| IANA action state | No IC | ||
Internet Engineering Task Force (IETF) T. Anderson
Request for Comments: 7757 Redpill Linpro
Updates: 6145 A. Leiva Popper
Category: Standards Track NIC Mexico
ISSN: 2070-1721 February 2016
Explicit Address Mappings for Stateless IP/ICMP Translation
Abstract
This document extends the Stateless IP/ICMP Translation Algorithm
(SIIT) with an Explicit Address Mapping (EAM) algorithm and formally
updates RFC 6145. The EAM algorithm facilitates stateless IP/ICMP
translation between arbitrary (non-IPv4-translatable) IPv6 endpoints
and IPv4.
Status of This Memo
This is an Internet Standards Track document.
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). Further information on
Internet Standards is available in 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/rfc7757.
Copyright Notice
Copyright (c) 2016 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
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.
Anderson & Leiva Popper Standards Track [Page 1]
RFC 7757 SIIT Explicit Address Mappings February 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
3. Explicit Address Mapping Algorithm . . . . . . . . . . . . . 5
3.1. Explicit Address Mapping Table . . . . . . . . . . . . . 5
3.2. Explicit Address Mapping Specification . . . . . . . . . 6
3.3. IP Address Translation Procedure . . . . . . . . . . . . 6
3.3.1. Address Translation Steps: IPv4 to IPv6 . . . . . . . 7
3.3.2. Address Translation Steps: IPv6 to IPv4 . . . . . . . 7
4. Hairpinning of IPv6 Traffic . . . . . . . . . . . . . . . . . 8
4.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 8
4.2. Recommendation . . . . . . . . . . . . . . . . . . . . . 9
4.2.1. Simple Hairpinning Support . . . . . . . . . . . . . 9
4.2.2. Intrinsic Hairpinning Support . . . . . . . . . . . . 9
5. Overlapping Explicit Address Mappings . . . . . . . . . . . . 10
6. Lack of Checksum Neutrality . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. Use Cases . . . . . . . . . . . . . . . . . . . . . 14
A.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . . . 14
A.2. IVI . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
A.3. SIIT-DC . . . . . . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Example IP Address Translations . . . . . . . . . . 15
B.1. Hairpinning Examples . . . . . . . . . . . . . . . . . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction
The Stateless IP/ICMP Translation Algorithm (SIIT) [RFC6145]
specifies that when translating IPv4 addresses to IPv6 and vice
versa, all addresses must be translated using the algorithm specified
in [RFC6052]. This document specifies an alternative to the
algorithm specified in [RFC6052], where IP addresses are translated
according to a table of Explicit Address Mappings configured on the
stateless translator. This removes the previous constraint that IPv6
nodes that communicate with IPv4 nodes through SIIT must be
configured with IPv4-translatable IPv6 addresses.
Translation using the Explicit Address Mapping Table does not replace
[RFC6052]. For most use cases, it is expected that both algorithms
Show full document text