APNIC is deeply involved in research and development initiatives that are designed to inform the basis of APNIC's operational and policy activities. These include data collection and analysis, speculative research, and standards development with both a short and long term focus.
The Asia Pacific region leads the world in terms of the rate of Internet deployment, with the strongest demand for IP resources stemming from the cutting-edge technological developments of the region's maturing societies. APNIC conducts extensive research into the depletion of the free pool of IPv4 addresses to predict timelines for IPv6 transition.
In order to guide the development of the Internet, accurate measurement and analysis of network activity is essential. APNIC participates in research initiatives such as the Day In The Life of the Internet project to provide the raw data for discussions of the operational future of the Internet.
APNIC also develops new and important technologies such as the APNIC Resource Certification project, whereby the rightful owners of Internet number resources can be unequivocally verified.
It is through these initiatives that APNIC contributes to the technological development of the Internet in the Asia Pacific region.
Daniel Karrenberg, Chief Scientist at the RIPE NCC, has just published an interesting analysis of RIPE NCC's IPv6 delegations per month (see A Look at IPv6 Allocations Since 1999). In that analysis, he identifies three distinct phases of IPv6 allocations: experimental (1999-2002), early adopters (2002-2007) and deployment (2007 to now).
So how does APNIC's data on IPv6 allocations compare to the Karrenberg's analysis of RIPE NCC allocations? It's actually very similar. For more information see:
Network 126.96.36.199/8 has been assigned by IANA to APNIC on the 19th January 2010, for use for as public unicast space for further address allocations and assignments. Before APNIC commences allocations and assignments from this space, APNIC has undertaken a study into 188.8.131.52/8. The particular question under investigation here is the extent to which addresses in network 184.108.40.206/8 are an "attractor" for unwanted traffic. In particular, is there a significant level of "leakage" of supposedly private use traffic directed to addresses in 220.127.116.11/8 that leak into the public Internet?
The report on this study is now available at:
and a PDF (which has more readable graphics) is at:
and two recommendations are included in this report regarding reservations of particular address blocks and further followup studies.
We would be interested in any comments on this report and its recommendations. Please followup to email@example.com, or directly to us at firstname.lastname@example.org if you prefer.
A number of DNS experts and APNIC R&D staff have collaborated on a write up of an emerging problem in DNSSEC: what happens when your keys roll over, but the deployed client/resolvers don't update their hand-installed trust? It looks like low traffic volumes have masked a problem of aggressive re-querying by the resolver, which has the potential to cause unexpected traffic surges on the nameservers behind a DNSSEC signed zone, all the way to the root.
We think this is a timely document considering that IANA is proceeding with the DNSSEC signed root in the first half of this year. The work has flagged the potential for high traffic levels, promiscuously to NS in delegation chains with DNSSEC enabled and misconfigured trust, which are proving difficult to eradicate at source.
It's online at http://www.potaroo.net/ispcol/2010-02/rollover.html
Day In The Life (DITL) Discusses some of the key observations made in a 2008/2009 data comparison.
An APNIC Research Youtube channel Has been created with 15 movies from the DITL data collection.
An overview of How the DITL data was processed has also been added.