Internet Governance and the move to IPv6
TU Delft April 2008 Alex Band & Arno Meulenkamp Internet Governance
Community Policies
Internet Resource Statistics
IPv6
2 Internet Governance ISOC
IETF
ICANN / IANA
RIRs
4 The 5 RIRs
5 What is RIPE NCC?
RIPE NCC is –a Network Coordination Center –an independent organisation –a not-for-profit membership association –one of the 5 Regional Internet Registries
6 Registration
7 Goals of the IR System: Registration
Why? Ensure uniqueness of IP address space usage Provide contact information for network operators
How? RIPE Database
Results: IP address space allocated uniquely Contact information available for Internet resources
8 Aggregation
9 Goals of the IR System: Aggregation
Why? Routing table grows fast Provide scalable routing solution for the Internet
How? Encourage announcement of whole allocations (min /21) Introduction of Classless Inter Domain Routing (CIDR)
Results: Growth of routing table slowed down
10 Conservation
11 Goals of the IR System: Conservation
Why? IP address space is limited resource Ensure efficient usage
How? Introduction of CIDR Community based policies to ensure fair usage
Results: IP address space consumption slowed Address space allocated on ‘need to use’ basis
12 IP address distribution
IANA
RIR
LIR
/23 /25 /25 End User
Allocation PA Assignment PI Assignment
13 Community Policies Policy Development Cycle
Need
Evaluation Proposal
Execution Discussion
Consensus
15 How policy is made
ICANN / IANA
ASO
AfriNIC RIPEReach NCC consensus ARIN across communitiesAPNIC LACNIC
AfriNIC RIPE ARIN APNIC LACNIC
community community community community community
proposal proposalGlobal proposalPolicy Proposal proposal proposal
16 Internet Resource Statistics IPv4 Address Pool - Now
Other
Central Registry 16% available
APNIC RIPE NCC
AfriNIC LACNIC source: http://potaroo.net ARIN 18 IPv4 Address Pool - The Future
19 IPv6 IPv6 Basics
IPv6 address: 128 bits – 32 bits in IPv4 Every subnet should be a /64 Customer assignments (sites) between: – /64 (1 subnet) – /48 (65536 subnets) Minimum allocation size /32 – 65536 /48’s
21 Huge subnets
Makes network planning easier Always enough addresses in a subnet DHCP not necessary for address configuration – but still possible Makes scanning subnets useless (botnets) – too many addresses in a subnet
22 IPv6 and IPv4 compatibility?
IPv6 is a different protocol from IPv4 IPv6 hosts cannot talk to IPv4 hosts directly
Tools like 6to4 and other tunneling options only let IPv6 hosts talk to eachother
23 IPv6 Transition
24 IPv6 Allocations
25 Getting an IPv6 allocation
To qualify, an organisation must: – Be an LIR – Advertise the allocation as a single prefix – Have a plan for making assignments within two years
26 Three Views
Who needs IPv6? We have NAT!
We’ll move when staying with IPv4 hurts too much
We’ll move before IPv4 runs out, smoothly
27 More information: www.ripe.net [email protected] [email protected]