IP/ICMP Translation Algorithm
RFC 7915
| Document | Type |
RFC - Proposed Standard
(June 2016; Errata)
Obsoletes RFC 6145
Was draft-bao-v6ops-rfc6145bis (individual)
|
|
|---|---|---|---|
| Last updated | 2016-10-05 | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Fred Baker | ||
| Shepherd write-up | Show (last changed 2016-01-21) | ||
| IESG | IESG state | RFC 7915 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) C. Bao
Request for Comments: 7915 X. Li
Obsoletes: 6145 CERNET Center/Tsinghua University
Category: Standards Track F. Baker
ISSN: 2070-1721 Cisco Systems
T. Anderson
Redpill Linpro
F. Gont
Huawei Technologies
June 2016
IP/ICMP Translation Algorithm
Abstract
This document describes the Stateless IP/ICMP Translation Algorithm
(SIIT), which translates between IPv4 and IPv6 packet headers
(including ICMP headers). This document obsoletes RFC 6145.
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 7841.
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/rfc7915.
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.
Bao, et al. Standards Track [Page 1]
RFC 7915 IPv4/IPv6 Translation June 2016
Table of Contents
1. Introduction and Motivation . . . . . . . . . . . . . . . . . 3
1.1. IPv4-IPv6 Translation Model . . . . . . . . . . . . . . . 3
1.2. Applicability and Limitations . . . . . . . . . . . . . . 3
1.3. Stateless vs. Stateful Mode . . . . . . . . . . . . . . . 4
1.4. Path MTU Discovery and Fragmentation . . . . . . . . . . 5
2. Changes from RFC 6145 . . . . . . . . . . . . . . . . . . . . 5
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Translating from IPv4 to IPv6 . . . . . . . . . . . . . . . . 6
4.1. Translating IPv4 Headers into IPv6 Headers . . . . . . . 7
4.2. Translating ICMPv4 Headers into ICMPv6 Headers . . . . . 9
4.3. Translating ICMPv4 Error Messages into ICMPv6 . . . . . . 13
4.4. Generation of ICMPv4 Error Message . . . . . . . . . . . 14
4.5. Transport-Layer Header Translation . . . . . . . . . . . 14
4.6. Knowing When to Translate . . . . . . . . . . . . . . . . 15
5. Translating from IPv6 to IPv4 . . . . . . . . . . . . . . . . 15
5.1. Translating IPv6 Headers into IPv4 Headers . . . . . . . 17
5.1.1. IPv6 Fragment Processing . . . . . . . . . . . . . . 19
5.2. Translating ICMPv6 Headers into ICMPv4 Headers . . . . . 19
5.3. Translating ICMPv6 Error Messages into ICMPv4 . . . . . . 22
5.4. Generation of ICMPv6 Error Messages . . . . . . . . . . . 23
5.5. Transport-Layer Header Translation . . . . . . . . . . . 23
5.6. Knowing When to Translate . . . . . . . . . . . . . . . . 24
6. Mapping of IP Addresses . . . . . . . . . . . . . . . . . . . 24
7. Special Considerations for ICMPv6 Packet Too Big . . . . . . 24
8. Security Considerations . . . . . . . . . . . . . . . . . . . 24
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1. Normative References . . . . . . . . . . . . . . . . . . 25
9.2. Informative References . . . . . . . . . . . . . . . . . 27
Appendix A. Stateless Translation Workflow Example . . . . . . . 30
A.1. H6 Establishes Communication with H4 . . . . . . . . . . 30
A.2. H4 Establishes Communication with H6 . . . . . . . . . . 32
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
Bao, et al. Standards Track [Page 2]
RFC 7915 IPv4/IPv6 Translation June 2016
Show full document text