ITU Workshop on IPv6
Geneva, Switzerland, 4 – 5 September 2008
IPv6 Matureness
& Challenges
Sheng Jiang
Ph.D., Huawei Technologies
Geneva, Switzerland, 4-5 September 2008
International
Telecommunication
Union
Brief History of IPv6
Primary work started 1989 towards
next generation IP
By 1992, 7 candidate solutions are
available
In July of 1994, IPv6 is recommended,
RFC 1752
By 1998, IPv6 protocol family is
accepted as RFCs
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
2
Brief History of IPv6 （2）
1999-2005, IPv6 specifications were
defined in IETF
2001-now, IPv6 protocol family are
developed
2004-2007, IPv6 deployment was
much slower than expectation
2008- , IPv4 address exhaustion
pushes people focus onIPv6
deployment again
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
3
Motivation of IPv6
32-bit IPv4 address space will be
exhausted
Demand on address is speeding up
15% address blocks are left in IANA now
Unallocated address pool exhaustion can
be foreseen before 2012
IPv6 is the best answer
NAT, private IPv4 addr, IPv4 addr reuse
can postpone the IPv4 address exhaustion
Postpone, but not solve
Create new problems
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
4
IPv6 Advantages
Big address space
128 bits
End-to-End
communication
Improved QoS
support
New security
addressing
Multihoming feature
Mobility feature
Network layer
IPSec
Autoconfiguration
Enhanced multicast
Simplified header
Extensible header
Advanced network services
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
5
IPv6 Protocol Family
Basic IPv6
IPv6 Address, Neighbor Discover,
ICMPv6, Tunnel, etc.
Mobility & Multihoming
MIPv6, Nemo, Shim6
Security
Mandated IPSec, SeND, CGA
Transition
NAT-PT (Deprecated ), Softwire, Dual
stack
DHCPv6, DNSv6
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
6
IPv6 Protocol Matureness
Most of IPv6 Protocols are mature
Relevant IETF WGs are closed, only
maintenance, operation and extension
Incremental deployment and transition
mechanisms are still controversial
IPv6-Ready Products Test
IPv6-Ready Logo Program since 2004,
initiated by IPv6 Forum
Data up to 2008/8/19
Phase 1, 359 products, from 15 countries
Phase 2, 209 products, from 12 countries
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
7
IPv6 Deployment Difficulties
Incremental Deployment is required
The Internet must support continued
IPv4 and IPv6 will co-exist for long time
Communication between IPv4-only and
IPv6-only is required
IPv6 deployment is lack of motivation
IPv4 still work, NAT reduces IPv4 addr
requirement
IPv6 does not give users new experiences
There is no mature IPv6 business model
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
8
Challenge 1: Transition Mechanisms
Dual Stack
No enough IPv4 addresses
need v4/v6 communication support
Tunneling
h
c
r
a
e
s
!
e
g
Protocol Translation
R oin
r
e
V4/v6 communication
mechanism
g
h
n
t
r haslbeen
o
NAT-PT(RFC2766)
deprecated
u
l
F sti issue, end-to-end issue
DNS-ALG issue, security
is
IPv6 over IPv4 network or IPv4 over IPv6 network
need v4/v6 communication
Application Level Gateway or Proxy Server
Low efficiency
Not generic, one ALG per service
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
Union
9
Challenges 2: Looking for
IPv6 Killer Applications
In last ten years, IPv6 society was
f
looking for IPv6 killer applications
l
e
s
t
i
!
Provide users new experiences,
which
e
6
c
v
a
P
IPv4 application can notI
p
s
s ss
i
n
Motivate IPv6 global
deployment
e
o
r
i
t
d
a
d
c
a
i
Most of technical
innovations
in IPv6
l
p
E
Ap ARG
is alsor suitable
for IPv4
e
L
l
l
i
s large address space and
tonly
KSo far,
i
h address cannot be copied in IPv4
t
security
i
w
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
10
Union
Challenge 3: IPv6 Business Model
Traditional model: user requirement
-> carriers -> vendors
s
Users are not care about IPv6 or IPv4
r
o
d
nnot move
Applications also contents are
e
!
v
6
to IPv6
th
Pv
I
o
b
s
IPv6 migration cost
arerd
not profitable
h
s
a
u
for carriers p
w
o
s
t
r
s
e
IPv6 support
from
vendors depend on
i
r
r
e
r demands
s
a
carrier
u
C
d
n
a will not have enough IPv4
Carriers
resources to develop new services
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
11
Union
Summary
IPv6 protocol is mature through it
will not stop to develop further
!
g
n
i
IPv4 address exhaustion
is the main
m
o n!
c
motivation of IPv6
s deployment
o
i
i
t
6
c
v
a
Carriers starts
IP atokefeel the pressure
T
from IPv4 address
shortage
IPv6 industry will increase soon
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
12
Union
Thank you
www.huawei.com
shengjiang@huawei.com
ITU Workshop on IPv6: Geneva, 4-5 September 2008
International
Telecommunication
13
Union