Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
1
Challenges inIPv6 Address Management
Paul WilsonDirector General
APNIC
2
What is an IP Address?
3
“On the Internet,nobody knows you’re a dog…”
by Peter Steiner, from The New Yorker, (Vol.69 (LXIX) no. 20)
4
www.google.com
www.redhat.com
www.ebay.com
www.dogs.biz
www.apnic.net
www.gnso.org
www.ebay.com
www.doggie.com
www.ietf.org
216.239.39.99
66.187.232.50
66.135.208.101
209.217.36.32
202.12.29.20
199.166.24.5
66.135.208.88
198.41.3.45
4.17.168.6
“On the Internet…”you are nothing but an IP Address!
202.12.29.142
5
What is an IP Address?
IPv4: 32 bits
232 = 4,294,967,296 addresses= 4 billion addresses
e.g. 202.12.29/24 (network address)202.12.29.142 (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 (network address)2001:0400:3c00:af92:: (host address)
6
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
7
My Computer www.cernet.cn2001:0C00:8888:: 2001:0400::
www.cernet.cn ? 202.112.0.462001:0400::
IP addresses are not domain names…
The Internet
DNS
8
Why IPv6?
9
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 policiesand marketing
– Additional complexity and performancedegradation
– “Fog on the Internet”
10
The NAT problem
10.0.0.1 ..2 ..3 ..4
R
61.100.32.0/26(64 addresses)
61.100.32.1 ..2 ..3 ..4
ISP 61.100.0.0/16
The Internet
*AKA home router, ICS, firewall
NAT*
61.100.32.128(1 address)
11
The NAT problem
Internet
10.0.0.1
61.100.32.128
NAT
?Extn 10
Phone Network
10 4567 9876
PABX
12
How are IP Addresses managed?
13
The early years: 1981 – 1992
“The assignment of numbers is also handled by Jon. If you aredeveloping a protocol or application that will require the use of alink, socket, port, protocol, or network number please contactJon to receive a number assignment.” (RFC 790)
1981:
14
IANA address consumption
19831984 1985 1986
19871988 1989
19901991
0
2
4
6
8
10
12
14
16
15
Global routing table: ’88 – ’92
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
Jul-88 Jan-89 Jul-89 Jan-90 Jul-90 Jan-91 Jul-91 Jan-92 Jul-92
16
0
10000
20000
30000
40000
50000
60000
70000
80000
90000
100000
Jan-89 Jan-90 Jan-91 Jan-92 Jan-93 Jan-94 Jan-95 Jan-96
Global routing table: Projection
17
The boom years: 1992 – 2001
“It has become clear that … these problems are likely to become criticalwithin the next one to three years.” (RFC1338)
“…it is [now] desirable to consider delegating the registration function to anorganization in each of those geographic areas.” (RFC 1366)
1992:
18
IANA address consumption
19831984 1985 1986
19871988 1989
19901991
0
2
4
6
8
10
12
14
161983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
0
2
4
6
8
10
12
14
16
various
assigned
ripencc
lacnic
arin
apnic
19
Global routing table
http://bgp.potaroo.net/as1221/bgp-active.html
CIDR deployment
“Dot-Com”boom
Projected routingtable growthwithout CIDR
Sustainablegrowth?
20
Recent years: 2002 – 2005
2004:Establishment of theNumber Resource Organisation
21
Unused
75
29%
RIPENCC
16
6%
LACNIC
2
1%
Historical
89
35%
Reserved
36
14%
APNIC
16
6%
ARIN
22
9%
IPv4 distribution – Global
22
IPv4 distribution – Regional
19992000 2001
20022003
20042005
0.00
0.50
1.00
1.50
2.00
2.50
3.00
apnic
arin
lacnic
ripencc
afrinic
23
IPv4 Allocations – Global top 10
199319941995199619971998 1999 2000 2001 2002 20032004
2005
0
0.5
1
1.5
2
2.5
3
3.5
4
4.5
5
ES
NL
CA
FR
DE
KR
UK
CN
JP
US
24
IPv4 allocations – CN
199319941995199619971998 1999 2000 2001 2002 20032004
2005
0.0
0.2
0.4
0.6
0.8
1.0
1.2
25
IPv4 lifetime
http://bgp.potaroo.net/ipv4
IANA allocations
RIR allocations
Addresses routed
Historical Data Projection
Reclamation?
26
Regional Internet Registries
27
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
28
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– Liaison: IETF, APT, PITA, APEC, ISP-A’s– ITU Sector Member– UN ECOSOC consultative status– Deployment of rootservers…
29
Internet infrastructure support
• ‘Anycast’ root serverdeployments– 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
• Beijing– 90% of queries now
handled locallyhttp://www.apnic.net/services/rootserver
I
KL
30
What is APNIC?
31
IP Address Policies
32
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
33
RIR policy coordination
OPEN
TRANSPARENT‘BOTTOM UP’
Anyone can participate
All decisions & policies documented& freely available to anyone
Internet community proposesand approves policy
Need
DiscussEvaluate
Implement Consensus
34
Global policy coordination
• Local actions have global impact– Consumption or wastage of common resource– Global routing table growth
• Bad behaviour can isolate entire networks andcountries
– 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
35
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
36
Summary
37
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
38
IPv6 – Internet for everything!
39
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!
40
Thank You