IPv4 Residual Deployment via IPv6 - a unified Stateless Solution (4rd)
draft-ietf-softwire-4rd-00

The information below is for an old version of the document
Document Type Active Internet-Draft (softwire WG)
Last updated 2012-05-21
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                          R. Despres, Ed.
Internet-Draft                                                 RD-IPtech
Expires: November 17, 2012                                      R. Penno
                                                     Cisco Systems, Inc.
                                                                  Y. Lee
                                                                 Comcast
                                                                 G. Chen
                                                            China Mobile
                                                                S. Jiang
                                            Huawei Technologies Co., Ltd
                                                            May 16, 2012

 IPv4 Residual Deployment via IPv6 - a unified Stateless Solution (4rd)
                       draft-ietf-softwire-4rd-00

Abstract

   The 4rd automatic tunneling mechanism makes IPv4 Residual Deployment
   possible via IPv6 networks without maintaining for this per-customer
   states in 4rd-capable nodes (reverse of the IPv6 Rapid Deployment of
   6rd).  To cope with the IPv4 address shortage, customers can be
   assigned IPv4 addresses with restricted port sets.  In some
   scenarios, 4rd-capable customer nodes can exchange packets of their
   IPv4-only applications via stateful NAT64s that are upgraded to
   support 4rd tunnels (in addition to their IP/ICMP translation of
   [RFC6145]).

Status of this Memo

   This Internet-Draft is submitted 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 November 17, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Despres, et al.         Expires November 17, 2012               [Page 1]
Internet-Draft  Stateless IPv4 Residual Deployment (4rd)        May 2012

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  The 4rd Model  . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Protocol Specification . . . . . . . . . . . . . . . . . . . .  7
     4.1.  Mapping rules and other Domain parameters  . . . . . . . .  7
     4.2.  Reversible Packet Translations at Domain entries and
           exits  . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.3.  From CE IPv6 Prefixes to 4rd IPv4 prefixes . . . . . . . . 13
     4.4.  From 4rd IPv4 addresses to 4rd IPv6 Addresses  . . . . . . 15
     4.5.  Fragmentation Considerations . . . . . . . . . . . . . . . 19
       4.5.1.  Fragmentation at Domain Entry  . . . . . . . . . . . . 19
       4.5.2.  Ports of Fragments addressed to Shared-Address CEs . . 20
       4.5.3.  Packet Identifications from Shared-Address CEs . . . . 21
     4.6.  TOS and Traffic-Class Considerations . . . . . . . . . . . 22
     4.7.  Tunnel-Generated ICMPv6 Error Messages . . . . . . . . . . 22
     4.8.  Provisioning 4rd Parameters to CEs . . . . . . . . . . . . 23
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 26
   7.  Relationship with Previous Works . . . . . . . . . . . . . . . 26
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 28
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 29
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 30
   Appendix A.  Textual representation of Mapping rules . . . . . . . 32
   Appendix B.  Configuring multiple Mapping Rules  . . . . . . . . . 33
   Appendix C.  ADDING SHARED IPv4 ADDRESSES TO AN IPv6 NETWORK . . . 35
     C.1.  With CEs within CPEs . . . . . . . . . . . . . . . . . . . 35
Show full document text