Fix6 – IPv6 News and info

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!

Did you know Google has a Product Ideas for Google website? Perhaps we can raise some awareness how badly we like to have IPv6 support.

So please help out and vote for the following idea:

IPv6 support for Google Mail / Gmail

The Google over IPv6 program allows ISPs with good connectivity to request IPv6 access for most Google services. In about a week, we’ll be adding Google App Engine and the appspot.com domain to this program. This means that all App Engine apps will become accessible over IPv6 to anyone participating in the program!

For most people, this won’t require any changes to your code at all. If your App Engine code reads os.environ["REMOTE_ADDR"] in Python, or HttpServletRequest.getRemoteAddr() in Java, be aware that this value may be an IPv4 address, like “192.0.2.1″, or an IPv6 address, like “2001:db8::1″. Now is the time to verify that your code doesn’t make any IPv4-specific assumptions, so that your IPv6-ready users will have a seamless transition.

More info on http://googleappengine.blogspot.com

Google has started to initiate the enabling of their Youtube site over IPv6.
It is currently available to participants in their Google over IPv6
program, http://www.google.com/intl/en/ipv6/ .

The www.youtube.com user interface so far does *not* have any AAAA
published, but the *much* more important (traffic wise) image and video
servers do.

:~$ host s.ytimg.com
s.ytimg.com is an alias for static.cache.l.google.com.
static.cache.l.google.com has address 74.125.13.213
static.cache.l.google.com has IPv6 address 2001:4860:4001:402::15

:~$ host v1.lscache1.c.youtube.com
v1.lscache1.c.youtube.com is an alias for v1.lscache1.l.google.com.
v1.lscache1.l.google.com has address 74.125.97.80
v1.lscache1.l.google.com has IPv6 address 2001:4860:4001:402::10

Read more about it on the Ripe IPv6 Workgroup mailinglist