idnits 2.17.1 draft-yang-v6ops-ipv6tran-select-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 2, 2015) is 3215 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force T. Yang 3 Internet-Draft L. Li 4 Intended status: Informational Q. Ma 5 Expires: Jan 2, 2016 China Mobile 6 July 2, 2015 8 Scenario of IPv6 Transition Technologies Selection 9 draft-yang-v6ops-ipv6tran-select-03 11 Abstract 13 Many IPv6 transition technologies has been proposed, such 14 as Dual-Stack, 6rd and so on. An CPE may support some of 15 them instead of only one. But the ISPs always support different kinds 16 of transition technologies. So they must control all the CPEs to 17 match the exact transition tech through the CPEs' management system 18 or configuring them before issuing to the customers. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on Jan 2, 2016 37 Copyright Notice 39 Copyright (c) 2013 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Problem Statement . . . . . . . . . . . . . . . .. . . . . . . 2 55 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1. Problem Statement 60 Nowadays, many IPv6 transitioning technologies has been proposed such 61 as Dual-Stack, DS-Lite, 6rd and so on. Each of them proposes 62 individual requirment to the CPEs. To promote the competitive 63 ability of products,the CPE manufacturers certainly will try to 64 support more technologies as much as possible. Meanwhile, the 65 operators tend to use single or less technologies. Moreover, users 66 can buy and use their own equipments instead of using the one which 67 operator gives them, that will bring the diversity of CPEs. 69 Assume that an operator uses one or more transitioning strategies in its 70 network. There are two ways to make the CPEs available. The first 71 one is to make a pre-configuration for each CPE in advance. But, 72 when the users modify the configuration or change to their own 73 equipment, the connection will fail. The Second method is to deploy 74 Network Management System (NMS) to configurate all the CPEs. Various 75 CPEs from different manufactories usually need different NMS which 76 means either the operator needs to maintains multiple NMS in their 77 network or operator can only use one manufacturer's product in a 78 subnet. What's worse, when users buy and use their own CPE instead 79 of using the original one, there will be no any solutions to 80 configurate correctly except visiting service. 82 Some specific messages need to be define between CPE and DHCP Server 83 to communicate the IPv6 transition technologies. 85 +----------------------+ 86 | ISP network | 87 | | 88 +-----+ | +-------+ | 89 | CPE |----------| BRAS | | 90 +-----+ | +-------+ | 91 | | 92 | | 93 +----------------------+ 94 Figure1 IPv6 trans tech configuration Scenario 95 2. Security Considerations 97 The security problem is under disscussion. 99 Authors' Addresses 101 Tianle Yang 102 China Mobile 103 32, Xuanwumenxi Ave. 104 Xicheng District, Beijing 100053 105 China 107 Email: yangtianle@chinamobile.com 109 Li Lianyuan 110 China Mobile 111 32, Xuanwumenxi Ave. 112 Xicheng District, Beijing 100053 113 China 115 Email: lilianyuan@chinamobile.com 117 Qiongfang Ma 118 China Mobile 119 32, Xuanwumenxi Ave. 120 Xicheng District, Beijing 100053 121 China 123 Email: maqiongfang@chinamobile.com