APNIC’s pool is low.

APNIC has historically allocated new addresses from IANA when their pool size has been about 2 x /8. Their pool recently got below that number so we can assume that we will see an allocation of 2 x /8 from IANA to APNIC soon.

All the RIR’s pool will be pretty well filled after this allocation. The sum of all the RIR’s and the various pool will be about 21.5 x /8. This is a historically high number. I don’t expect to see any allocations for a while until ARIN and APNIC would have to refill their pool in the November/December time frame.

After that I would expect RIPE and APNIC to allocate in February of 2011 and then finally AfriNIC snatching the last block from the IANA pool somewhere March/April of next year.

Source:  The IPv4 Depletion site

BURSTNET Web Hosting Provides IPv6 IP Addressing Now

BurstNET Technologies, Inc.™, a leading provider of budget hosting services, today announced IPv6 addressing service available end-to-end on its entire product line: including Dedicated Servers, Virtual Private Servers (VPS), & Co-Location.

Complete info at GreatResponder.

RIPE NCC IPv6 for LIRs Training Course

RIPE NCCRIPE NCC announced that they still have some seats for the IPv6 training course that LIR members can attend.

The focus of the IPv6 training course is to raise awareness about IPv6 and the current best practices for deploying it. It also covers IPv6 Internet addressing policies and how to obtain IPv6 address space.

If you are registered as a LIR, and interested in their IPv6 training course, please register though the LIRPortal:

https://lirportal.ripe.net/lirportal/training/course-list.html

More information about the training:

http://www.ripe.net/training/ipv6/outline.html

Tainted blocks?

I first heard about the idea of tainted /8 blocks from Tony Hain from Cisco a few years ago (thanks for sharing your ideas). The fear was that some IPv4 addresses were unusable because some equipment vendors, documents and networks would use addresses from those blocks “illegally”.

One of the most tainted block could be the 1/8 block (Come on, who hasn’t used 1.1.1.1 or 1.2.3.4 in an example in documentation or as an IPv4 for a quick hack). One excellent description of the problem and a study on how tainted those blocks could be can be found in Mark Blachets blog.

Thankfully the problem does not appear to be as severe as initially anticipated. APNIC got the 1/8 block allocated from IANA in January 2010 and started to delegated large chunks of the block in May of 2010 as described here

There are reports about some bogus traffic to a few of the addresses within the 1/8 block. What has happened is that APNIC reserved and trashed a few /24 from the 1/8 block.. Those /24 will probably never be used on the Internet. These blocks in question are 1.0.0.0/24, 1.1.1.0/24, 1.4.0.0/24, 1.10.10.0/24, 1.50.8.0/24 that totaling about 1000 addresses. A whois lookup points them to researchers at APNIC. Most of the rest of the block is now allocated to various APNIC members.

RIPE allocated the 2/8 block from IANA in September 2009. Most of the addresses are used up, for example 2.2.2.2 is delegated to France Telecom. There are no signs of small delegations that are thrown away because of dirtyness in the 2/8 block.

The conclusion that can be drawn is that we do not have to be overly concerned about tainted IPv4 addresses. The problem appears to only affect very specific subnets and IPv4 addresses and not whole /8. I would assume that the same will be seen in other potentially tainted blocks such as 100/8.

Source:  http://www.ipv4depletion.com

Google finally indexing the IPv6 internet

Some good IPv6 news from Google

As of 18th of June (perhaps sooner) the Googlebot has been indexing websites via IPv6:

2001:4860:4801:1109:0:6006:1300:b075 – – [18/Jun/2010:08:46:05 +0200] “GET /robots.txt HTTP/1.1” 200 69 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”
2001:4860:4801:1109:0:6006:1300:b075 – – [18/Jun/2010:09:47:01 +0200] “GET /robots.txt HTTP/1.1” 200 69 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”
2001:4860:4801:1109:0:6006:1300:b075 – – [18/Jun/2010:10:48:06 +0200] “GET /robots.txt HTTP/1.1” 200 69 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”

In the logs of Fix6 i can find these request from the 18th June up until the 19th of July.

The IP is from the Google IPv6 range and resolves to:

5.7.0.b.0.0.3.1.6.0.0.6.0.0.0.0.9.0.1.1.1.0.8.4.0.6.8.4.1.0.0.2.ip6.arpa domain name pointer crawl-2001-4860-4801-1109-0000-6006-1300-b075.googlebot.com.

And that reverse back the the IPv6 address. So its a Googlebot with only IPv6 connectivity!

This is some very good news! Keep up the good work Google!

China Telecom Pilots IPv6

China Telecom has launched pilot projects for Internet Protocol v6 (IPv6) in four provinces, looking to better understand the Internet addressing protocol as it applies to varied industries, such as crop monitoring in greenhouses and property management networks.

Complete info at InformationWeek.