IPv6 Address Allocation Policies & Procedures

1. IPv6 Address Allocation Policies & Procedures Champika Wijayatunga, APNIC 1st ASEAN IPv6 Summit Oct 20-22, 2003 – Kuala Lumpur, Malaysia

2. Presentation Outline • APNIC Overview • APNIC community and the policy development process • IPv6 allocation and assignment policies • Statistics

3. APNIC Overview

4. What is APNIC? • Regional Internet Registry (RIR)for the Asia Pacific Region • Regional authority for Internet Resource distribution • IP addresses (IPv4 and IPv6), AS numbers, in-addr.arpa delegation • Established 1993 • Operating within ICANN (IANA) structure • Pilot project of APNG in Tokyo, Japan • Relocated to Brisbane, Australia in 1998

5. What is APNIC? • Industry self-regulatory body • Non-profit, neutral and independent • Participation by those who need and use IP addresses • Consensus-based, open and transparent • Membership-based structure • Open to any interested party • Provides formal structure for cost recovery, election of representatives etc

6. APNIC Region

7. Where are APNIC Members?

8. APNIC is not… • Not a network operator • Does not provide networking services • Works closely with APRICOT forum • Not a standards body • Does not develop technical standards • Works within IETF in relevant areas (IPv6 etc) • Not a domain name registry or registrar • Will refer queries to relevant parties

9. What is APNIC’s role? • Resource distribution & registration services • IPv4, IPv6, ASNs, in-addr.arpa, whois • Policy development and implementation • Discuss the policies via mailing lists, Open policy meetings, SIG sessions • Membership reviews and approves policy • Training and education • Effective IP address management: Asia Pacific Policies and Procedures

10. Internet Registry structure ICANN IANA ASO APNIC ARIN LACNIC RIPE NCC NIR LIR LIR ISP ISP ISP ISP LIR LIR LIR ISP ISP ISP ISP ISP ISP ISP ISP

11. What is the APNIC Community? • Open forum in the Asia Pacific • Open to any interested parties • Voluntary participation • Decisions made by consensus • Public meetings • Mailing lists • web archived

12. Global Internet Community APNIC Internet Community APAN SANOG / PITA etc APNIC Members IETF Individuals ISP Associations ISOC Definition – “Internet Community”

13. What does the community do ? • Develops Internet resource policies • Applicable to the use of IP addresses, ASNs etc. • Provides input on the direction of APNIC • open and democratic participatory process • Shares information and experience • Discusses matters relevant to the Internet • A voice in regional Internet operations through participation in APNIC activities

14. APNIC policy development process • Who are involved? • APNIC Members • ISPs, NIRs, etc. • Executive Council • 7 members elected by the APNIC members • APNIC General Secretariat • APNIC’s staff • Internet Community at large • Interested parties

15. Principles of policy development • ‘Bottom up’, consensus based decision making • Community proposes and approves policy • No policies implemented without consensus of community • Open and transparent • Anyone can attend • All decisions archived

16. Principles of policy development OPEN • Anyone can participate Consensus based ‘BOTTOM UP’ TRANSPARENT • Internet community proposes & approves policy • All decisions & policies documented & freely available to anyone

17. Participation in policy development • Why should I bother? • Responsibility as an APNIC member • To be aware of the current policies for managing address space allocated to you • Business reasons • Policies affect your business operating environment and are constantly changing • Ensure your ‘needs’ are met • Educational • Learn and share experiences • Stay abreast with ‘best practices’ in the Internet

18. Open Policy Meeting & Mailing Lists Elements of the process • MM: forum specific to APNIC business eg. fee structure, election of executive council & endorsement of policy decisions MemberMeeting • WGs: semi formal, volunteer group tasked by a SIG to work on • a particular project until completed • eg. ‘Broadband’ Working Groups Special InterestGroups SIGs: Formal groups which discuss broad areas of policy relevant to the APNIC internet community Birds of a Feather • BOFs: Informal meetings to exchange ideas eg. CA BOF, Network Abuse BOF, Training • Need to hold at least one to • form new SIG

19. How does it work? New policy or amendment proposed Posted to SIG ML for discussion Face to face discussions in public open forum (SIGs) Consensus? NO YES Report of consensus in SIG to MM Endorsement by MM? NO YES Implementation 3 months

20. How to get your voice heard • Contribute on the public mailing lists • http://www.apnic.net/community/lists/index.html • Attend meetings • Or send a representative • Gather input at forums • Give feedback • Training or seminar events • Next meeting: In conjunction with APRICOT 2004 - Kuala Lumpur, 24-28 Feb 2004 • http://www.apnic.net/meetings/

21. IPv6 Policies & Procedures

22. IPv6 policy development process Discussions within APNIC community Policy meetings & SIGs, mailing lists etc Consensus of community (Liaison with other RIRs) Regional Policy Variations Membership approval By RIRs and community Policy is implemented

23. IPv6 address policies • Accordance with the Regional Internet Registry IPv6 policy document • http://www.apnic.net/policies.html • Developed through joint discussions among the APNIC, ARIN and RIPE communities

24. IPv6 address policies - goals • Internet is able to function and grow to the maximum extent possible • Aggregation • Hierarchical distribution • Aggregation of routing information • Limiting no of routing entries advertised into the Internet • Efficient address usage • Avoid wasteful practices • Minimise Overhead • Registration of addresses, Uniqueness, Fairness & consistency

