Stateless Source Address Mapping for ICMPv6 Packets
draft-ietf-v6ops-ivi-icmp-address-03

The information below is for an old version of the document
Document Type Active Internet-Draft (v6ops WG)
Last updated 2012-08-21 (latest revision 2012-07-10)
Replaces draft-xli-v6ops-ivi-icmp-address
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Document shepherd Fred Baker
IESG IESG state AD Evaluation::Revised I-D Needed
Telechat date
Responsible AD Ron Bonica
IESG note Fred Baker (fred@cisco.com) is the document shepherd.
Send notices to v6ops-chairs@tools.ietf.org, draft-ietf-v6ops-ivi-icmp-address@tools.ietf.org
Network Working Group                                              X. Li
Internet-Draft                                                    C. Bao
Intended status: BCP                              CERNET Center/Tsinghua
Expires: January 12, 2013                                     University
                                                                 D. Wing
                                                        R. Vaithianathan
                                                                   Cisco
                                                               G. Huston
                                                                   APNIC
                                                           July 11, 2012

          Stateless Source Address Mapping for ICMPv6 Packets
                  draft-ietf-v6ops-ivi-icmp-address-03

Abstract

   A stateless IPv4/IPv6 translator may receive ICMPv6 packets
   containing non IPv4-translatable addresses as the source that should
   be passed across the translator as an ICMP packet directed to the
   IPv4-translatable destination.  This document presents
   recommendations for source address translation in ICMPv6 headers for
   such cases.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 12, 2013.

Copyright Notice

   Copyright (c) 2012 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

Li, et al.              Expires January 12, 2013                [Page 1]
Internet-Draft      Source Address Mapping for ICMPv6          July 2012

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . . . 3
   3.  Problem Statement and Considerations  . . . . . . . . . . . . . 3
   4.  ICMP Extension  . . . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Stateless Address Mapping Algorithm . . . . . . . . . . . . . . 4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
   9.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5

Li, et al.              Expires January 12, 2013                [Page 2]
Internet-Draft      Source Address Mapping for ICMPv6          July 2012

1.  Introduction

   The IP/ICMP translation document of IPv4/IPv6 translation [RFC6145]
   states that "the IPv6 addresses in the ICMPv6 header may not be IPv4-
   translatable addresses and there will be no corresponding IPv4
   addresses represented of this IPv6 address.  In this case, the
   translator can do stateful translation.  A mechanism by which the
   translator can instead do stateless translation is left for future
   work."  This document presents recommendations for this case.

2.  Notational Conventions

   The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
   document, are to be interpreted as described in [RFC2119].

3.  Problem Statement and Considerations

   When a stateless IPv4/IPv6 translator receives an ICMPv6 message
   [RFC4443] (for example "Packet Too Big") sourced from an non-IPv4-
   translatable IPv6 address, directed to an IPv4-translatable IPv6
   address, it needs to generate an ICMP message.  For the reasons
Show full document text