IPv4/IPv6 Coexistence Framework Prefixing/Encap/Translation (PET) draft-cui-softwire-pet-01 draft-cui-softwire-pet64-00 Yong Cui, Mingwei Xu, Shengling.

Slides:

Advertisements

Similar presentations

Stateless IPv4-IPv6 Interconnection for DS-lite and A+P Flexible IPv6 Migration Scenarios in the Context of IPv4 Address Shortage I-D.boucadair-behave-ipv6-portrange.

Advertisements

4V6 – stateless 4Via6 W. Dec R. Asati

Public IPv4 over Access IPv6 network draft-cui-softwire-host-4over6-06 draft-cui-softwire-dhcp-over-tunnel-01 Y. Cui, J. Wu, P. Wu Tsinghua Univ. C. Metz.

Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.

1 IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG

Introduction to IPv6 Network & Application Passakon Prathombutr Next Generation Internet (NGI) National Electronics and Computer Technology Center.

IPv4 - IPv6 Integration and Coexistence Strategies Warakorn Sae-Tang Network Specialist Professional Service Department A Subsidiary.

CPSC Network Layer4-1 IP addresses: how to get one? Q: How does a host get IP address? r hard-coded by system admin in a file m Windows: control-panel->network->configuration-

Halifax, 31 Oct – 3 Nov 2011 ICT Accessibility For All 4over6 technology for IPv6 transition Yong CUI CCSA (Tsinghua University) Document No: GSC16-PLEN-71.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Implementing IP Addressing Services Accessing the WAN – Chapter 7.

Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.

IPv6 Transition Technologies Yasuo Kashimura Senior Manager, Japan, APAC IPCC Alcatel-lucent.

For IPv4 Provisioning in IPv6 Network 1 Yong Cui, Jianping Wu, Peng Wu. Tsinghua Univ. (CERNET) Chris Metz. Cisco Systems Olivier Vautrin, Alain Durand.

Translation Spot Negotiation in IPv4/IPv6-Coexist Mesh draft-cui-softwire-pet-03 Yong Cui, Mingwei Xu, Peng Wu Jianping Wu, Xing Li, Chris Metz.

Notes for IPv6 Terrance Lee. Transition Mechanisms for IPv6 Hosts and Routers (RFC 2893)

Lightweight 4over6 in access network draft-cui-softwire-b4-translated-ds-lite-01 China Telecom: Chongfeng Xie, Qiong Sun Tsinghua University: Yong Cui,

Y. Cui, J. Wu, P. Wu Tsinghua Univ. C. Metz Cisco Systems O. Vautrin Juniper Networks Y. Lee Comcast Public IPv4 over Access IPv6 Network draft-cui-softwire-host-4over6-04.

IPv4/IPv6 Translation: Framework Li, Bao, and Baker.

IETF 79 th Considerations for Stateless Translation (IVI/dIVI) in Large SP draft-sunq-v6ops-ivi-sp-01 Qiong Sun( China Telecom) Heyu Wang( China Telecom)

IP/ICMP Translation Algorithm (IIT) Xing Li, Congxiao Bao, Fred Baker

1 IPv6 Address Management Rajiv Kumar. 2 Lecture Overview Introduction to IP Address Management Rationale for IPv6 IPv6 Addressing IPv6 Policies & Procedures.

NAT64 marcelo bagnulo, Philip Matthews, Iljitsch van Beijnum IETF 72 - Dublin.

Unified IPv6 Transition Framework With Flow-based Forwarding draft-cui-softwire-unified-v6-framework-00 Presenter: Cong Liu 1.

1 Solving the Softwire Mesh Problem Chris Metz, IETF Softwire WG Interim Meeting Hong Kong February 2006.

For IPv6 host connecting IPv4 Internet 1 Yong Cui, Jianping Wu Tsinghua Univ. (CERNET) Contact:

資管 Lee Lesson 11 Coexistence and Migration. 資管 Lee Lesson Objectives Coexistence and migration overview Coexistence mechanisms ◦ Dual Stack ◦ Tunneling.

RSIP Address Sharing with End-to-End Security Mike Borella, 3Com Corp. Gabriel Montenegro, Sun Microsystems March 2000.

CSE 8343 Group 3 Advanced OS Inter Operability Between IPv4 and IPv6 Team Members Aman Preet Singh Rohit Singh Nipun Aggarwal Chirag Shah Eugene Novak.

Coexistence and Migration

1 464XLAT Combination of Stateful and Stateless Translation draft-ietf-v6ops-464xlat-01 IETF 83 v6ops WG Japan Internet Exchange Co.,Ltd.

