draft-ietf-v6ops-ivi-icmp-address-04.txt   draft-ietf-v6ops-ivi-icmp-address-05.txt 
Network Working Group X. Li Network Working Group X. Li
Internet-Draft C. Bao Internet-Draft C. Bao
Intended status: BCP CERNET Center/Tsinghua Intended status: BCP CERNET Center/Tsinghua
Expires: March 9, 2013 University Expires: March 10, 2013 University
D. Wing D. Wing
R. Vaithianathan R. Vaithianathan
Cisco Cisco
G. Huston G. Huston
APNIC APNIC
September 5, 2012 September 6, 2012
Stateless Source Address Mapping for ICMPv6 Packets Stateless Source Address Mapping for ICMPv6 Packets
draft-ietf-v6ops-ivi-icmp-address-04 draft-ietf-v6ops-ivi-icmp-address-05
Abstract Abstract
A stateless IPv4/IPv6 translator may receive ICMPv6 packets A stateless IPv4/IPv6 translator may receive ICMPv6 packets
containing non IPv4-translatable addresses as the source. These containing non IPv4-translatable addresses as the source. These
packets should be passed across the translator as ICMP packets packets should be passed across the translator as ICMP packets
directed to the IPv4 destination. This document presents directed to the IPv4 destination. This document presents
recommendations for source address translation in ICMPv6 headers to recommendations for source address translation in ICMPv6 headers to
handle such cases. handle such cases.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 9, 2013. This Internet-Draft will expire on March 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3. Problem Statement and Considerations . . . . . . . . . . . . . 3 3. Problem Statement and Considerations . . . . . . . . . . . . . 3
3.1. Considerations . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Recommendations . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Recommendations . . . . . . . . . . . . . . . . . . . . . . 4
4. ICMP Extension . . . . . . . . . . . . . . . . . . . . . . . . 4 4. ICMP Extension . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Stateless Address Mapping Algorithm . . . . . . . . . . . . . . 4 5. Stateless Address Mapping Algorithm . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . . 5 9.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
[RFC6145] section 5.2 of the "IP/ICMP Translation Algorithm" [RFC6145] section 5.2 of the "IP/ICMP Translation Algorithm"
document. states that "the IPv6 addresses in the ICMPv6 header may document. states that "the IPv6 addresses in the ICMPv6 header may
not be IPv4-translatable addresses and there will be no corresponding not be IPv4-translatable addresses and there will be no corresponding
IPv4 addresses representing this IPv6 address. In this case, the IPv4 addresses representing this IPv6 address. In this case, the
translator can do stateful translation. A mechanism by which the translator can do stateful translation. A mechanism by which the
translator can instead do stateless translation is left for future translator can instead do stateless translation is left for future
skipping to change at page 4, line 37 skipping to change at page 4, line 37
the origin rather than simply blackholing at or beyond the the origin rather than simply blackholing at or beyond the
translator. In the future, a new ICMP extension whose presence translator. In the future, a new ICMP extension whose presence
indicates that the packet has been translated and that the source indicates that the packet has been translated and that the source
address belongs to the translator, not the originating node can also address belongs to the translator, not the originating node can also
be considered. be considered.
5. Stateless Address Mapping Algorithm 5. Stateless Address Mapping Algorithm
If a pool of public IPv4 addresses is configured on the translator, If a pool of public IPv4 addresses is configured on the translator,
it is RECOMMENDED to randomly select the IPv4 source address from the it is RECOMMENDED to randomly select the IPv4 source address from the
pool. This can superficially avoid the appearance of a routing loop pool. This can somehow avoid the appearance of a routing loop in
in tools unaware of the ICMP extension such as traceroute. An tools unaware of the ICMP extension such as traceroute, even though
enhanced traceroute application is RECOMMENDED in order to obtain the those addresses do not really show the actual topology apart from the
IPv6 source addresses which generated the ICMPv6 messages. hop count. An enhanced traceroute application is RECOMMENDED in
order to obtain the IPv6 source addresses which generated the ICMPv6
messages.
6. Security Considerations 6. Security Considerations
This document recommends the generation of IPv4 ICMP messages from This document recommends the generation of IPv4 ICMP messages from
IPv6 ICMP messages. These messages would otherwise have been IPv6 ICMP messages. These messages would otherwise have been
discarded. It is not expected that new considerations result from discarded. It is not expected that new considerations result from
this change. As with a number of ICMP messages, a spoofed source this change. As with a number of ICMP messages, a spoofed source
address may result in replies arriving at hosts that did not expect address may result in replies arriving at hosts that did not expect
them using the facility of the translator. them using the facility of the translator.
 End of changes. 6 change blocks. 
9 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/