Mapping of Address and Port (MAP) - Deployment Considerations
draft-ietf-softwire-map-deployment-01

The information below is for an old version of the document
Document Type Active Internet-Draft (softwire WG)
Last updated 2013-02-25
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
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)
Network Working Group                                             Q. Sun
Internet-Draft                                             China Telecom
Intended status: Informational                                   M. Chen
Expires: August 29, 2013                                         FreeBit
                                                                 G. Chen
                                                            China Mobile
                                                                 T. Tsou
                                                     Huawei Technologies
                                                            S. Perreault
                                                                Viagenie
                                                       February 25, 2013

     Mapping of Address and Port (MAP) - Deployment Considerations
                 draft-ietf-softwire-map-deployment-01

Abstract

   This document describes when and how an operator uses the technique
   of Mapping of Address and Port (MAP) for the IPv4 residual deployment
   in the IPv6-dominant domain.

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 August 29, 2013.

Copyright Notice

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

Sun, et al.              Expires August 29, 2013                [Page 1]
Internet-Draft               MAP Deployment                February 2013

   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.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Case Studies . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Deployment Consideration . . . . . . . . . . . . . . . . . . .  6
     4.1.  Network Models . . . . . . . . . . . . . . . . . . . . . .  6
     4.2.  Building the MAP domain  . . . . . . . . . . . . . . . . .  7
       4.2.1.  MAP deployment model planning  . . . . . . . . . . . .  8
       4.2.2.  MAP domain planning  . . . . . . . . . . . . . . . . .  8
       4.2.3.  MAP rule provisioning  . . . . . . . . . . . . . . . .  9
       4.2.4.  MAP DHCPv6 server deployment consideration . . . . . . 10
       4.2.5.  PSID consideration . . . . . . . . . . . . . . . . . . 11
       4.2.6.  Addressing and routing . . . . . . . . . . . . . . . . 12
       4.2.7.  MAP vs. MAP-T vs. 4rd  . . . . . . . . . . . . . . . . 12
     4.3.  BR settings  . . . . . . . . . . . . . . . . . . . . . . . 13
     4.4.  CE settings  . . . . . . . . . . . . . . . . . . . . . . . 16
     4.5.  Supporting system  . . . . . . . . . . . . . . . . . . . . 17
   5.  MAP Address Planning . . . . . . . . . . . . . . . . . . . . . 19
     5.1.  Planning for Residual Deployment, a Step-by-step Guide . . 19
     5.2.  Remarks on Deployment Paradigms  . . . . . . . . . . . . . 21
   6.  Migration Methodology  . . . . . . . . . . . . . . . . . . . . 23
     6.1.  Roadmap for MAP-based Solution . . . . . . . . . . . . . . 23
       6.1.1.  Start from Scratch . . . . . . . . . . . . . . . . . . 23
       6.1.2.  Coexiting Phases . . . . . . . . . . . . . . . . . . . 23
       6.1.3.  Exit Strategy  . . . . . . . . . . . . . . . . . . . . 23
     6.2.  Migration Mode . . . . . . . . . . . . . . . . . . . . . . 24
       6.2.1.  Passive Transition . . . . . . . . . . . . . . . . . . 24
       6.2.2.  Active Transition  . . . . . . . . . . . . . . . . . . 24
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26
   9.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 27
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 28
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Show full document text