Lightweight 4over6 + SD-nat (aka stateless DS-Lite) = Lightweight DS-Lite (twice as light!) Alain Durand (Juniper) Ian Farrer (DT) (Softwire item, presented.

Implementing IP Addressing Services Accessing the WAN – Chapter 7.

IPv4/IPv6 transition experience and the features of stateless translation (IVI) Xing Li Plenary: Life after IPv4 Exhaustion.

IPv6 and IPv4 Coexistence Wednesday, October 07, 2015 IPv6 and IPv4 Coexistence Motorola’s Views for Migration and Co-existence of 3GPP2 Networks to Support.

IETF 73 / behave 1 Minneapolis / Gabor Bajko Randy Bush Rémi Després Pierre Levis Olaf Maennel Teemu Savolainen Port Range Proposals.

Sharing a single IPv4 address among many broadband customers

Two Dimensional IP Routing Architecture draft-xu-rtgwg-twod-ip-routing-00 Mingwei Xu, Jianping Wu, Shu Yang CERNET Dan Wang Hong Kong Polytechnic University.

Prefix-specific and bi-directional explicit Address Mapping (IVI) for IPv4/IPv6 Coexistence and Transition Xing Li, Maoke Chen, Congxiao Bao, Hong Zhang.

RIPE Berlin – May, 2008 Vince Fuller (for Dino, Dave, Darrel, et al) LISP: Intro and Update

Softwire IETF 78. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and.

The Implementation of 6TALK Yong-Geun Hong The 1 st GLOBAL IPv6 Summit in AP

DNS and IP Scalability Communication Systems Design 2002.

Different Address Family Transit (DAFT) using Encapsulation and BGP-MP Extension Tsinghua University Feb 23, 2006 Contact: ----A.

Softwire Mesh Framework: Multicast Mingwei Xu Yong Cui CERNET, China Chris Metz, Cisco 68 th IETF Meeting, Prague March 2007.

1 NCM _05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved. How would you prepare for the technology you need.

Lesson 2 Introduction to IPv6.

Network Performance Test on IPv Technology Laboratory, KT Choi Sung Mi

W&L Page 1 CCNA CCNA Training 3.4 Describe the technological requirements for running IPv6 in conjunction with IPv4 Jose Luis Flores /

Bjorn Landfeldt, The University of Sydney 1 NETS 3303 IPv6 and migration methods.

Softwire mesh MIB draft-cui-softwire-mesh-mib Peng Wu Tsinghua University.

Stateless 1:N IVI and Stateless 1:N double IVI X. Li, C. Bao, H. Zhang November 12, 2009.

Public 4over6: WGLC feedback Peng Wu IETF84. Feedback from WGLC Relationship with stateless 4-over-6 solutions? Different primary targets and application.

A Reset on Softwire Mesh Multicast Mingwei Xu Yong Cui CERNET, China Chris Metz, Cisco IETF76 Meeting, Hiroshima Nov 2009.

Lightweight 4over6: An Extension to DS-Lite Architecture draft-cui-softwire-b4-translated-ds-lite-09 Y. Cui, Q. Sun, M. Boucadair, T. Tsou, Y. Lee and.

IETF 80 th Lightweight Address Family Transition for IPv6 draft-sunq-v6ops-laft6-01 Chongfeng Xie( China Telecom ) Qiong Sun( China Telecom)

Presented By:- Avinash Kumar Nitesh Kumar Yadav. OUTLINE  Introduction of IP v4.  Introduction of IP v6.  Advantages of IP v6 over IP v4.  Transition.

Single-stack IPv6-only data center deployments

Translation Spot Negotiation in IPv4/IPv6-Coexist Mesh

Softwire Mesh Framework: Multicast

PE-based IPv6 multicast transition for mesh problem

Softwire Mesh Solution Framework

SIIT-DC: IPv4 Service Continuity for IPv6 Data Centres

Softwire Security Update

Copyright © 2006 Juniper Networks

Implementing IP Addressing Services

IPv6 VPN Based Address Format draft-lee-l3vpn-ipv6-vpn-00.txt

CERNET2 IPv6-only Practice: Backbone, Servers, Clients and 4aaS

Implementing IP Addressing Services

DHCP: Dynamic Host Configuration Protocol

Chapter 4: outline 4.1 Overview of Network layer data plane

Presentation transcript:

IPv4/IPv6 Coexistence Framework Prefixing/Encap/Translation (PET) draft-cui-softwire-pet-01 draft-cui-softwire-pet64-00 Yong Cui, Mingwei Xu, Shengling Wang, Jianping Wu, Xing Li, Chris Metz, etc. CERNET, CISCO Nov. 2009

Motivation: Diminish the disadvantage of translation Do we need translation? YES We have spent years to reduce the complexity of translation –SIIT, NAT-PT, … –IVI, NAT64, DNS64, … Why not look at finding the right place to diminish the disadvantage of translation? –Even using an additional tunnel IPv6 Edge network Host B (IPv6) Dual-stack backbone IPv4 Internet Xlate ??? Host A (IPv4) AFBR1 AFBR2

Motivation IP layer (Hardware) Stateless (Scalable) Separated routing (Scalable) E-IP over I-IP Tunneling ALG (Software) Stateful (No Scalable) Routing merge (No Scalable) E-IP  I-IP Translation Processing Layer State Maintenance Application Scenario It is necessary to –decide which method should be used in given scenarios –how they collaborate for solving transition problems while utilizing both advantages? IPv4/IPv6 Routing

Example to combine them In the beginning of small IPv6 network Next step on large IPv6 backbone Incremental deployment for 100 IPv6 edge networks –Optionally xlate on either side How can network decide where to use tunneling or xlate IPv6 Backbone IPv6 Edge IPv4 Internet AFBR Xlate PE IPv6 Backbone IPv6 Edge IPv4 Internet Softwire AFBR SW AFBR SW AFBR Xlate

PET framework P: prefixing –all transition operations of control plane involved with subnet prefix For tunneling: prefix announcement, tunnel endpoint discovery/selection, and so on For translation: prefix configuration or address mapping policy, and so on E: encapsulation –all tunneling operations of data plane Encapsulation/decapsulation/MTU processing T: translation –all translation operations of data plane address mapping/protocol translation/MTU processing.

I-IP Backbone (Dual-stack) E-IP network PET PET framework PET E-IP Backbone PET I-IP network PET Edge Network IPv4IPv6IPv4IPv6

source IPv4 4  6  4 SW Function of PET PET Encap. IPv6 backbone IPv6 PET Decap. IPv4 PET Signaling Dest IPv6 Edge net Xlate+SW Decap IPv4 6  6  4 Local-Xlat+ SW IPv6 Backbone IPv4 6  6  4 Remote Xlat Forwarding Xlate IPv4 Encap. Decap+ Xlate IPv6 4  6  6 SW+ Remote Xlat

PET signaling Functionality –Negotiate between PET boxes –Who should do translation / tunneling –For what kind of packets / prefix Example –Negotiate the translation preference (TP) –Parameters: Bandwidth, pps, load –Stateless/Stateful

PET: Softwire + Behave (1:1/IVI) IPv6 Campus IPv6 Backbone IPv4 Internet PET2 DNS6DNS4 IVI prefix(P_ivi)+IPv4 Address allocation PET1 IVI mapped IPv4 prefix IPv4 Internet prefix Softwire routing [ P_ivi+ IPv4 prefix ] [ P_ivi+ ( /0) ] IPv6 native routing DNS process IPv6 packet Src: remove P_ivi Dst: remove P_ivi IPv4 packet Softwire vif + Xlate IPv6 interface for IPv6 dst TP1 lose TP2 win IPv4 packet Src add P_ivi Dst add P_ivi IPv6 packet Softwire vif for IPv4 dst IPv6 interface for IPv6 dst TP2 win √√ TP1TP2 PET signaling √

PET: Softwire + Behave (1:1/IVI) IPv6 Campus IPv6 Backbone IPv4 Internet PET2 DNS6DNS4 IVI prefix(P_ivi)+IPv4 Address allocation PET1 DNS process Remove P_ivi TP1 win 4over6 Softwire IPv6 packet IPv4 packet Decap Softwire vif + Xlate IPv6 interface for IPv6 dst TP2 lose IPv4 packet IPv6 packet Decapsulation Add P_ivi 4over6 Softwire Softwire vif for IPv4 dst IPv6 interface for IPv6 dst IVI mapped IPv4 prefix IPv4 Internet prefix Softwire routing [ P_ivi+ IPv4 prefix ] [ P_ivi+ ( /0) ] IPv6 native routing √√ TP1TP2 PET signaling √

PET: Softwire + Behave (1:N) IPv6 Backbone IPv4 Internet PET2 DNS6 DNS4 IPv6 address allocation PET1 DNS process TP2 win TP1 lose IPv6 packet Src: IPv6 addr+port => PET2 v4 addr + port Dst: remove P_ivi IPv4 packet Softwire vif + Xlate IPv6 interface for IPv6 dst TP2 win Src: add P_ivi Dst: port=> IPv6 addr+port IPv4 packet IPv6 packet Softwire vif for IPv4 dst IPv6 interface for IPv6 dst IVI mapped IPv4 prefix IPv4 Internet prefix Softwire routing [ P_ivi+ IPv4 prefix ] [ P_ivi+ ( /0) ] IPv6 native routing √√ TP1TP2 PET signaling √ IPv6 Campus

PET: Softwire + Behave (1:N) IPv6 Campus IPv6 Backbone IPv4 Internet PET2 DNS6DNS4 IPv6 address allocation PET1 DNS process Src: IPv6 ddr+port =>PET1 v4 addr + port Dst: remove P_ivi TP1 win 4over6 Softwire IPv6 packet IPv4 packet Decap Softwire vif + Xlate IPv6 interface for IPv6 dst TP2 lose IPv4 packet IPv6 packet Decapsulation; Src: add P_ivi Dst: port=> IPv6 addr+port 4over6 Softwire Softwire vif for IPv4 dst IPv6 interface for IPv6 dst IVI mapped IPv4 prefix IPv4 Internet prefix Softwire routing [ P_ivi+ IPv4 prefix ] [ P_ivi+ ( /0) ] IPv6 native routing √√ TP1TP2 PET signaling √

Future work PET signaling will be defined by BGP extension based on Softwire Leveraging other existing tunneling and translation technologies