www.facebook.com is v6 here, but I see no AAAA for the fbcdn.net subdomains.
Funny you bring up "getting all the subsidiary sties right".
I tried to comment on an NPR story last night, to find that their
AJAX comment popup points to *an HTTPS* server... whose cert expired
at 1752 on 6/6. I pointed that out to both @nprtechteam and @acarvin
around 10pET when I noticed it... and got no reply from either, which
is slightly unusual for them.
Worst part: Unscrollable box, so I *couldn't* just bypass it even if
I'd wanted to. Oops, Mozilla...
Cheers,
-- jra
... and Gmail, too ...
/TJ
I thought I'd heard that LTE transport was *IPv6 only*...
Cheers,
-- jra
Now I'm seeing it. Quite the short TTL:
; <<>> DiG 9.6-ESV-R4 <<>> AAAA www.facebook.com @glb2.facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34595
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.facebook.com. IN AAAA
;; ANSWER SECTION:
www.facebook.com. 30 IN AAAA 2620:0:1c00:0:face:b00c:0:1
;; Query time: 34 msec
;; SERVER: 69.171.255.10#53(69.171.255.10)
;; WHEN: Tue Jun 7 17:32:31 2011
;; MSG SIZE rcvd: 62
Earlier I was getting no AAAA:
; <<>> DiG 9.6-ESV-R4 <<>> AAAA www.facebook.com @glb2.facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32876
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.facebook.com. IN AAAA
;; AUTHORITY SECTION:
www.facebook.com. 500 IN SOA glb01.sf2p.tfbnw.net.
hostmaster.facebook.com. 2008102433 10800 3600 604800 86400
;; Query time: 29 msec
;; SERVER: 69.171.255.10#53(69.171.255.10)
;; WHEN: Tue Jun 7 16:27:29 2011
;; MSG SIZE rcvd: 101
That is expected, the CDN is not IPv6 enabled (yet)
Anyone with native v6 want to help me test my content? I don't have any v6 access from anything except a few dedicated servers yet. Off list response is fine 
Good catch, applies to pop & smtp as well. Baby steps, I guess?
/TJ
Anybody keeping any realtime stats ?
-J
I'm observing our netflow of the ipv6 address-family from nodes where we're capable. It's not that interesting actually. I've seen larger spikes than what we're seeing [so far].
Akamai has a realtime IPv6 stats page as well here:
You can check out the hits/second peaks of what they're seeing. I do wonder if it will just taper off over time, or if we will see a big spike during the day in EU.
I know for my "geeknet" here at home, I'm seeing all the ipv6 enabled properties flow through, mostly facebook and google, including the analytics site which actually is likely collecting the most interesting data of all.
- Jared
Thanks for the link Jared.
I wonder how many eye-balls are really enabled to reach the IPv6
sites. Akamai's site doesn't show very impressive numbers, trying to
figure why 300ms latency and >4% packet loss ?
-J
My guess is it's over the entire set of akamai properties hosted there, so cisco, bing, etc.. that all point to edgesuite and their related domains.
The latency is likely due to suboptimal tunneling vs native. The density of IPv6 peering likely doesn't fully match the rest of the world either, sometimes you have to go across the country because someone can't do v6 on the local port.
I do also find it interesting there's not a significant spike at the AMSIX IPv6 sFlow page either.
http://www.ams-ix.net/sflow-stats/ipv6/
We have seen a traffic increase but nothing like what I was expecting, nay hoping to see. (i.e.: gigs and gigs of traffic - it does look like ~2x to me in an unscientific eye-look at a chart).
Some of this may just be due to the methods used by the various sites to enable IPv6. (e.g.: main site only, not sub-sites, and not things like fbcdn etc).
There are people listed on the ISOC site that are not serving up AAAA records either, so perhaps they are doing last minute testing and we will see an increase as a result. It's still early to measure a final result obviously, but the observation part is quite interesting for me now. I do hope to see more traffic over the next 12-24 hours. Maybe the "asia peak" time will be most interesting….
- Jared
I was wondering the same thing... we have v6 enabled to about 700 users in our native Ethernet to the home deployment here in Seattle. Unfortunately, user routers don't seem to often support v6 resulting in only about 2-8% of users in most buildings using it, and most of those are just people plugged directly into the wall jacks we provide without routers. I wonder how long it will take for everyone to upgrade their home routers.
John
If all the home CPE router vendors stopped shipping IPv4 only boxes,
not that long. At the moment the price point for IPv6 CPE routers
is still 2-3x the IPv4 only boxes when you can find one though not
all of that difference is IPv6. The IPv6 boxes often have multiple
radio and other extras. This shows that CPE vendors still see IPv6
as something *extra* and not something that should be *standard*.
Mark
Some sites still require ipv4 to load properly (stylesheets, statics,
etc)
disable ipv4 on your machine and go to:
http://www.facebook.com
http://www.cnn.com/WORLD/
http://www.yahoo.com/
I guess it is a start though.
LTE supports both IPv4 and IPv6 (of course) but some operators deploy IPv6 only (with NAT64). (e.g. T-mobile, although their '4G' network is actually 3G with the latest high speed features, +1 for innovative marketing department)
/Joakim
The D-Link DIR series v6 capables are not actually more than about a 10%
premium over the corresponding ipv4-only competition.
I see them in computer stores fairly regularly these days.
Owen
Sadly, although I can connect over IPv6 to Gmail an email sent from within the browser to an IPv6-only address (AAAA but also an MX) still gives the "DNS Error: DNS server returned answer with no data" message.
Transport is one thing but getting applications working with an IPv6 world will take longer (not that it is that hard )
Cheers
Neil
Some of it may be down to client behaviour. Despite Facebook being a 30 second TTL, I had to flush my MacOS X DNS cache before I'd get the new AAAA record.
Tim