IPv6 Address Allocation APNIC IPv6 Summit July 2-6 2001, Korea Anne Lord, APNIC My name is Paul Wilson, Director General of APNIC, the Asia Pacific Network Information Centre. APNIC is the Regional Internet Registry for the Asia-Pacific region, and since 1999 we have had responsibility for distribution of IPv6 address space in this region. This presentation will provide some recent figures on the actual deployment and usage of IPv6 address space.

Overview Address Policy Deployment Status Gobal policy document status Current issues Deployment Status Allocation analysis Database registrations Routing announcements

Policy Development Oct 1998 Initial discussions RIRs/IETF and RIR communities Jul 1999 Provisional policy document released Aug 1999 IPv6 allocation service began Oct 1999 Review of policy document after early deployment experience 2001 Revised policy document to be published following extensive IETF/community input 2002… Policies always subject to change

Current Status Consensus on Discussion ongoing /48 for a “site” If no need for subnets, less can be used Discussion ongoing Almost 100 SubTLA’s allocated End of bootstrap period? PI assignments Policy needed in IPv6? Address architecture IETF/RIR recommendations – revision of rfc2374

IPv6 Addressing – RFC2374 Aggregatable Global Unicast Format RFC2374 (FP001) 128 bit addresses Mixes technology and policy FP TLA ID Reserved NLA ID SLA ID Interface ID 3 bits 64 bits 13 bits 8 bits 24 bits 16 bits Public toplogy (48 bits) Site topology (16 bits) Interface Identifier (64 bits)

IPv6 Addressing - Proposal IPv6 Unicast Addressing Proposal: Separate technology and policy FP Site Interface ID 001 45 bits 16 bits 64 bits Recommended IANA allocation Recommended “site” boundary

Next APNIC Meeting APNIC 12, Taipei Policy discussions A warm welcome! http://www.apnic.net/meetings Policy discussions Joint IPv6/Address Policy SIG Wed 29th August A warm welcome! To anyone with interest in IPv6 policy development especially this community Feedback and input requested

In the Asia Pacific Region IPv6 Allocations In the Asia Pacific Region

IPv6 Allocations by RIRs APNIC 2001:0200::/23 29 allocations (/35) ARIN 2001:0400::/23 17 allocations (/35) RIPE NCC 2001:0600::/23 37 allocations (/35) The RIRs have been making IPv6 allocations since May 1999 (for around 20 months now), and they have made a total of 53 allocations in total. APNIC and RIPE NCC have made an average of around 1 subTLA allocation per month, while ARIN is making allocations at around half of that rate. Under the slow-start allocation policy, only the /35 prefix is allocated initially, but the entire /29 is reserved. So far, no further allocations have been made to holders of /35 allocations. By comparison, the 6BONE registry records 76 pTLA allocations in total (/24 and /28 prefixes).

APNIC Allocations by Country Total Allocations: 29

IPv6 Allocations Over Time APNIC allocations to 18 June 2001 Since August 1999 7 in 1999 15 in 2000 7 in 2001 By organisation 6 Research ISPs 3 Government ISPs 20 Commercial ISPs

Registry Coordination Request evaluation Peer review by all RIRs of IPv6 SubTLA requests Ensures global consistency Accuracy Discussion of difficult cases Consult with 6Bone Policy document Needs global agreement on policy

IPV6 Members Update Feedback from members > 1 year Type of services being provided IPv6 connectivity, interoperability tests, experimental services, ftp servers , web browsing Connectivity Connected to 6TAP and other IPv6 networks in the region Network implementation Native IPv6 & tunneling

APNIC IPv6 Dissemination Training courses Expanded module on IPv6 architecture Open seminars Introduction to IPv6 Tutorials In conjunction with APNIC meetings FAQ http://www.apnic.net/faq/IPv6-FAQ.html

Database Registrations by RIR

Prefix Distribution – APNIC Router Total Prefixes: 192

Routing Table Analysis Registration does not indicate usage Allocation records are reliable to determine who “might” use address space Assignment records may be incomplete Actual usage shown by routing tables However, this is a subjective view depending on point of observation Also, view changes constantly with time As mentioned earlier, there are some problems with trying to assess address deployment through the registry databases. First, only the allocation records can be trusted as truly up to date and complete, as the registries will add these records at the time of making an allocation. Second, assignment records may be registered any time before or after an assignment is made. In any case, registrations do not relate directly to the usage of address space, in terms of its “connectedness” to the internet. To assess actual utilisation of the address space, it is necessary to look at the Internet, specifically at routing tables that indicate whether a block of addresses is connected. When we do this we must realise however that the view of the routing table depends on the point of observation, and may change dramatically from place to place. In the slides which follow, I present data from the 6BONE routing table, collected from CSELT and Merit.

Questions?