Softwire Wei Mi, Ed. Internet-Draft Jingguo Ge Intended status: Informational CNIC/Chinese Academy of Sciences Expires: June 29, 2015 December 26, 2014 The Applicability Index of IPv4/IPv6 Encapsulation draft-mi-softwire-applicable-index-encapsulation-00 Abstract The Softwire working group is currently discussing both encapsulation and translation based stateless IPv4/IPv6 solutions in order to be able to provide IPv4 connectivity to customers in an IPv6-Only environment. The purpose of this document is to describe the basic issues and key elements of the IPv4/IPv6 encapsulation, and presents its applicability index that would help the operators decide on the development scheme for their IPv6 transition.It could lead to significant operational benefits and potential savings for the operators. 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 June 29, 2015. 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 Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 1] Internet-Draft December 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 2. The Basic Issues and Key elements of Encapsulation Mechanisms 3 2.1. Basic Issues . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Key Elements . . . . . . . . . . . . . . . . . . . . . . 3 3. Applicability Index of Encapsulation . . . . . . . . . . . . 4 3.1. Sustainable Index . . . . . . . . . . . . . . . . . . . . 4 3.2. The Support Degree of Business Application Index . . . . 4 3.3. The Preformance Index . . . . . . . . . . . . . . . . . . 4 3.4. The Development Index . . . . . . . . . . . . . . . . . . 5 3.5. The Security Index . . . . . . . . . . . . . . . . . . . 5 4. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 8. Informative References . . . . . . . . . . . . . . . . . . . 6 1. Introduction The Softwire working group is currently discussing both encapsulation and translation based stateless IPv4/IPv6 solutions developed for the purposes of offering IPv4 connectivity to the customers in an IPv6-Only environment. Generic mechanism for IPv4/IPv6 encapsulation mechanismsare specified in [RFC2529], [RFC3056], [RFC4380], [RFC4659], [RFC5214], [RFC5569], [RFC5747], [RFC6333], [RFC7040], etc. With the diverse characteristics and transition requirements of practical networks and the lack of overall transition architecture, the selection and deployment of IPv6 transition mechanisms are very difficult. In an effort to push forward the IPv6 transition process, this document describles the basic issues and key elements of encapsulation mechanisms, and presents the applicability index that would help the operators decide on the development scheme for their IPv6 transition.It could lead to significant operational benefits and potential savings for the operators. Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 2] Internet-Draft December 2014 2. The Basic Issues and Key elements of Encapsulation Mechanisms Encapsulation mechanisms can achieve communications between IPv6 networks/hosts across an IPv4 network (IPv6-over-IPv4), and communications between IPv4 networks/hosts across an IPv6 network (IPv4-over-IPv6). 2.1. Basic Issues Its basic operations include encapsulation/de-encapsulation and route discovery between tunnel endpoints. Encapsulationoperation only affect the network layer: a. The basic data operation Encapsulation/de-encapsulation is the basic data plane operation. For IPv6 transition usage, the encapsulation manners such as IP-IP, GRE (Generic Routing Encapsulation) L2TP (Layer Two Tunneling Protocol), MPLS (Multiple protocol Label Switching), IPsec (Internet Protocol Security) can all be adopted.For a wide selection, network operator can make the decision to select suitable transition mechanism. b. The basic control operation The basic control plane operations include the routing interaction across heterogeneous network, the route discovery between tunnel endpoints, and the encapsulation address mapping by a particular address scheme or address/prefix binding. 2.2. Key Elements a. Transition equipment In encapsulation mechanisms, the tunnel endpoints are the transition equipments. They need to support dual-stack which can be an AFBR (Address Family Border Router) or host equipments. They should support encapsulation/ deencapsulation and routing forward across heterogeneous network and the route discovery between tunnel endpoints. They also maintain the encapsulation address mapping by a particular address scheme or address/prefix binding. Thus, the tunnel transition equipment has requirements in the use of bandwidth, computing and finding, storage. b. Encapsulation/de-encapsulation Encapsulation makes the IPv4/IPv6 packet as a payload of the other IP protocol. It retains the integrity of IP packet information. But it adds the size of packet and may create the fragment reassembly problem. c. The routing across heterogeneous networks Encapsulation mechanisms need to support the routing forward across Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 3] Internet-Draft December 2014 heterogeneous networks. And the border routers should maintain the binding and realizes the transparent data transmission. Thus, encapsulation is stateless and lightweight. d. The routing discovery between tunnel endpoints In encapsulation mechanisms, the tunnel endpoints need to discover each other. And it involves some problems, such as the selection and dynamic or static configuration of tunnel endpoint, state maintenance. 3. Applicability Index of Encapsulation There are applicability index which need to be analyzed by the operator when choosing which transition technology option they would like to deploy. The applicability index in terms of sustainable, applications, performance and development. This section describes some of those considerations. 3.1. Sustainable Index Sustainable index would include: a. The scenarios and function of transition represents whether meet the needs of transitional scenario. b. Both (a)the coupling degree between IPv4 address and (b) IPv6 address and the reuse rate of IPv4 addresses resource represent whether promote the deployment and usage of IPv6. 3.2. The Support Degree of Business Application Index The support degree of business application index would include: a. The support degree of IPv4 application represents the impact on the IPv4 business application. b. The support degree of IPv6 application represents the impact on the IPv6 business application. 3.3. The Preformance Index The preformance index would include: a. The performance requirements of tunnel endpoint can be divided into (a)The maintenance and finding of state or mapping table and (b) the routing discovery, which represents the capacity of bandwidth, computing and finding, storage. Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 4] Internet-Draft December 2014 b. The routing scalability can be divided into (a) the independence between IPv4 and IPv6 routing and (b) the aggregation of IPv6 addresses, which represents the impact on the scope of deployment. c. Robustness represents the capacity of redundancy backup. 3.4. The Development Index The cost of development index would include: a. Technological and industry maturity represent the support degree of standard. b. The update cost can be divided into (a) the impact on application layer, (b) the impact on network layerand and (c) the impact on end users layer, which represent the impact on the present network. c. The cost of operation, management and maintenance represent the impact on the operator. d. The problem of fragmentation and restructuring. 3.5. The Security Index The security index includes the security issues and concerns. 4. Conclusions For the consideration of deployment scenarios and address format, numerous encapsulation transition mechanisms have been proposed in the past ten years. However, due to a wide range of mechanisms and a lot of overlap and similar functions, no one encapsulation mechanism can be used in all transition scenarios. The applicability index of IPv4/IPv6 encapsulation described in this document have highlighted the applicability of all encapsulation transition mechanisms to help the operators decide on the development scheme for their IPv6 transition. 5. Acknowledgements 6. IANA Considerations This memo includes no request to IANA. Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 5] Internet-Draft December 2014 7. Security Considerations All drafts are required to have a security considerations section. 8. Informative References [RFC2529] Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 Domains without Explicit Tunnels", RFC 2529, March 1999. [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001. [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006. [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, "BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN", RFC 4659, September 2006. [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 2008. [RFC5569] Despres, R., "IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)", RFC 5569, January 2010. [RFC5747] Wu, J., Cui, Y., Li, X., Xu, M., and C. Metz, "4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions", RFC 5747, March 2010. [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion", RFC 6333, August 2011. [RFC7040] Cui, Y., Wu, J., Wu, P., Vautrin, O., and Y. Lee, "Public IPv4-over-IPv6 Access Network", RFC 7040, November 2013. Authors' Addresses Wei Mi (editor) CNIC/Chinese Academy of Sciences 4 South 4th Street, Zhongguancun Beijing 100190 CN Phone: +86 10-58812931 EMail: miwei@cstnet.cn Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 6] Internet-Draft December 2014 Jingguo Ge CNIC/Chinese Academy of Sciences 4 South 4th Street, Zhongguancun Beijing 100190 CN Phone: +86 10-58813817 EMail: gejingguo@cstnet.cn Wei Mi & Jingguo Ge Expires June 29, 2015 [Page 7]