Plenary: Life after IPv4 Exhaustion

IPv4/IPv6 transition experience

and the features of stateless
translation (IVI)
Xing Li
2011-02-23
AS-level (1)

2
 AS-level (2)

IPv4 AS count (35k) IPv6 AS count (3k)

3
 After IPv4 exhaustion

•  In 172 days
–  Increase AS number from 3K  35K
–  Make 99% of the content IPv6 available
–  Mission impossible
4
 Ready and not ready
Contents: Not ready Contents

Applications: Some is ready

Applications

NMS/Billing/CRM: Not ready

Core Network
Core: Ready NMS
DNS: Ready DNS Metro Core Billing
MultiService Edge Node CRM
（BRAS/SR/GGSN/PDSN）
Access: Not ready
Fix Access Mobile Access
xDSL FTTx LAN Wifi 1X、EVDO

Hosts: Most can be ready

Hosts Mobile Devices
Mobile Devices: Not ready
5
IPv6 S curve

172 days 6
 Who will be mostly affected
•  The existing IPv4-only users
–  They are happy now, until there are IPv6-only
content/users
–  Upgrade to dual stack is not very urgent
–  Upgrade to dual stack should not degrade
their experience
•  The new users
–  They do NOT accept the service if they
cannot access the global IPv4 Internet.
7
SP should make a decision in 172 days

(IPv4+NAT44) IPv6
(IPv4+NAT44) + +
IPv6 translation-to-IPv4

NAT444 Dual-tack Lite IVI, NAT64

8
IPv4/IPv6 transition standard roadmap
Solution Standard /Draft Standard note
roadmap
IVI (stateless) RFC6052* (addr-fmt), RFC6144* Est. Mar, IETF
(framework), RFC6145* (xlate), 2011 behave
RFC6147 (dns), WG
ivi*, [in IETF-editor queue]
NAT64 RFC6052* (addr-fmt), RFC6144* Est. Mar, IETF
(stateful) (framework), RFC6145* (xlate), 2011 behave
RFC6146 (stateful), RFC6147 (dns) WG
Dual Stack lite Dual-stack-lit-06 [AD Est. Q2, IETF
Evaluation::Revised ID Needed] 2011 softwire
WG
6RD RFC5969 Aug, 2010 IETF
softwire
WG
NAT444 nat444-03 Est. Not in
Unknown IETF WG

* CERNET authors/co-authors 9
If  IPv6  is  so  great,  how  come  it  is  not  there  yet?  

•  Applications
–  Need upfront investment,
stacks, etc.
–  Similar to Y2K, 32 bit vs.
“clean address type”
•  Network
–  Need to ramp-up
investment
–  No “push-button”
transition

•  IPv4 exhaustion does not change this

–  NAT44 vs. IPv6 10
 CERNET and CERNER2

IPv4   IPv6-­‐only  
2,000  Universities     200  Universities    
25,M  Users   2M  Users  
11
 To encourage transition
•  CERNET (IPv4)
–  Congested and charged.
•  CERNET2 (IPv6)
–  Light loaded and free of charge.

•  So, for using high quality and free network, port

your application to IPv6.

12
IPv4 and IPv6 traffic

IPv4 IPv6

•  CERNET IPv6’ traffic is about 20% of IPv4

13
 So what are IPv6 traffics
•  Mostly video
•  Anything which cannot be accessed via
IPv4
•  If both IPv4/IPv6 are available, the users
prefer to use IPv4 (better experience)
•  Except EE and CS students

14
 When will be the X’-day?
•  We have asked our customers
–  Can we turn off CERNET (IPv4) and only
provide CERNET2 (IPv6) services?
–  The answer is absolutely NO! If there is a
single IPv4-only content in the global Internet,
we can not turn off IPv4.
•  We have almost reached X-day (IPv4
address depletion)
•  When will be the X’-day (turn off IPv4)?

15
 The killer application
•  Video?
•  P2P?
•  Internet of Things?
•  The
intercommunication
with the IPv4 Internet
is the killer application
of IPv6.
16
 We invented IVI

