464XLAT Tutorial

Hypes? Fanfares? Fads?
Wading through the muddy IPv6 puddle
~ 464XLAT Tutorial ~
Japan Internet Exchange Co., Ltd.
Masataka MAWATARI <mawatari@jpix.ad.jp>
APNIC 40 @ JAKARTA, INDONESIA

• This tutorial introduces you the background
and technical inside and around 464XLAT
(RFC 6877).
• Hope to be of assistance to you in the
464XLAT network on your service in the
future.
Introduction
Copyright © 2015 Japan Internet Exchange Co., Ltd. 2

1. Background:
motivation of IETF and a brief introduction
about IPv4 over IPv6
2. 464XLAT network architecture
3. Use case and implementations
Agenda

1. Background:
Agenda

• Little IPv6 but massive spreading CGN
– Today, IPv6 growth is finally real.
• NAT64/DNS64 is just not good enough
– Some applications don’t work in the IPv6-only
networks with NAT64/DNS64.
• Scarcity consciousness...?
– IPv6/IPv4 coexistence techniques weren’t
actually run on the commercial network.
– People thought that must be complicated...
Background around IPv6 at the time

Tested application worked or didn’t work ?
in the IPv6-only network with NAT64/DNS64
Reference: http://goo.gl/z3j3q

The progress of IPv4 over IPv6 technique
Reference: https://ripe65.ripe.net/presentations/91-townsley-map-ripe65-ams-sept-24-2012.pdf

• Minimal IPv4 resource requirements,
maximum IPv4 efficiency through statistical
multiplexing.
• No new protocols required, quick deployment.
• IPv6-only networks are simpler and therefore
less expensive to operate.
Motivation and uniqueness of 464XLAT
Reference: Section 3 of RFC 6877 (464XLAT: Combination of Stateful and Stateless Translation)
https://tools.ietf.org/html/rfc6877#section-3

The timeline of 464XLAT draft (1)
2011/10/16 Published draft-mawatari-softwire-464xlat-00
» This was initial publication in softwire WG.
» “Introduction” was clarified and polished.
» Cameron Byrne from T-Mobile USA was joined as one
of co-authors.
» “Network Architecture” and “” Applicability were
separated to “Wireline Network” and “Wireless 3GPP
Network”.
2011/11/15 Introduced in softwire WG IETF 82
» v6ops WG is more suitable than softwire WG for
discussion about 464XLAT.
2012/01/15 Published draft-mawatari-v6ops-464xlat-00
» This was initial publication in v6ops WG.
Timeline

2012/02/11 Approval as a WG document in v6ops WG
2012/02/15 Published draft-ietf-v6ops-464xlat-00
» “CLAT in a Gateway” and “CLAT to CLAT
communications” were added.
» “Terminoloty” and “DNS Proxy Implementation” were
revised.
» The text in “Auto IPv6 Prefix Assignment” was merged
to “IPv6 Prefix Handling”.
» “Introduction” and “Motivation and Uniqueness of
464XLAT” were revised.
» “IPv6 Fragment Header Consideration” was deleted.
2012/03/26 Introduced in v6ops WG IETF 83
» Changed from Infomational to BCP by chairs comment.
» “IPv6 address format” and “IPv4/IPv6 address
translation chart” were revised.
Timeline

» “IPv6 Prefix Handling” was revised.
» “Relationship between CLAT and NAT44” was added.
» “Terminology” and “Network Architecture” were
revised.
» Text about BIH (Bump-in-the-Host) was added.
» “Examples of IPv4/IPv6 Address Translation” was
added.
» “Wireless 3GPP Network Applicability” was revised.
2012/07/30 Introduced in sunset4 WG IETF 84
2012/08/03 Introduced in v6ops WG IETF 84
» Approval of start of Working Group Last Call at v6ops.
» “BCP Scenario” was added.
Timeline

» “Network Architecture” was revised.
» Text about Neighbor Discovery Proxy was added.
» Texts about BIH (Bump-in-the-Host) and Neighbor
Discovery Proxy were deleted.
2012/12/07 IETF Last Call started
» “BCP Scenario” was revised.
2013/02/02 Registered in RFC Editor Queue
» “BCP Scenario” was deleted.
2013/04/02 Published RFC 6877
Timeline

1. Background:
Agenda

• Simple technique to provide IPv4 access service
across IPv6 network by combining existing and
well-known stateful and stateless translation.
– Stateful NAT64 : RFC 6146
– Stateless NAT64 : RFC 6145
• 464XLAT has low barriers to entry since only a
small amount of IPv4 addresses are needed to
support the stateful translation function in the
PLAT.
• 464XLAT can apply to wireline network and
wireless 3GPP network.
What is 464XLAT (RFC 6877)

• PLAT : Provider side translator (XLAT)
– A stateful translator complies with [RFC6146] that
performs 1:N translation. It translates global IPv6 address
to global IPv4 address, and vice versa.
• CLAT : Customer side translator (XLAT)
– A stateless translator complies with [RFC6145] that
performs 1:1 translation. It algorithmically translates
private IPv4 address to global IPv6 address, and vice
versa.
– CLAT function is applicable to a router, or endnode such
as a mobile phone.
– The presence of DNS64 [RFC6147] and any port mapping
algorithm are not required.
Terminology of 464XLAT

