1. IPv6 address deployment status Paul Wilson, APNIC
Internet Week 2000
IPv6 address deployment status
Paul Wilson, 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.

2. IPv6 Address Deployment
Registration records (whois)
Allocations to RIRs and 6BONE
Allocations by RIRs
Assignments
Routing table analysis
Allocated prefixes
Unaggregated prefixes
Prefix distribution
Conclusions
I will be providing figures firstly derived from the registration records (whois databases) maintained by the Regional Internet Registries (including APNIC, ARIN and RIPE NCC), and also by the 6BONE project.
These will include a summary of the allocations and reservations which have been made to these organisations, and of the allocations made by them to other organisations. Where available, I will also give some data about the registrations recorded for IPv6 assignments, made to intermediate ISPS and end sites.
Of course, the registration records in RIR databases do not represent actual usage of any address space, so I have also obtained some data about actual utilisation of IPv6 address space, according to IPv6 routing tables. This is in many ways more interesting than the figures obtained from the whois databases, however it is also more subjective, because the result that is seen depends on the point of observation. I will give more information on this shortly.
I also have some very brief conclusions to provide at the end of the presentation.

3. IPv6 TLA Reservations 6bone SubTLAs TLA 3ffe::/16 reserved for 6bone
RFC2471: “IPv6 Testing Address Allocation”
SubTLAs
TLA 2001::/16 reserved for subTLAs
RFC2450: “Proposed TLA and NLA Assignment Rules”
SubTLA blocks (/23) allocated to each RIR and to the IANA (64 subTLAs each)
RFC2928: “Initial IPv6 Sub-TLA ID Assignments”
IPv6 allocations and reservations have been made as follows:
The 3ffe:: TLA has been reserved for the 6BONE, since RFC2471.
The 2001:: TLA has been reserved for division into subTLAs (that is, into /29 blocks), and from this space each of the RIRs has been allocated a /23 (corresponding to 64 subTLA blocks) for initial allocations to be made. This is in accordance with RFC2928.

4. IPv6 Allocations to RIRs
% whois -h whois.apnic.net 2001:200::/23
inet6num: :200::/23
netname: APNIC-AP-SUBTLAS
descr: Asia Pacific Network Information Center
descr: Level Park Road.
descr: PO Box 2131
descr: Milton QLD 4064
descr: Australia
country: AU
admin-c: HM20-AP
tech-c: NO4-AP
mnt-by: MAINT-APNIC-AP
changed:
source: APNIC
Each of the RIR whois databases contains records corresponding to the allocation that the RIR received from IANA, and also to the allocations and assignments made from that address space.
Each RIR operates an IPv6-compliant database, and APNIC uses the RIPE database code.
This is the record corresponding to APNIC’s initial allocation from IANA.

5. IPv6 Allocations to RIRs
% whois -h whois.ripe.net 2001:600::/23
inet6num: :0600::/23
netname: EU-ZZ
descr: RIPE NCC
descr: European Regional Registry
country: EU
admin-c: NN32-RIPE
tech-c: CREW-RIPE
tech-c: OPS4-RIPE
status: SUBTLA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: RIPE-NCC-HM-MNT
changed:
changed:
source: RIPE
And this is the record corresponding to RIPE NCC’s initial allocation from IANA.

6. IPv6 Allocations to RIRs
% whois -h whois.arin.net 2001:400::/23
American Registry for Internet Numbers (ARIN-001)
4506 Daly Dr
Suite 201
Chantilly, VA 20151 US
Netname: ARIN-001
Netnumber: 2001:0400:0000:0000:0000:0000:0000:0000/23
Maintainer: ARIN
The ARIN Registration Services Host contains ONLY Internet
Network Information: Networks, ASN's, and related POC's.
Please use the whois server at rs.internic.net for DOMAIN
Information and whois.nic.mil for NIPRNET Information.
As you may know, ARIN runs different database code, so its record and output formats are different.
This is the record corresponding to ARIN’s initial allocation from IANA.

7. IPv6 Allocations by RIRs
APNIC :0200::/23
21 allocations (/35)
ARIN :0400::/23
10 allocations (/35)
RIPE NCC 2001:0600::/23
22 allocations (/35)
6bone 3ffe::/16
76 allocations (59 / /28)
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).

8. RIR Allocations over Time
The 21 allocations made in the APNIC region are illustrated here, and of course Japan accounts for the majority of them (11 out of 21 in total).
5 allocations have been made to Korea, 2 to Taiwan, and 1 each to Singapore, Australia and China.
APNIC is unique as an RIR in having a number of National Internet Registries within its membership structure, and JPNIC is one of these NIRs. APNIC is cooperating closely with JPNIC on IPv6 allocations, and most of the allocations in Japan have been made via JPNIC. Organisations requiring IPv6 space in Japan should speak directly to JPNIC about their requirement.

9. APNIC Allocations by Country
The 21 allocations made in the APNIC region are illustrated here, and of course Japan accounts for the majority of them (11 out of 21 in total).
5 allocations have been made to Korea, 2 to Taiwan, and 1 each to Singapore, Australia and China.
APNIC is unique as an RIR in having a number of National Internet Registries within its membership structure, and JPNIC is one of these NIRs. APNIC is cooperating closely with JPNIC on IPv6 allocations, and most of the allocations in Japan have been made via JPNIC. Organisations requiring IPv6 space in Japan should speak directly to JPNIC about their requirement.
Total Allocations: 21

