1 / 11

M.Mawatari @ Japan Internet Exchange Co.,Ltd. M.Kawashima @ NEC AccessTechnica, Ltd.

464XLAT Combination of Stateful and Stateless Translation draft-ietf-v6ops-464xlat-01 IETF 83 v6ops WG. M.Mawatari @ Japan Internet Exchange Co.,Ltd. M.Kawashima @ NEC AccessTechnica, Ltd. C.Byrne @ T-Mobile USA. What is 464XLAT?. PLAT : Provider side translator(XLAT)

ronaldemccoy
Download Presentation

M.Mawatari @ Japan Internet Exchange Co.,Ltd. M.Kawashima @ NEC AccessTechnica, Ltd.

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. 464XLATCombination of Stateful and Stateless Translationdraft-ietf-v6ops-464xlat-01IETF 83v6ops WG M.Mawatari @ Japan Internet Exchange Co.,Ltd. M.Kawashima @ NEC AccessTechnica, Ltd. C.Byrne @ T-Mobile USA

  2. What is 464XLAT? PLAT : Provider side translator(XLAT) CLAT : Customer side translator(XLAT) IPv6 IPv6 IPv6 IPv4 IPv4[P] IPv6 IPv6 Internet IPv4 Internet PLAT CLAT IPv4 IPv6 Private IPv4 Global IPv4 StatefulXLATE[RFC 6146] StatelessXLATE[RFC 6145] 464XLAT provides limited IPv4 connectivity across anIPv6-only network by combining existing and well-known stateful protocol translation RFC 6146 in the core andstateless protocol translation RFC 6145 at the edge.

  3. What is 464XLAT? (cont.) • What it is • Combined RFC 6145 and RFC 6146 • Easy to deploy and available today, commercial and open source shipping product • Effective at providing basic IPv4 service to consumers over IPv6-only access networks • Efficient use of very scarce IPv4 resources • What it is NOT • A perfect replacement for IPv4 or Dual-stack service • Category: Standards Track

  4. Motivation and Uniqueness of 464XLAT • Minimal IPv4 resource requirements • This is shown as strong point due to stateful translation in PLAT. Each 1 IPv4 can mask more than n*64,000 flows. • ISPs can efficiently and effectively share limited IPv4 global address pool. • If ISPs have little IPv4 address (e.g. ISPs in APAC already had exhausted IPv4), they can share it for end-users. • No new protocols required • It is only necessary to use standard technologies based on RFC already published. • Most of ISPs do not have a lot of time to make a new protocol.

  5. Motivation and Uniqueness of 464XLAT (cont.) 3. Cost-effective transition to IPv6 • When combined with DNS64, ISP can provide sharing IPv4 address and IPv4/IPv6 translation at same time. • ISPs can do traffic engineering without deep packet inspection devices. • If the other ISPs operate PLAT as PLAT providers, ISPs for IPv6 consumers can independently do traffic engineering on common backbone routers. • CPE can replace simply from NAT44 to NAT46.It means that saving the resource in CPE.Therefore, CPE can widely adapt from the wireline to the wireless.

  6. Timeline of 464XLAT draft 2011/10/16Published draft-mawatari-softwire-464xlat-00 2011/10/24Published draft-mawatari-softwire-464xlat-01 2011/10/31Published draft-mawatari-softwire-464xlat-02 2011/11/15Introduced version -02 in softwire WGIETF 82 2012/01/15Published draft-mawatari-v6ops-464xlat-00 • Motivation and Uniqueness 464XLAT is added • Some implementation considerations are added 2012/02/15Published draft-ietf-v6ops-464xlat–00 as a WG draft 2012/03/12Published draft-ietf-v6ops-464xlat–01 Timeline

  7. Version individual draft through v6ops WG draft • Changes • Since this is an Informational Draft,a normative language has been removed. • Terminology • Clarifying the behavior and function of CLAT. • Implementation Consideration • Clarifying “DNS proxy” and “IPv6 prefix handling on CLAT”. • Adding the explanations of “CLAT function in gateway” and “hub and spoke architecture”.

  8. Next steps • Any issues to discuss from the audience. • Trying to get the approval of v6ops WGLC. • Getting more knowledge by running code. • experiences from wireline network and mobile network.

  9. Backup Slides

  10. Network architecture 2001:db8:cafe::cafe IPv6 2001:db8:aaaa::aa IPv6 IPv6 Native IPv4 IPv4[P] IPv6 IPv6 Internet IPv4 Internet PLAT CLAT IPv4 464XLAT PLAT> IPv4 pool[192.0.2.1 - 192.0.2.100]XLATE DST Prefix[2001:db8:1234::/96] CLAT>XLATE SRC Prefix[2001:db8:aaaa::/96]XLATE DST Prefix[2001:db8:1234::/96] 198.51.100.1 192.168.1.2 IPv4 SRC192.0.2.1 IPv4 DST198.51.100.1 IPv4 SRC192.168.1.2 IPv4 DST198.51.100.1 IPv6 SRC2001:db8:aaaa::192.168.1.2 IPv6 DST2001:db8:1234::198.51.100.1 StatelessXLATE[RFC 6145] StatefulXLATE[RFC 6146] • This architecture consist of CLAT and PLAT have the applicability to landline network (e.g. FTTH) and mobile network (e.g. 3GPP).

  11. References • Android-CLAT (CLAT code for Android) • http://code.google.com/p/android-clat/ • n900ipv6 (CLAT code for Nokia n900) • https://code.google.com/p/n900ipv6/wiki/Nat64D • 464XLAT experiences in JPIX • http://www.apricot2012.net/program/ipv6-conference • NEC AccessTechnica CLAT for wireline. • This CPE is used for JPIX trial service and WIDE Camp Spring 2012. NEC AccessTechnica CL-AT1000P

More Related