This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] test-ipv6.com
- Previous message (by thread): [ipv6-wg] internal additional IPv4 assignment policy
- Next message (by thread): [ipv6-wg] test-ipv6.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jason Fesler
jfesler at gigo.com
Tue May 11 19:07:35 CEST 2010
Shane Kerr suggested I post this here; that some of you may find it useful. http://test-ipv6.com or http://aaaa.test-ipv6.com The intent of this site is to help the user what it will mean when publishers start publishing dual-stack. When it makes sense, the test will be updated to indicate what the future looks like when publishers are IPv6 only. The dual stack publishing case is an open question that has been discussed between content and access providers. Measurements published by Google indicate a number of users with IPv6 enabled, routes installed, but the connectivity fails. In this situation, from the user's perspective, the site is down, and the user will go to the competitor's site (Still "up", IPv4 only). Followup measurements by other parties (Tore Anderson published some data; I've seen private data by other organizations) confirm the scale of the numbers Google has seen. While content providers will continue to do their own measurements (whether publicly or privately), they won't likely be indicating to the "broken" users what fate they are facing or how to fix it. This is where I hope something like my site can help, in a brand-neutral way. Please review the FAQ; and if you have comments feel free to send them to me. The site will automatically show a survey form if you have results I don't fully understand; if you see it pop up, please fill it out with contact details in case I need to ask more questions. I've seen lots of crazy things so far! Note: This is a side project of mine, not an employer's. As such, resources are limited. Please don't post this to slashdot - I'm not appropriately resourced for it (both for hardware and finances). -- Jason Fesler, email/jabber <jfesler at gigo.com> resume: http://jfesler.com "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life."
- Previous message (by thread): [ipv6-wg] internal additional IPv4 assignment policy
- Next message (by thread): [ipv6-wg] test-ipv6.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]