Global Global
IPv4 IPv6

IPv4-
accessible
servers/clients

CERNET (IPv4) CERNET2 (IPv6)

17
 Translation scenarios

xlate xlate
The IPv4 An IPv6 An IPv4 The IPv6
Internet Network Network DNS Internet
DNS

Scenario 1 “an IPv6 network to the IPv4 Internet” < NAT64 Scenario 3 “an IPv4 network to the IPv6 Internet” < NAT64
IVI { Scenario 2 “the IPv4 Internet to an IPv6 network” Scenario 4 “the IPv6 Internet to an IPv4 network”

xlate xlate
An IPv4 An IPv6 The IPv4 The IPv6
Network DNS Network Internet Internet
DNS

Scenario 5 “an IPv6 network to an IPv4network” < NAT64 Scenario 7 “the IPv6 Internet to the IPv4 Internet”
IVI { Scenario 6 “an IPv4 network to an IPv6 network” Scenario 8 “the IPv4 Internet to the IPv6Internet”

18
 Stateless translation (IVI)

IPv6
IVI
IPv4

A subset of IPv6
addresses

Real IPv4 host mirrored IPv6 host mirrored IPv4 host Real IPv6 host

A subset of IPv6 addresses

19
www.ivi2.org

20
 1:N IVI

IPv6 address port

port i=0 2001:db8:a4a6:3ac8:c00a:2000:: 84

IPv4 address 84 i=1

85 2001:db8:a4a6:3ac8:c00a:2001:: 85
202.38.108.5
86 i=2
2001:db8:a4a6:3ac8:c00a:2002:: 86
87
i=3
2001:db8:a4a6:3ac8:c00a:2003:: 87

•  If R=256
•  A /24 is equivalent to a /16

21
 1:N dIVI

H0
DS
Hgw0

The IPv4 1:N An IPv6 H1

Internet IVI network Hgw1 DS

H2
Hgw2 DS

The IPv6
Internet HgwK HK
DS

22
 Make things easy and simple
•  Service Continuity
–  Only upgrade core network to dual stack
–  Keep the existing IPv4 access network running as
usual
•  Minimal customer Impact
–  Deploy IPv6-only data center with 1:1 IVI to move
content to IPv6 without loosing the IPv4 users
–  Deploying new IPv6-only access network with 1:N
double IVI for new customers using shared IPv4
addresses
•  Incremental investment
–  Incremental deployment with direct returns.
23
 Remarks (1)
•  Dual stack and tunnel are coexistence
technologies
–  10 year experience indicates that we have not
achieved transition via dual stack and tunnel
•  Let’s try translation now
–  We need a single Internet, not two Internets
(IPv4 and IPv6)
–  Due to the long tail, the transition cannot be
achieved in short time
24
 Remarks (2)
•  The competition is what type of translation
technologies we will use
IPv4 Internet IPv4 Internet

NAT44 NAT44 NAT44 IVI IVI IVI

RFC1918 RFC1918 RFC1918 IPv6 IPv6 IPv6

IPv6 IPv6 IPv6

IPv6 Internet IPv6 Internet

•  Translation between •  Translation between

–  IPv4 and RFC1918 –  IPv4 and IPv6 25
 Conclusions
•  IPv6 is the right direction and it works
–  A lot of addresses
–  End-to-end address transparency
•  IPv6 is not easy – the rest of users and contents
may still use IPv4
–  Service Continuity
–  Minimal customer Impact
–  Incremental investment
•  The universal connectivity is the fundamental
requirement for using Internet
–  Translation
26
 IVI IPv4/IPv6 transition
IPv4 Transition IPv6
IPv4 area IPv6 area
Service

Support Support Support

IPv4 IPv6 (IVI) IPv6 (non-IVI)

V4 only Network V6 only Network

Network

IVI
User

Support IPv4 Support IPv6 (IVI) Support IPv6 (non-IVI)

27