Download as PDF, PPTX
Uploaded byRIPE NCC
IPv4 depletion & IPv6 deployment in the RIPE NCC service region
The document discusses IPv4 depletion and the deployment of IPv6 within the RIPE NCC service region, highlighting the organization’s role, community engagement, and policy development. It provides statistics on IPv4 address availability and projections for exhaustion, emphasizing the necessity of transitioning to IPv6 for continued internet growth. The RIPE NCC's policies for resource allocation and reclamation, along with strategies for engaging the community in IPv6 deployment, are also detailed.
More Related Content
![Cisco IPv6 Deployment Statics, by Shishio Tsuchiya [APRICOT 2015]](https://cdn.slidesharecdn.com/ss_thumbnails/6-150316212419-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to IPv4 depletion & IPv6 deployment in the RIPE NCC service region
IPv4 depletion & IPv6 deployment in the RIPE NCC service region
- 1. IPv4 depletion &IPv6 deployment in the RIPE NCC service region Kjell Leknes - June 2010
- 2. Outline • About RIPE and RIPE NCC • IPv4 depletion • IPv6 deployment • Engaging the community - RIPE NCC and the RIPE community - Training courses - IPv6 Act Now 2
- 3. RIPE NCC • Since 1992 in Amsterdam • Independent not-for-profit organisation • 6500+ members in 75 countries • One of five Regional Internet Registries (RIRs) • Does not make policies 3
- 4.
- 5. IP address distribution /0 IANA /8 RIR /21 LIR /23 /25 /25 End User Allocation PA Assignment PI Assignment 5
- 6. RIPE NCC services • Distribute resources • Database Reverse DNS - IPv4 • ENUM - IPv6 • K-root name server - AS numbers • E-learning • Training courses - LIR • RIPE Labs - Routing Registry • IPv6 Act Now website - DNS for LIRs - IPv6 6
- 7. RIPE community • Policy forum - Not a legal entity - No official membership - Open to everyone • One RIPE chairman and working group chairs • No voting --> consensus • Work done on mailing lists and at meetings by: - Working groups - Task forces 7
- 8. RIPE meetings • Two RIPE meetings per year • Plenary discussions - Wide ranging topics • Working group meetings - More specific focus • Policy discussions • Exchange of views and information • Interaction with other internet stakeholders 8
- 9. RIPE policy development • Open - Anyone can participate - Policy meetings - Mailing lists • Transparent - List discussions archived publicly - Meetings transcribed • Bottom-up process - By the Internet community 9
- 10. Global policy development AfriNIC RIPE NCC ARIN APNIC LACNIC AfriNIC RIPE ARIN APNIC LACNIC community community community community community proposal proposal proposal proposal proposal 10
- 11. Global policy development ICANN / IANA ASO AfriNIC Reach consensusARIN RIPE NCC across communities APNIC LACNIC AfriNIC RIPE ARIN APNIC LACNIC community community community community community proposal proposal Global proposal Policy Proposal proposal proposal 10
- 12.
- 13. IPv4 address pool- June 2005 Other Central Registry 25% available APNIC RIPE NCC LACNIC AfriNIC ARIN 12
- 14. IPv4 address pool- Now Various Other RIPE NCC 6% AfriNIC available APNIC ARIN LACNIC 13
- 15. What we know • RIRs are in total consistently consuming around 10 /8s each year • There are 16 /8 blocks remaining in the global free pool in June 2010 • Projected exhaustion of the global IPv4 free pool August 2011 • IPv6 adoption is the only way to ensure continued Internet growth 14
- 16. IPv4 address poolprojections IANA Pool RIR Allocations Advertised RIR Pool Today 256 Data Projection 220 192 128 64 0 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 15
- 17. IPv4 allocation reduction • RIPE NCC currently allocates up to 12 months • As of 1 July 2010 - 9 months • As of 1 January 2011 - 6 months • As of 1 July 2011 - 3 months 16
- 18. IPv4 reclamation • RIPE NCC reclaim addressing based on: - Non payment - Returned by LIR - LIRs pending closure • RIPE NCC has so far reclaimed 5,730,304 IPs 17
- 19. The last /8 • LIRs may receive only one allocation • Max allocation size /22 (1024 IPs) • Only available to LIRs having an IPv6 allocation • /16 (65 536 IPs) will be reserved for unforeseen circumstances 18
- 20.
- 21. Getting an IPv6allocation • Must be an LIR • LIR must plan to deploy IPv6 within 2 years • Minimum allocation size /32 - 65536 /48’s • Customer assignments (end sites) between: - /64 (1 subnet) - /48 (65536 subnets) • Every subnet should be a /64 • Announce as single prefix recommended 20
- 22. Getting IPv6 providerindependent (PI) space • To qualify you must: - Demonstrate you will multihome - Meet the contractual requirements • Minimum assignment size /48 • Can only be used for infrastructure 21
- 23. IPv6 allocations andannouncements 1500 RIPE NCC Allocations Announcements 1200 900 600 300 0 2004 2005 2006 2007 2008 2009 22
- 24. IPv6 allocations andannouncements 1500 RIPE NCC Allocations Announcements 1200 900 600 300 0 2004 2005 2006 2007 2008 2009 22
- 25. IPv6 allocations andannouncements 1500 RIPE NCC Allocations Announcements 1200 900 600 300 0 2004 2005 2006 2007 2008 2009 22
- 26. Engaging the community • RIPE / RIPE NCC events - RIPE IPv6 working groups - RIPE cooperation working group - RIPE NCC government roundtables • Other fora: - Internet Governance Forum (IGF) - OECD - ITU events - European Commission (EC) • IPv6 Act Now website 23
- 27.
- 28.