|
| News | Profile | Code | Photography | Looking Glass | Projects | System Statistics | Uncategorized |
Blog |
Well, World IPv6 Day has come and gone. I won't bore you with statistics that you can easily search for (like this one).
Anyway, it was a great success, with two unfortunate exceptions.
For the first hour or two, Juniper Networks had an issue with their site being reachable, yet not loading completely for clients behind tunnels. It was identified to be a PMTUD issue, and was fixed shortly after.
For the first 17 hours, Level 3 Communications had a tiny issue with their public website. It simply threw HTTP 404 errors:
I'm not sure why it took them so long to fix. They were also one of the parties that was noticeably absent from the IPv6 providers chat where I hung out throughout the day. Either way, epic fail.
Pretty much everything else worked as planned. It was neat hitting almost every major site via IPv6. YouTube seemed to serve out video from the caches faster via IPv6 than via IPv4. I suspect this was due to Google not rate limiting IPv6 connections, which is nice.
And also, speaking of YouTube.. apparently they are among some of the folks who decided to keep some of their AAAAs around after June 8th. For example, I'm still seeing AAAAs for their streaming servers:
09:50:27.583022 IP 127.0.0.1.22516 > 127.0.0.1.53: 13777+ AAAA? v10.lscache7.c.youtube.com. (44) 09:50:27.590659 IP 127.0.0.1.53 > 127.0.0.1.22516: 13777 1/4/0 AAAA 2001:4860:4003:5::17 (151)
I'm certainly not complaining, video content still downloads quickly compared to IPv4!
One disappointment for World IPv6 Day is Netflix. They seem to have gone in the other direction. Although once providing web services and streaming over IPv6 (via Limelight Networks), they've almost completely abandoned IPv6 after moving their systems to Amazon EC2. Although EC2 is starting to support IPv6, I think they're a long way from actually making it available to all of their customers.
To keep a nice log of things, I threw together a tiny script that parses the participant list and runs the following for each hostname provided:
A snapshot of this taken on Jun 8th at 07:57:57 (EDT) is available here. The source is this web server:
One thing to note in the above snapshot is that if Level3 is taken, hop 3's PTR is erroneous. It's not Dallas1, it's probably NewYork1. Although, maybe they developed some quantum entanglement network interface to make the round-trip time between Dallas and New York lower than 1 ms. Yeah, probably not.
In other news, although my place of employment intentionally did not participate in World IPv6 Day with website dual-stacking, we ended up doing it five days later. Corporate policy forbids me to associate myself with the company name in "blogs and web forums," so I can't actually provide it. However, if you think really big MSO in the United States, you'll figure it out pretty quickly. Also, let's just say that there's a surprisingly large volume of 6to4 traffic. Not much Teredo traffic, but I think I have an idea about that. I also saw a few silly addresses:
Not sure what to think about those, other than.. epic fail! I'll let you figure out why.
One other thing I've noticed.. lots of hits from 2600:1010::/29 and 2600:1000::/28. Yep, these are IPv6 addresses from mobile devices on Verizon's LTE network. And to boot, they've all got an MSS of 1940. This means the L3 MTU is 2000. Anyone with one of those USB dongles care to confirm this?
There's talk about the next IPv6 event lasting for a week. I'm on board for that!
New comments are currently disabled for this entry.
     |
This HTML for this page was generated in 0.002 seconds. |