Transcript PPT - apnic

Challenges in
IPv6 Address Management
Paul Wilson
Director General
APNIC
1
What is an IP Address?
2
“On the Internet,
nobody knows you’re a dog…”
3
by Peter Steiner, from The New Yorker, (Vol.69 (LXIX) no. 20)
“On the Internet…”
you are nothing but an IP Address!
www.redhat.com
66.187.232.50
www.google.com
216.239.39.99
www.apnic.net
202.12.29.20
www.ietf.org
4.17.168.6
www.ebay.com
66.135.208.101
202.12.29.142
www.ebay.com
66.135.208.88
www.doggie.com
198.41.3.45
4
www.dogs.biz
209.217.36.32
www.gnso.org
199.166.24.5
What is an IP Address?
IPv4: 32 bits
232
= 4,294,967,296 addresses
= 4 billion addresses
e.g. 202.12.29/24
202.12.29.142
(network address)
(host address)
IPv6: 128 bits
2128 = 340,282,366,920,938,463,463,374,607,431,770,000,000
= 340 billion billion billion billion addresses ?
e.g. 2001:0400::/32
2001:0400:3c00:af92::
5
(network address)
(host address)
What is an IP Address?
• Internet infrastructure addresses
– Uniquely assigned to infrastructure elements
– Globally visible to the entire Internet
• A finite “Common Resource”
– Never “owned” by address users
• Managed globally under common policies
– To ensure globally cohesive Internet
– Policies developed by the Internet community
– Implemented by cooperative RIR system
• Not dependent upon the DNS
6
IP addresses are not domain names…
The Internet
DNS
202.112.0.46
www.cernet.cn ?
2001:0400::
2001:0C00:8888::
My Computer
7
2001:0400::
www.cernet.cn
Why IPv6?
8
Rationale for IPv6
• IPv4 address space consumption
– Now up to 10 years unallocated remaining
– More if unused addresses can be reclaimed
– These are today’s projections – reality will
definitely be different
• Loss of “end to end” connectivity
– Widespread use of NAT due to ISP policies
and marketing
– Additional complexity and performance
degradation
– “Fog on the Internet”
9
The NAT problem
The Internet
ISP
61.100.0.0/16
61.100.32.0/26
(64 addresses)
61.100.32.128
(1 address)
R
61.100.32.1
10
..2
NAT*
..3
..4
10.0.0.1
..2
..3
..4
*AKA home router, ICS, firewall
The NAT problem
Phone
Network
Internet
NAT
PABX
61.100.32.128
10 4567 9876
?
10.0.0.1
11
Extn 10
How are IP Addresses managed?
12
The early years: 1981 – 1992
1981:
“The assignment of numbers is also handled by Jon. If you are
developing a protocol or application that will require the use of a
link, socket, port, protocol, or network number please contact Jon
to receive a number assignment.” (RFC 790)
13
IANA address consumption
16
14
12
10
8
6
4
2
0
1983
14
1984
1985
1986
1987
1988
1989
1990
1991
Global routing table: ’88 – ’92
9000
8000
7000
6000
5000
4000
3000
2000
1000
0
Jul-88
15
Jan-89
Jul-89
Jan-90
Jul-90
Jan-91
Jul-91
Jan-92
Jul-92
Global routing table: Projection
100000
90000
80000
70000
60000
50000
40000
30000
20000
10000
0
Jan-89
16
Jan-90
Jan-91
Jan-92
Jan-93
Jan-94
Jan-95
Jan-96
The boom years: 1992 – 2001
1992:
“It has become clear that … these problems are likely to become critical
within the next one to three years.” (RFC1338)
“…it is [now] desirable to consider delegating the registration function to an
organization in each of those geographic areas.” (RFC 1366)
17
IANA address consumption
16
16
14
14
12
12
10
10
various
assigned
ripencc
lacnic
arin
apnic
88
66
44
18
1990
2005
2004
1989
2003
2002
2001
1988
2000
1999
1998
1987
1997
1996
1995
1986
1994
1993
1985
1992
1984
1991
1983
1990
00
1983
1984
1985
1986
1987
1988
1989
22
1991
Global routing table
Sustainable
growth?
“Dot-Com”
boom
Projected routing
table growth
without CIDR
CIDR
deployment
19
http://bgp.potaroo.net/as1221/bgp-active.html
Recent years: 2002 – 2005
2004:
Establishment of the
Number Resource Organisation
20
IPv4 distribution – Global
Historical
89
35%
Reserved
36
14%
APNIC
16
6%
ARIN
22
9%
LACNIC
2
1%
RIPENCC
16
6%
Unused
75
29%
21
IPv4 distribution – Regional
3.00
2.50
2.00
apnic
arin
lacnic
ripencc
afrinic
1.50
1.00
0.50
0.00
1999
22
2000
2001
2002
2003
2004
2005
IPv4 Allocations – Global top 10
5
4.5
4
ES
NL
CA
FR
DE
KR
UK
CN
JP
US
3.5
3
2.5
2
1.5
1
0.5
0
199319941995
19961997 1998
1999
23
2000 2001
2002 2003
2004
2005
IPv4 allocations – CN
1.2
1.0
0.8
0.6
0.4
0.2
0.0
199319941995
19961997 1998
1999
24
2000 2001
2002 2003
2004
2005
IPv4 lifetime
Reclamation?
Historical Data
25
Projection
http://bgp.potaroo.net/ipv4
Regional Internet Registries
26
What are RIRs?
• Regional Internet Registries
– Industry self-regulatory bodies
– Non-profit, neutral and independent
– Open membership-based structures
• Internet resource allocation and registration
– Primarily, IP addresses – IPv4 and IPv6
• Policy development and coordination
– Open Policy Meetings and processes
• Training and outreach
– Training courses, seminars, conferences…
• Publications
– Newsletters, reports, web site
27
What is APNIC?
• RIR for Asia Pacific region
– Established 1993, Tokyo
– 1010 members in 45 of 62 AP economies
– 45 staff, 18 nationality/language groups
• National Internet Registry structure
– All NIR follow same policies
– Very close cooperation with CNNIC and others
• Other activities
–
–
–
–
28
Liaison: IETF, APT, PITA, APEC, ISP-A’s
ITU Sector Member
UN ECOSOC consultative status
Deployment of rootservers…
Internet infrastructure support
• ‘Anycast’ root server
deployments
– Substantial funding by
APNIC
– Working with root
operators (F, I, K, M)
– 10+ deployed to 2004
– Work in progress
• AU (K), JP (K), IN, SG,
KH, PK, CN
KL
I
• Beijing
– 90% of queries now
handled locally
http://www.apnic.net/services/rootserver
29
What is APNIC?
30
IP Address Policies
31
IP address management policies
• Fundamental technical principles
– Provider-based addressing
– Objective demonstrated need
– Conservation, aggregation and registration
• Administrative policies
– “Common resources” – not owned
– Management in common interest
– First-come-first-served allocation
• Constantly evolving through policy process
– By consensus of Internet operator community
– Process is open to all interested parties
32
RIR policy coordination
Need
Anyone can participate
OPEN
Evaluate
‘BOTTOM UP’
Implement
Internet community proposes
and approves policy
33
Discuss
TRANSPARENT
Consensus
All decisions & policies documented
& freely available to anyone
Global policy coordination
• Local actions have global impact
– Consumption or wastage of common resource
– Global routing table growth
• Bad behaviour can isolate entire networks and
countries
– E.g. Spam and hacking
• Inconsistent policies also cause global effects
– E.g. Fragmentation of IP address space
– If widespread, Internet routing is fragmented
– End of global end-end routability
• Address policies must be globally consistent
– RIRs work hard to ensure this
34
Recent proposals
• IPv6 reservations for all countries
– Based on fair measure (population)
– Could help to ensure fairness in future
– Technical impacts need to be studied
• IPv6 allocations to all countries
– Strong risk of diverging policies
– 250 different policy systems?
– Likely to seriously impact global Internet
• Parallel allocation systems
– Competing systems may exhaust limited IP address
resource
– Implications should be studied
35
Summary
36
IP address policy
• A global internet needs global policy
– RIRs and NRO achieve this
– 10+ years of successful experience
• Policy fragmentation
– Internet fragmentation, loss of global routing
• IPv4 has a long history
– Result of early allocations is unfair distribution
– RIRs have ensured that current allocation policies
are fair to all
• IPv6 is being managed better from the start
– RIR system is responsible and fair
– Policy will continue to evolve with the Internet
37
IPv6 – Internet for everything!
38
IPv6 – Summary
• The good news…
– IPv6 is available now!
– IPv6 addresses are very easy to obtain
• The not so good news…
– Complexity: cost and learning curve
– Demand? Do users want it? “Chicken and Egg”
• The reality: A long transition
– “Changing engines mid-flight”
– Long process – 10 years to complete?
• The critical message: Start now!
39
Thank You
40