Translation Spot Negotiation in IPv4/IPv6-Coexist Mesh

Slides:

Advertisements

Similar presentations

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-

Advertisements

Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.

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.

1 3gpp_trans / 09/02 / IPv6 Transition Solutions for 3GPP Networks draft-wiljakka-3gpp-ipv6-transition-01.txt Juha Wiljakka, Nokia.

Possible approaches to signal IPv4 embedded IPv6 Multicast Address.

RFC 3489bis Jonathan Rosenberg Cisco Systems. Technical Changes Needed Allow STUN over TCP –Driver: draft-ietf-sip-outbound Allow response to omit CHANGED-

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

IPv6: The Next Generation Internet Protocol Luke Simpson and Martin Bouts ECE 4112 Spring 2005 May 2nd, 2005.

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.

1 Network Architecture and Design Advanced Issues in Internet Protocol (IP) IPv4 Network Address Translation (NAT) IPV6 IP Security (IPsec) Mobile IP IP.

MAP-T and MAP-E deployment in CERNET and China Telecom

This work is supported by the National Science Foundation under Grant Number DUE Any opinions, findings and conclusions or recommendations expressed.

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)

Network-based IP VPNs using Virtual Routers Tim Hubbard.

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

Polycom Conference Firewall Solutions. 2 The use of Video Conferencing Is Rapidly Growing More and More people are adopting IP conferencing Audio and.

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

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.

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

HUAWEI TECHNOLOGIES CO., LTD. IPv4/IPv6 multicast interoperation Sheng Jiang Senior Research Engineer Huawei

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.

Network Layer4-1 Chapter 4: Network Layer r 4. 1 Introduction r 4.2 Virtual circuit and datagram networks r 4.3 What’s inside a router r 4.4 IP: Internet.

BGP-MPLS VPN extension for IPv4/IPv6 Hybrid Network Defeng Li Huawei Technologies.

Flexible Traffic Engineering: When OpenFlow Meets Multi-Protocol IP- Forwarding IEEE COMMUNICATIONS LETTERS, VOL. 18, NO. 10, OCTOBER 2014 Authors: Suoheng.

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.

Softwire IETF 84. Preparation Blue sheet Note taker? Jabber room? …

IPv6 transition strategies IPv6 forum OSAKA 12/19/2000 1/29.

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.

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

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.

Softwire Security Requirement Update draft-ietf-softwire-security-requirements-02.txt IETF Meeting, Prague March 19, 2007 Shu Yamamoto Carl Williams Florent.

11 Softwire Security Analysis and Guidance for Mesh Shu Yamamoto Carl Williams Florent Parent Hidetoshi Yokota draft-ietf-softwire-security-requirements-XX.txt.

/ Jonne Soininen v6ops-3GPP Design Team IETF#55, v6ops wg Atlanta, USA Jonne Soininen / Juha Wiljakka

1 3gpp_trans/ / IPv6 Transition Solutions for 3GPP Networks draft-wiljakka-3gpp-ipv6-transition-00.txt Juha Wiljakka,

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

Softwire Mesh Example CERNET2 Xing Li. Outline  CERNET2 Briefing  CERNET2’s IPv4 over IPv6 requirement  Configurations  Summary.

November 6, 2006Softwire WG Meeting1 Softwires “Mesh” Scenario Problem: –pass AF1 routing and data over the AF1-free core, –while obeying certain constraints.

Can we save the OPEN Internet? with focus on The Two-Port Internet Problem and what to do about it Terry Gray Designated Prophet of Doom University of.

Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations (RFC 6324) Po-Kang Chen Oct 19,

H.323 NAT Traversal Problem particular to H.323(RAS->Q.931->H.245):  RAS from private network to public network can pass NAT  Q931 、 H.245 adopts the.

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.

Softwire Security Update Shu Yamamoto Carl Williams Florent Parent Hidetoshi Yokota 67 IETF, San Diego.

V4 traversal for IPv6 mobility protocols - Scenarios Mip6trans Design Team MIP6 and NEMO WGs, IETF 63.

Single-stack IPv6-only data center deployments

Performance Evaluation of OSPF and IS-IS Routing Protocols using

Internet Protocol Version 6 Specifications

Softwire Mesh Framework: Multicast

draft-patel-raszuk-bgp-vector-routing-01

PE-based IPv6 multicast transition for mesh problem

Chongfeng. Xie(Presenter), Qiong Sun, Qi He, Cathy Zhou

Alain Durand, Comcast David Ward, Cisco

Softwire Mesh Solution Framework

Softwire Security Update

Introducing Novell IPv6 Stack

IS3120 Network Communications Infrastructure

Copyright © 2006 Juniper Networks

A Unified Approach to IP Segment Routing

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

An Introduction to MPLS-PIM Interworking

IETF South Korea PCEP Link-State extensions for Segment Routing draft-li-pce-pcep-ls-sr-extension-01 Zhenbin Li (Huawei) Xia Chen (Huawei) Nan.

IPv6 Development in China

M. Boucadair, J. Touch, P. Levis and R. Penno

Multicast Support for Dual Stack Lite and 6RD

Presentation transcript:

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

Challenges of translation Basic IPv4-IPv6 transition techniques Tunnel for IPv4-over-IPv6/IPv6-over-IPv4 traversing Translation for IPv4-IPv6 inter-connection But translation has technical challenges Scalability: IPv4 addr consuming/mapping maintenance Application layer translation Operation complexity: per-packet/from IP to app layer Lack of efficient NAT46 mechanism Refer to RFC4966 for more details Inherent properties due to the principle of translation per-packet/from IP to app layer

Tunnel for translation spot “transfer” Naturally, translation happens on IP border Use a tunnel to transfer the translation to other spot Tunnel for traversing between translation spot and IP border Choose translation spot flexibly Translator with better hardware capability; traffic less-aggregated; support ALG or not; etc. IP Border Translation Spot IPvX Backbone IPvY Internet IPvX Edge BR AFBR Xlate Translation Spot IP Border IPvX Backbone IPvY Internet IPvX Edge Xlate TE BR IPvY-over-IPvX Tunnel AFBR TE AFBR Xlate

Real Problem in IPv4/IPv6-coexist mesh Mesh Scenario Exists in CERNET2 Communications E-IP over I-IP traversing(RFC5565) Inter-connection between E-IP & I-IP (the scope of this draft) Translation spot AFBR (IP-border) BR (non IP-border) I-IP Internet E-IP Internet BR AFBR I-IP Client Net I-IP Backbone E-IP Client Net BR Support alg myself; know my translation volume and total mapping number I’m capable of doing that; I can’t do translation at all AFBR I-IP Client Net E-IP Client Net I-IP Client Net E-IP Client Net

Solution Softwire tunnel(RFC 5565) to transfer translation spot E-IP over I-IP routing(RFC 5549) required for translation Translation spot negotiation using BGP on AFBRs/BRs BGP already supported by AFBR/BR in mesh scenario Protocol extensions: A new BGP Attribute "Translation Information Attribute" with 4 TLVs, to Decide translation spot Deliver translation context