[ipv6-wg] New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
- Previous message (by thread): [ipv6-wg] New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
- Next message (by thread): [ipv6-wg] New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
MarcoH
marcoh at marcoh.net
Wed Jun 12 15:56:10 CEST 2013
> Dear colleagues, > > Please see a new article on RIPE Labs contributed by Stephane Bortzmeyer: > > How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)? > > https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-believe-they-have-ipv6-but-are-wrong (private contribution to this list as "somebody who cares") This seems to highlight the problem that "Happy Eyeballs" was invented to hide: clients who think they have connectivity but in reality don't. Now I appreciate HE as the customer friendly approach in suppressing the negative effects (timeouts) of this, but if the problem is as big as you say it is, namely over 10% this is a very nice and very big "disaster waiting to happen." What happens when the first true IPv6-only services appear on net, that is 10% of your install base calling the support desk (if you're lucky) or taking their revenue elsewhere? Which leads to some questions: -Is 10% really a representative figure or do RIPEatlas probes have a higher chance of living in some experimental (and potentially broken) network. -Should there be some effort undertaken in finding the cause of this brokenness and getting it fixed. And ultimately, is there anything the IPv6 WG should or could do? Marco
- Previous message (by thread): [ipv6-wg] New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
- Next message (by thread): [ipv6-wg] New on RIPE Labs: Measuring IPv6 Capability of RIPE Atlas Probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]