Internet Engineering Task Force                                   D. Hui
Internet-Draft                                                    H. Min
Intended status: Informational                              China Monile
Expires: Jan 3, 2016                                        July 6, 2015
                                                            


              IPv6 Transition Technologies Selection in NFV
               draft-hui-v6ops-ipv6trans-select-nfv-00.txt


Abstract

   Nowadays, many IPv6 transition technologies have been proposed, such
   as Dual-Stack, 6rd and so on.  A CPE may support some of them 
   instead of only one.  But the ISPs always support different kinds of
   transition technologies, such as Dual-Stack, DS-lite and so on.  So
   they must control all the CPEs to match the exact transition tech
   through some standard messages. When the ISP network uses NFV, the 
   message communication will between the network gateway and the V-CPE
   to configure the IPv6 transition technology in CPE.

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 Jan 3, 2016.

Copyright Notice

   Copyright (c) 2015 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
   
Hui                  Expires Jan 3, 2016                        [Page 1]

Internet-Draft            ipv6trans-select-nfv                 July 2015


   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. Problem Statement	.............................................. 2
   2. Security Considerations	........................................ 3
   3. IANA Considerations	............................................ 3

1.  Problem Statement
   Nowadays, many IPv6 transitioning technologies has been proposed such
   as Dual-Stack, DS-Lite, 6rd and so on.  Each of them proposes 
   individual requirement to the CPEs.  To promote the competitive 
   ability of products, the CPE manufacturers certainly will try to 
   support more technologies as much as possible.  Meanwhile, the 
   operators tend to use single or less technologies.  Moreover, users 
   can buy and use their own equipments instead of using the one which 
   operator gives them, that will bring the diversity of CPEs.
   
   Assume that an operator uses one or more transitioning strategies in 
   its NFV network.  There are two ways to make the CPEs available.  
   The first one is to make a pre-configuration for each CPE in advance.
   But, when the users modify the configuration or change to their own 
   equipment, the connection will fail.  The Second method is to deploy
   Network Management System (NMS) to configure all the CPEs.  Various 
   CPEs from different manufactories usually need different NMS which 
   means either the operator needs to maintain multiple NMS in their 
   network or operator can only use one manufacturer's product in a 
   subnet.  What's worse, when users buy and use their own CPE instead 
   of using the original one, there will be no any solutions to 
   configure correctly except visiting service.
   
   NFV makes the vCPE to control the CPE, so we need some messages to 
   configure the IPv6 transition tech between network gateway and vCPE.
   
         +----------------------+
         |         NFV cloud    |
         |                      |
+-----+  |  +-------+  +------+ | +------+
| CPE |-----| vCPE  |--|vBRAS |---| CGNAT|
+-----+  |  +-------+  +------+ | +------+
         |                      |
         |                      |
         +----------------------+
Figure1 NFV IPv6 trans tech configuration architecture





Hui                  Expires Jan 3, 2016                        [Page 2]

Internet-Draft            ipv6trans-select-nfv                 July 2015


2. Security Considerations

   TBD
   
3. IANA Considerations

   TBD
 
Authors' Addresses

   Hui Deng
   China Mobile

   Email: denghui@chinamobile.com


   Min Hui
   China Mobile
   Email: huimin@chinamobile.com
































Hui                  Expires Jan 3, 2016                        [Page 3]