draft-ietf-v6ops-ivi-icmp-address-02.txt   draft-ietf-v6ops-ivi-icmp-address-03.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: January 4, 2013 University Expires: January 12, 2013 University
D. Wing D. Wing
R. Vaithianathan R. Vaithianathan
Cisco Cisco
G. Huston G. Huston
APNIC APNIC
July 3, 2012 July 11, 2012
Stateless Source Address Mapping for ICMPv6 Packets Stateless Source Address Mapping for ICMPv6 Packets
draft-ietf-v6ops-ivi-icmp-address-02 draft-ietf-v6ops-ivi-icmp-address-03
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 that should containing non IPv4-translatable addresses as the source that should
be passed across the translator as an ICMP packet directed to the be passed across the translator as an ICMP packet directed to the
IPv4-translatable destination. This document presents IPv4-translatable destination. This document presents
recommendations for source address translation in ICMPv6 headers for recommendations for source address translation in ICMPv6 headers for
such cases. 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 January 4, 2013. This Internet-Draft will expire on January 12, 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 3, line 23 skipping to change at page 3, line 23
work." This document presents recommendations for this case. work." This document presents recommendations for this case.
2. Notational Conventions 2. Notational Conventions
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in [RFC2119]. document, are to be interpreted as described in [RFC2119].
3. Problem Statement and Considerations 3. Problem Statement and Considerations
When a stateless IPv4/IPv6 translator receives an ICMPv6 message (for When a stateless IPv4/IPv6 translator receives an ICMPv6 message
example "Packet Too Big") sourced from an non-IPv4-translatable IPv6 [RFC4443] (for example "Packet Too Big") sourced from an non-IPv4-
address, directed to an IPv4-translatable IPv6 address, it needs to translatable IPv6 address, directed to an IPv4-translatable IPv6
generate an ICMP message. For the reasons discussed below, choosing address, it needs to generate an ICMP message. For the reasons
the source IPv4 address of this ICMP message is problematic. discussed below, choosing the source IPv4 address of this ICMP
message is problematic.
The address used should not cause the ICMP packet to be a candidate The address used should not cause the ICMP packet to be a candidate
for discarding, particularly in the contest of uRPF filters for discarding, particularly in the contest of uRPF filters
[RFC3704]. This consideration precludes the use of private IPv4 [RFC3704]. This consideration precludes the use of private IPv4
address space [RFC1918] in this context. address space [RFC1918] in this context.
It is also a consideration that the IPv4/IPv6 translation is intended It is also a consideration that the IPv4/IPv6 translation is intended
for use in contexts where IPv4 addresses may not be readily for use in contexts where IPv4 addresses may not be readily
available, so it is not considered to be appropriate to use IPv4- available, so it is not considered to be appropriate to use IPv4-
translatable IPv6 addresses for all internal points in the IPv6 translatable IPv6 addresses for all internal points in the IPv6
 End of changes. 5 change blocks. 
9 lines changed or deleted 10 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/