25. IPv6 address policies - principles • Address space not to be considered freehold property • License model of allocation • Allocations are not considered permanent, but always subject to review and reclamation • Licenses renewed automatically while addresses in use, consistent with policies

26. IPv6 address policies - principles • Routability not guaranteed • No guarantee that any address allocation or assignment will be globally routable • Minimum Allocation • To facilitate prefix-based filtering • Minimum allocation size is /32 • Consideration of IPv4 Infrastructure

27. IPv6 address management hierarchy IANA RIR RIR LIR/ISP LIR/ISP Downstream ISP Customer Site Customer Site

28. IPv6 addressing structure 128 bits 0 127 32 16 16 64 LIR /32 Customer Site /48 Device /128 Subnet /64

29. IPv6 allocation policy • Initial allocation size is /32 • Allocated to any IPv6 LIR (ISP) planning to connect 200 End Sites within 2 years • This is the default initial allocation to “new” ISPs (“slow start” policy) • Provides 16 bits of site address space • Larger initial allocations can be made if justified according to: • IPv6 network infrastructure plan • Existing IPv4 infrastructure and customer base

30. IPv6 allocation policy • LIR to ISP allocation • No specific policy • Optimum utilization of the total address block allocated to the LIR • All /48 assignments to end sites are required to be registered either by the LIR or its subordinate ISPs • HD-Ratio when a subsequent allocation becomes necessary

31. IPv6 Assignments • Default assignment /48 for all End Sites • Providing /16 bits of space for subnets • End Site defined as an end user of an ISP where: • The ISP assigns address space to the end user • The ISP provides Internet transit service to the end user • The ISP advertises an aggregate prefix route that contains the end user's assignment • ISP POPs (Points of Presence) are also defined as End Sites

32. IPv6 assignments • /48s assignments per end site • /64 only one subnet • /128 only one device connecting • Larger assignments - Multiple /48s • Some end sites will need more than one /48 • Should be reviewed by RIR/NIR • Second opinion process • ISP infrastructure • /48 per POP

33. IPv6 assignments • IPv6 assignments to End Sites used to determine utilisation of IPv6 address blocks • Intermediate allocation hierarchy not considered • All assignments must be registered • Utilisation determined from registrations • Intermediate allocation and assignment practices are the responsibility of the LIR.

34. RIR Registration Allocation LIR Allocation ISP Assignment Assignment IPv6 registration • LIR is responsible for all registrations

35. IPv6 utilisation requirement • Subsequent allocation may be requested when IPv6 utilisation requirement is met • Utilisation of IPv6 address space is measured differently from IPv4

36. IPv6 utilisation requirement • Under IPv4, address space utililsation measured as simple pecentage: • IPv4 utilisation requirement is 80% • When 80% of address space has been assigned or allocated, LIR may receive more • E.g. ISP has assigned 55000 addresses of /16

37. IPv6 utilisation requirement • Under IPv6 utilisation will be measured according to HD-Ratio (RFC 3194): • IPv6 utilisation requirement is HD=0.80 • Measured according to assignments only (intermediate allocations are ignored) • E.g. ISP has assigned 10000 sites from /32

38. IPv6 utilisation requirement • HD Ratio utilisation requirement of 0.80 • RFC3194 “The Host-Density Ratio for Address Assignment Efficiency”

39. Subsequent allocation • Subsequent allocation can be made when HD = 0.80 is reached • Other address management policies should also be met • Correct registrations • Correct assignment practices etc

40. Subsequent allocation • Subsequent allocation size is at least doubled • Where possible, the allocation will be made from an adjacent address block • Resulting IPv6 Prefix is 1 bit shorter • Should be sufficient for 2 years requirement

41. Other conditions • Existing /35 Allocations • A number of /35s have been assigned under interim IPv6 policy • Holders of /35s immediately eligible to request /32

42. Portable IPv6 assignments • For IXPs • Demonstrate ‘open peering policy’ • 3 or more peers • Portable assignment size: /48 • All other needs should be met through normal processes • Critical Infrastructure • Root DNS, ccTLD, IANA, RIRs/NIRs, but not IXPs • Assignment size is /32

43. IPv6 address allocation procedures • IPv6 Allocations to RIRs from IANA • APNIC • 2001:0200::/23 • 2001:0C00::/23 • 2001:0E00::/23 • ARIN • 2001:0400::/23 • LACNIC • 2001:1200::/23 • RIPE NCC • 2001:0600::/23 • 2001:0800::/23 • 2001:0A00::/23 • IPv6 FAQ • http://www.apnic.net/faq/IPv6-FAQ.html

44. IPv6 address request form • IPv6 Address Request form • http://www.apnic.net/apnic-bin/ipv6-subtla-request.pl • Use by organisations requesting IPv6 allocations that they will use for addressing their own infrastructure and making assignments to customers

45. IPv6 address request form • Information Required • Contact details • Structure of the organisation • In terms of how the IP addresses will be utilised • Peering relationships • Does the member have exterior routing protocol peering relationships • IPv6 service plan • Planned addressing structure • ISPs infrastructure • Customer assignments (IPv4 Customers)

46. Statistics

47. IPv4 allocations - global

48. IPv4 growth in Asia Pacific Last Update 26 Sep 2003

49. IPv6 Allocations - Global

50. IPv6 Allocations - Global