10. ARIN Allocations by Country
In the ARIN region, only 10 subTLA allocations have been made, and these are distributed as shown in this chart (with 8 allocations to the USA, and 1 each to Canada and Mexico).
Total Allocations: 10

11. RIPE NCC Allocations by Country
RIPE NCC has made 22 allocations in total, which are widely distributed across Europe. 7 have been made in Germany, 2 each in France and the UK, and 1 each in a further 11 countries.
Total Allocations: 22

12. 6BONE Allocations by Country
For comparison, 6BONE pTLA allocations have been made in 30 different countries, and the USA accounts for 24 of these allocations.
The next most “active” countries in terms of allocations are: the UK (5), Germany and Japan (4 each), and Switzerland, Denmark and the Netherlands (3 each).
Total Allocations: 76

13. Database Registrations by RIR
The figures shown so far illustrate the allocations made by RIRs and 6BONE to their members, but not the assignments which have been made by members to their own customers.
This chart shows the assignments which have been registered in each of the RIR databases, in addition to the allocations. At the time of writing, ARIN data was not available.
Of course, registration of assignments cannot be enforced, so there is no way of telling how many may assignments have actually been made.

14. Database Registrations – 6BONE
For comparison, the 6BONE registry shows many more assignments, as illustrated here.
This may be evidence of “better behaviour” in the 6BONE community, or simply a result of the maturity of the 6BONE, and the fact that “production” IPv6 address allocations have only been recently made.

15. 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.

16. Allocations Routed (6BONE/CSELT)
Total Prefixes: 129
This chart shows how many of the allocations made by 6BONE and the RIRs are currently appearing in the routing table (as reported by CSELT).
The total height of each bar represents the total number of allocations made by each registry. The blue area represents the number of allocations currently routed, the red area represents the number which have been routed but which were offline when this view was taken, and the white area shows the number which have not yet appeared in the routing table.

17. Prefix Distribution (6BONE/Merit)
Total Prefixes: 234
This chart shows the full prefix distribution, as reported by Merit.
Prefixes in the /24, /28 and /35 ranges are “valid” announcements (in routing policy terms), while all the others are classed as “unaggregated” announcements – that is, longer prefixes which are advertised by various sites.
This particular view of the routing table changes dramatically depending on viewpoint. When this data was gathered, one 6BONE site was reporting a routing table with over 400 entries, and another had less than The APNIC site receives routes which are filtered by our upstream (CISCO), and contains no unaggregated routes at all, so the total size of that routing table is less than 100.
Est. *
* Note: /24 + /28 = 64 prefixes

18. Prefix Distribution (6BONE/CSELT)
Total Prefixes: 54
This chart shows the full prefix distribution, as reported by Merit.
Prefixes in the /24, /28 and /35 ranges are “valid” announcements (in routing policy terms), while all the others are classed as “unaggregated” announcements – that is, longer prefixes which are advertised by various sites.
This particular view of the routing table changes dramatically depending on viewpoint. When this data was gathered, one 6BONE site was reporting a routing table with over 400 entries, and another had less than The APNIC site receives routes which are filtered by our upstream (CISCO), and contains no unaggregated routes at all, so the total size of that routing table is less than 100.

19. Conclusions Useful statistics are available
Allocations and assignments: RIRs
Routing: 6BONE, CSELT, MERIT, etc
However no “complete picture” yet
Need consolidated standard set of stats
RIRs will produce more regular IPv6 stats as allocations increase
Suggestions and requests welcome!!!
In conclusion, these are very early figures on IPv6 deployment.
They have been assembled from various sources, including 6BONE, Merit and CSELT, however one problem is that no site seems to provide a complete picture.
A complete picture of course would include time-sequence data, which would tell us more about changes in the table as time goes on, and it would also provide multiple viewpoints.
APNIC would like in future to incorporate IPv6 statistics into our regular statistics, and also to increase our involvement in analysis of the routing infrastructure, for both IPv4 and IPv6. We would welcome your suggestions.

20. APRICOT 2001
Asia Pacific Regional Internet Conference on Operational Technologies
Premier regional technical conference on Internet operational issues
26 Feb to 2 Mar 2001, Kuala Lumpur, Malaysia
Workshop, tutorial and plenary agendas
Including IPv6 training and presentations
In conclusion, these are very early figures on IPv6 deployment.
They have been assembled from various sources, including 6BONE, Merit and CSELT, however one problem is that no site seems to provide a complete picture.
A complete picture of course would include time-sequence data, which would tell us more about changes in the table as time goes on, and it would also provide multiple viewpoints.
APNIC would like in future to incorporate IPv6 statistics into our regular statistics, and also to increase our involvement in analysis of the routing infrastructure, for both IPv4 and IPv6. We would welcome your suggestions.

21. APNIC Open Policy Meeting
Coming up during APRICOT2001!
Programme includes:
Training on IP address policies and procedures
Special Interest Groups (SIGs)
Address policies and procedures
IPv6 policies and procedures
Routing, DNS, database and others
APNIC Annual Members Meeting: 2 Mar 2001
In conclusion, these are very early figures on IPv6 deployment.
They have been assembled from various sources, including 6BONE, Merit and CSELT, however one problem is that no site seems to provide a complete picture.
A complete picture of course would include time-sequence data, which would tell us more about changes in the table as time goes on, and it would also provide multiple viewpoints.
APNIC would like in future to incorporate IPv6 statistics into our regular statistics, and also to increase our involvement in analysis of the routing infrastructure, for both IPv4 and IPv6. We would welcome your suggestions.

22. Internet Week 2000 Thank you
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.