I was browsing the schedule of the upcoming ICANN meetings in San Juan and noticed a logo in the top left corner suggesting that the web site is “IPv6 enabled”.
Unfortunately, we are not there yet. Good try, maybe next time.
hiram:~ patrick$ host sanjuan2007.icann.org
sanjuan2007.icann.org is an alias for ganges.lax.icann.org.
ganges.lax.icann.org has address 208.77.191.173
hiram:~ patrick$ dig ganges.lax.icann.org AAAA
; <<>> DiG 9.3.4 <<>> ganges.lax.icann.org AAAA
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13528
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ganges.lax.icann.org. IN AAAA
Still, congratulations to ICANN for the work they have done to make information more accessible on the web. The only missing piece now is an ICS file to be able to import the meeting schedules directly in our computer or PDA.
Pages:
Still down today, while the San Juan meeting is going one. Tested with two different operators, who both have native IPv6.
Here, from Renater:
% traceroute6 sanjuan2007.icann.org
traceroute to ganges.lax.icann.org (2620:0:2d0:5:218:8bff:fef8:78e0) from 2001:660:3003:8::4:69, 30 hops max, 16 byte packets
1 gw.inge.ipv6.nic.fr (2001:660:3003:8::1) 2.304 ms 2.887 ms 1.322 ms
2 * afnic-g0-3-10.cssi.renater.fr (2001:660:300c:1001:0:131:0:2200) 2.028 ms !N 3.529 ms !N
Works here, through a Teredo tunnel. If anything, this shows there is still some work ahead for operators to guarantee global IPv6 reachability.
It works now, thanks probably to your post
% traceroute6 sanjuan2007.icann.org
traceroute to ganges.lax.icann.org (2620:0:2d0:5:218:8bff:fef8:78e0) from 2001:7a8:7509::1, 30 hops max, 16 byte packets
1 2001:7a8:1:3::c3:301 (2001:7a8:1:3::c3:301) 44.129 ms 44.947 ms 43.552 ms
2 gi0-2-3-edou.ipv6.nerim.net (2001:7a8:1:3::114) 43.841 ms !N 43.745 ms !N 43.806 ms !N
Yes, “network unreachable”, there is now an IPv6 address but no route (tested with two different providers). Still, it was a big effort for ICANN, congratulations.
No, not a risk, just another complication.
Anyway, I believe it’s done now.
Still need to get to ICS – tied up with 1,000 other things at the moment. (Talking of which – should have an IPv6 factsheet ready to go for San Juan.)
Kieren
Hi Kieren,
We get it to IPv6 soon as everything is tested and safe and stable.
Your reaction is quite typical of what I often hear, i.e. that going IPv6 is somehow a risk. Most people are still worried about running IPv6 on productions sytems, while they have no such reservations about deploying a new CMS, although the risks to have an non-operational web site is much higher.
Why do you want an ICS file? I think we have/had vCal.
All these acronyms are quite confusing, indeed. I confess ICS is not a standard, but rather the file name extension for iCalendar, as defined in RFC 2445. vCal is a proprietary format, not to be confused with vCalendar, the predecessor of iCalendar.
See you in Puerto Rico.
Hey Patrick,
I roared with laughter when I saw this. I can’t believe you managed to find the time spot in which the Public Participation site isn’t IPv6.
We made it IPv6 in time for the Lisbon meeting but are currently transitioning to a new server (Ganges) which is just IPv4 at the moment because we wanted to reduce the risk factors as far as possible.
The IPv6 Pub Part site has been up for months and the Ganges transition happened on, um, yesterday I think. This week anyway. So your timing is immaculate.
We get it to IPv6 soon as everything is tested and safe and stable.
Why do you want an ICS file? I think we have/had vCal. Will check it out.
Kieren