Deployment Considerations for Lightweight 4over6
draft-ietf-softwire-lightweight-4over6-deployment-01

Document Type Active Internet-Draft (softwire WG)
Last updated 2017-07-03
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             Q. Sun
Internet-Draft                                                    C. Xie
Intended status: Informational                             China Telecom
Expires: January 4, 2018                                          Y. Lee
                                                                 Comcast
                                                                 M. Chen
                                                                 FreeBit
                                                                   T. Li
                                                     Tsinghua University
                                                               I. Farrer
                                                     Deutsche Telekom AG
                                                            July 3, 2017

            Deployment Considerations for Lightweight 4over6
          draft-ietf-softwire-lightweight-4over6-deployment-01

Abstract

   Lightweight 4over6 is a mechanism for providing IPv4 services to
   clients connected to a single-stack IPv6 network.  The architecture
   is similar to DS-Lite, but the network address translation function
   is relocated from the tunnel concentrator to the tunnel client, hence
   reducing the amount of state which must be maintained in the
   concentrator to a per-customer level.  This document discusses the
   applicability, describes various deployment models and provides
   deployment considerations for Lightweight 4over6.

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 January 4, 2018.

Sun, et al.              Expires January 4, 2018                [Page 1]
Internet-Draft        lightweight-4over6-deployment            July 2017

Copyright Notice

   Copyright (c) 2017 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.  Deployment Models . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Top-Down Deployment Model . . . . . . . . . . . . . . . .   4
     2.2.  Bottom-Up Deployment Model  . . . . . . . . . . . . . . .   5
     2.3.  Campus Deployment . . . . . . . . . . . . . . . . . . . .   5
   3.  Overall Deployment Considerations . . . . . . . . . . . . . .   5
     3.1.  IP Addressing and Routing . . . . . . . . . . . . . . . .   5
       3.1.1.  IPv4 Routing  . . . . . . . . . . . . . . . . . . . .   5
       3.1.2.  IPv6 Routing  . . . . . . . . . . . . . . . . . . . .   6
     3.2.  lwB4 Configuration  . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  DHCPv6 Based Provisioning . . . . . . . . . . . . . .   6
       3.2.2.  DHCPv4 over DHCPv6 Based Provisioning . . . . . . . .   7
       3.2.3.  PCP Based Provisioning  . . . . . . . . . . . . . . .   7
       3.2.4.  NETCONF/YANG Based Provisioning . . . . . . . . . . .   7
       3.2.5.  Other lwB4 Configuation Considerations  . . . . . . .   7
     3.3.  lwAFTR Discovery  . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Impacts on Accouting  . . . . . . . . . . . . . . . . . .   8
   4.  lwAFTR Deployment Considerations  . . . . . . . . . . . . . .   8
     4.1.  Logging at the lwAFTR . . . . . . . . . . . . . . . . . .   9
     4.2.  MTU and Fragmentation Considerations  . . . . . . . . . .   9
     4.3.  Reliability Considerations of lwAFTR  . . . . . . . . . .   9
     4.4.  Location of lwAFTRs in the Network  . . . . . . . . . . .  10
     4.5.  Path Consistency Consideration  . . . . . . . . . . . . .  10
   5.  lwB4 Deployment Considerations  . . . . . . . . . . . . . . .  11
Show full document text