[v4tov6transition] ISP support of Native IPv6 across NAT44 CPEs - Proposed 6a44 Specification

[Rémi Després <[e-mail]>]

Hi all,

Draft-despres-softwire-6a44-00, coauthored with Brian and Sheng, has just been posted (http://tools.ietf.org/html/draft-despres-softwire-6a44-00).
It describes a solution for ISPs to offer native IPv6 across IPv4-only CPEs (NAT44 CPEs).

It results from convergence discussion between authors of draft-carpenter-6man-sample-00 and draft-despres-softwire-6rdplus-00, taking into account comments made by authors of draft-lee-softwire-6rd-udp-01, and those made other Softwire WG participants since IETF 78.

It is submitted to become, after discussion in the WG, a Softwire I-D.

Regards,
RD 



Internet Engineering Task Force                               R. Despres
Internet-Draft                                                 RD-IPtech
Intended status: Standards Track                            B. Carpenter
Expires: April 8, 2011                                 Univ. of Auckland
                                                                S. Jiang
                                            Huawei Technologies Co., Ltd
                                                         October 5, 2010


                  Native IPv6 Across NAT44 CPEs (6a44)
                     draft-despres-softwire-6a44-00

Abstract

   Most CPEs should soon be dual stack, but a large installed base of
   IPv4-only CPEs is likely to remain for several years.  Also, with the
   IPv4 address shortage, more and more ISPs will assign private IPv4
   addresses to their customers.  The need for IPv6 connectivity
   therefore concerns hosts behind IPv4-only CPEs, including such CPEs
   that are assigned private addresses.  The 6a44 mechanism specified in
   this document addresses this need, without limitations and
   operational complexities of Tunnel Brokers and Teredo to do the same.

   6a44 is based on an address mapping and on a mechanism whereby
   suitably upgraded hosts behind a NAT may obtain IPv6 connectivity via
   a stateless 6a44 server function operated by their Internet Service
   Provider.  With it, traffic between two 6a44 hosts in a single site
   remains within the site.  Except for IANA numbers that remain to be
   assigned, the specification is intended to be complete enough for
   running codes to be independently written and interwork.

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 April 8, 2011.




Despres, et al.           Expires April 8, 2011                 [page 1]

Internet-Draft    Native IPv6 behind NAT44 CPEs (6a44)      October 2010


Copyright Notice

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


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  6a44 IPv6 Address Format . . . . . . . . . . . . . . . . . . .  6
   4.  Address Mappings and Encapsulations  . . . . . . . . . . . . .  8
   5.  MTU considerations . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Host Acquisition of IPv6 Addresses and their Lifetimes . . . . 10
   7.  Security considerations  . . . . . . . . . . . . . . . . . . . 13
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     10.1.  Normative References  . . . . . . . . . . . . . . . . . . 15
     10.2.  Informative References  . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16