1 / 11

4V6 – stateless 4Via6

4V6 – stateless 4Via6. http://tools.ietf.org/html/draft-dec-stateless-4v6 W. Dec ( wdec@cisco.com ) R. Asati ( rajiva@cisco.com ) C. Bao ( congxiao@cernet.edu.cn ) H. Deng ( denghui@chinamobile.com ). Introduction.

vicki
Download Presentation

4V6 – stateless 4Via6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4V6 – stateless 4Via6 http://tools.ietf.org/html/draft-dec-stateless-4v6 W. Dec (wdec@cisco.com) R. Asati (rajiva@cisco.com) C. Bao(congxiao@cernet.edu.cn) H. Deng (denghui@chinamobile.com)

  2. Introduction • Motivation for stateless solutions can be found in: draft-operators-softwire-stateless-4v6-motivation • A number of stateless solutions have been proposed. • 4rd, 4v6 (encapsulated or translated mode) • dIVI-PD (translated mode) • These stateless solutions have shared characteristics; commonly termed stateless 4V6. • Main differences lies in algorithm and form of transport: v4-v6 Mapped-Encapsulation or v4-v6 Translation • This presentation focuses on the operational considerations of Stateless4V6 and its forms of transport • It also looks at the 4V6 impact when applied to wider industry standard architectures

  3. 4V6 IPv6 Address • CE IPv6 subnet is assigned announced via DHCPv6-PD or RA (/64) • This is NOT in addition to another PD or RA prefix • 4V6 index encodes all or part of the IPv4 address + a port index.

  4. NAT Stateless 4V6Translation Mode (example only – NOT numerically accurate) Index - f = Ports 2000-2999 NAT44 +4V6 IPv4-Private Customer + IPv6 4V6 address= 2001:beef:(1.1.1.1.f):: 2001:beef:: IPv4-Public IPv6 4V6 Gateway DA:port SA:port NAT44 Source IP Address + Port Stateless v4-v6 address mapping Done by CPE Stateless NAT64 DA:port SA:port Done by GW Stateless IPv6 to IPv4 mapping (NAT64) + port index 2001:beef:1.1.1.1.f:2000 2001:beef:8.8.8.8:80 2001:beef:8.8.8.8:80 2001:beef:1.1.1.1.f:2000 DA:port SA:port 8.8.8.8:80 192.168.0.1:1444 1.1.1.1:2000 8.8.8.8:80 8.8.8.8:80 1.1.1.1:2000 1.1.1.1:2000 8.8.8.8:80 192.168.0.1:1444 1.1.1.1:2000 8.8.8.8:80 8.8.8.8:80 NAPT Done by CPE User’s native IPv6 traffic not shown – travels as ships in the night using native IPv6 forwarding

  5. NAT Stateless46Mapped Tunnel Mode – (Example only - NOT numerically accurate) Index - f = Ports 2000-2999 NAPT44 +4V6 IPv4-Private Customer + IPv6 2001:beef::ff 4V6 address = 2001:beef:(1.1.1.1.f): IPv4-Public IPv6 4V6 Gateway DA:port SA:port NAPT Source IP Address MAP IPv4 to IPv6 address + Encap. DA=4rd Gateway Address Done by CPE Decap packet Note: IPv4 Port shown for IPv4 packets DA SA Done by GW MAP IPv4 to IPv6 address + index & Encap 2001:beef:1.1.1.1.f 2001:100 2001:100 2001:beef:1.1.1.1.f 8.8.8.8:80 192.168.0.1:1444 1.1.1.1:2000 1.1.1.1:2000 8.8.8.8:80 8.8.8.8:80 1.1.1.1:2000 8.8.8.8:80 8.8.8.8:80 1.1.1.1:2000 192.168.0.1:1444 1.1.1.1:2000 8.8.8.8:80 8.8.8.8:80 8.8.8.8:80 1.1.1.1:2000 NAPT Done by CPE User’s native IPv6 traffic not shown – travels as ships in the night using native IPv6 forwarding Decap Packet

  6. Stateless 46Comparison Summary

  7. Operation4V6 in a 3GPP system • 3GPP system functionality is defined to support an extensive set of IP network service requirements, • Eg Per subscriber QoS, charging, data volume plans. • System is in common deployment. IPv6 fully supported in Release 8/9 • Key functionality is the representation and signaling across various interfaces of the user’s virtual connection (Bearer). This is specified in terms of IP Filters. • 3GPP currently defines IPv4 & IPv6 traffic filters. • No clearly defined way how to represent IPv4inIPv6 traffic *alongside* regular IPv6 traffic. • Possible options are an additional (default) bearer (ie additional session), or a new bearer type.

  8. Operation4V6 in 3GPPCharacteristics Summary

  9. Operation4V6 in a PCMM system • Cable Labs

  10. Operation4V6 in PCMMCharacteristics Summary

  11. Conclusion • No critical technical issues with 4V6 and either the 4V6 mapped-tunnel or translation based modes • Both approaches represent valid choices • Translated (non encapsulated) transport appears to be operationally less impactful to broader systems and services • Re-uses native IPv6 network features and system interfaces • Does not require numerous IPv4 extensions to standard architectures that already support IPv6 • Operational impact of both approaches should be documented and trade-offs outlined/clarified.

More Related