464XLAT network architecture (Wireline)
CLAT PLAT
IPv6
Internet
198.51.100.1
192.168.1.2
IPv4
Internet
IPv6
IPv4 Private
PLAT>
IPv4 pool
[192.0.2.1 - 192.0.2.100]
PLAT-Side XLATE IPv6 Prefix
[2001:db8:bbbb::/96]
CLAT>
CLAT-Side XLATE IPv6 Prefix
[2001:db8:aaaa::/96]
[2001:db8:bbbb::/96]
IPv4 SRC
192.168.1.2
IPv4 DST
198.51.100.1
IPv6 SRC
2001:db8:aaaa::192.168.1.2
IPv6 DST
2001:db8:bbbb::198.51.100.1
IPv4 SRC
192.0.2.1
IPv4 DST
198.51.100.1
2001:db8:aaaa::aa
2001:db8:cafe::cafe
IPv6 Native
464XLAT
Stateless
NAT64
[RFC 6145]
Stateful
NAT64
[RFC 6146]
IPv6
IPv4
IPv6
IPv4

464XLAT network architecture (Mobile)
PLAT
IPv6
Internet
198.51.100.1
IPv4
Internet
PLAT>
IPv4 pool
[192.0.2.1 - 192.0.2.100]
[2001:db8:bbbb::/96]
IPv4 SRC
192.0.0.4
IPv4 DST
198.51.100.1
IPv6 SRC
2001:db8:aaaa::464
IPv6 DST
2001:db8:bbbb::198.51.100.1
IPv4 SRC
192.0.2.1
IPv4 DST
198.51.100.1
2001:db8:cafe::cafe
IPv6 Native
464XLAT
Stateless
NAT64
[RFC 6145]
Stateful
NAT64
[RFC 6146]
IPv6
IPv6
IPv4
User equipment/Mobile Phone
CLAT>
IPv4 host address for XLATE (clat4)
[192.0.0.4/32]
IPv6 host address for XLATE
[2001:db8:aaaa::464/128]
[2001:db8:bbbb::/96]
IPv4
CLAT function

CLAT function
The mobile phone uses
a routed point to point
interface as the source
of 464XLAT traffic
IPv6
(from mobile phone after translation)
IPv6
(from tethered device)
User Equipment/
Mobile Phone
(enable tethering function)
NAT46
NAT44
IPv4
(from tethered device before translation)
interface
wlan0
interface
rmnet0
Tethered device
192.168.1.100/24
2001:db8:aaaa::cafe/64
2001:db8:aaaa::464/128
192.0.0.4/32
IPv6 Native464XLAT
IPv6
(from tethered device)
Host address for
the local traffic to use
2001:db8:aaaa::/64
[RA]
Focusing on the case of tethering (Mobile)

• RFC 7278
– “Extending an IPv6 /64 Prefix from a Third
Generation Partnership Project (3GPP) Mobile
Interface to a LAN Link”
– This is for mobile device to perform the IPv6
tethering function without DHCPv6-PD
• RFC 7335
– “IPv4 Service Continuity Prefix”
• 192.0.0.0/29
– A IPv4 host address is needed for 464XLAT
CLAT function inside the endnode such as a
smart phone
RFCs for the mobile network applicability

1. Background:
Agenda

• T-Mobile US (US)
– Deployed in the
GSM/UMTS/LTE network
– February, 2015.
Exceeded 50%
• SK Telecom (South Korea)
– http://ipv6event2015.vn/download/2-SKT-
ApplyingIPv6ToLTENetworks.pdf
• Orange Poland (Poland)
– http://www.data.proidea.org.pl/plnog/12edycja/day2/track4/01
_ipv6_implementation.pdf
Use case (Mobile)
Network operator measurements, 12th August 2015
http://www.worldipv6launch.org/measurements/

Use case (Wireline)
PLAT
IPv6
JPIX IP Backbone
(Global IPv4/IPv6)
CLAT
Global
IPv4
The Internet
(Global IPv4)
IX Switch
Content Server (Global IPv4)
ISP Backbone
(IPv6)
IPv6
IPv4
Stateful
NAT64
Stateless
NAT64
Private
IPv4IPv4
• The target of this is ISP
that provide IPv6 access
service for end users
• For members of JPIX IX
service.
• Approximate 20 ISPs
participant in trial now.
• Reference
– http://www.jpix.ad.jp/en/service/ipv6v4.html

Use case (Wireline)
JPIX datacenter @ Tokyo, Japan
The
Internet
Conference venue @ Fukuoka, Japan
Device connected to
WiFi SSID for 464XLAT
IPv6
IPv4 only
Content Server
PLATCLAT
(Cisco ASR1002-X)
Global
IPv4
IPv4
IPv6 IPv4
IPv6
APRICOT-APAN 2015 conference network
Private IPv4/IPv6

Implementations (PLAT)
• A10 Networks
Thunder Series
(ACOS 2.6.4 or later)
• Cisco Systems
Cisco ASR 1000 Series
(IOS-XE 3.4.0S or later)
• F5 Networks
BIG-IP Series
(OS 11.1 or later)
• Juniper Networks
SRX Series
(JUNOS 10.4 or later)
• Seiko Solutions
Netwiser iX-3740
(v2.0.0)
Cisco ASR 9000 Series
(IOS-XR 4.3.0 or later)
M/MX Series
(JUNOS 10.2 or later)

464XLAT Tutorial

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (6)

Similar to 464XLAT Tutorial

Similar to 464XLAT Tutorial (20)

More from APNIC

More from APNIC (20)

Recently uploaded

Recently uploaded (16)

464XLAT Tutorial