datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

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

Document type: Active Internet-Draft (softwire WG)
Document stream: IETF
Last updated: 2014-10-30 (latest revision 2014-10-12)
Intended RFC status: Experimental
Other versions: plain text, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Yes
Document shepherd: Suresh Krishnan
Shepherd Write-Up: Last changed 2014-07-23

IESG State: IESG Evaluation::Revised I-D Needed
IANA Review State: IANA OK - Actions Needed
IANA Action State: None
(Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.)
Responsible AD: Ted Lemon
Send notices to: softwire-chairs@tools.ietf.org, draft-ietf-softwire-4rd@tools.ietf.org

Internet Engineering Task Force                               R. Despres
Internet-Draft                                                 RD-IPtech
Intended status: Experimental                              S. Jiang, Ed.
Expires: April 15, 2015                     Huawei Technologies Co., Ltd
                                                                R. Penno
                                                     Cisco Systems, Inc.
                                                                  Y. Lee
                                                                 Comcast
                                                                 G. Chen
                                                            China Mobile
                                                                 M. Chen
                                                        Freebit Co, Ltd.
                                                        October 12, 2014

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

Abstract

   For service providers to progressively deploy IPv6-only network
   domains while still offering IPv4 service to customers, this document
   specifies a stateless solution.  Its distinctive property is that
   TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during domain
   traversal, and that IPv4 fragmentation rules are fully preserved end-
   to-end.  Each customer can be assigned one public IPv4 address, or
   several, or a shared address with a restricted port set.

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 15, 2015.

Despres, et al.          Expires April 15, 2015                 [Page 1]
Internet-Draft  Stateless IPv4 Residual Deployment (4rd)    October 2014

Copyright Notice

   Copyright (c) 2014 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  The 4rd Model . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Protocol Specifications . . . . . . . . . . . . . . . . . . .   8
     4.1.  NAT44 on CE . . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Mapping rules and other Domain parameters . . . . . . . .   8
     4.3.  Reversible Packet Translations at Domain entries and
           exits . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.4.  Address Mapping from CE IPv6 Prefixes to 4rd IPv4
           prefixes  . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.5.  Address Mapping from 4rd IPv4 addresses to 4rd IPv6
           Addresses . . . . . . . . . . . . . . . . . . . . . . . .  16
     4.6.  Fragmentation Processing  . . . . . . . . . . . . . . . .  21
       4.6.1.  Fragmentation at Domain Entry . . . . . . . . . . . .  21
       4.6.2.  Ports of Fragments addressed to Shared-Address CEs  .  21
       4.6.3.  Packet Identifications from Shared-Address CEs  . . .  22
     4.7.  TOS and Traffic-Class Processing  . . . . . . . . . . . .  23
     4.8.  Tunnel-Generated ICMPv6 Error Messages  . . . . . . . . .  23
     4.9.  Provisioning 4rd Parameters to CEs  . . . . . . . . . . .  24
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  27
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
   7.  Relationship with Previous Works  . . . . . . . . . . . . . .  28
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  29
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  30

[include full document text]