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] Happy Eyeballs bias
- Previous message (by thread): [ipv6-wg] Happy Eyeballs bias
- Next message (by thread): [ipv6-wg] Happy Eyeballs bias
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bajpai, Vaibhav
v.bajpai at jacobs-university.de
Wed Oct 26 19:06:41 CEST 2016
> On 26 Oct 2016, at 17:43, Jen Linkova <furry13 at gmail.com> wrote: > > On Wed, Oct 26, 2016 at 5:27 PM, Philip Homburg > <pch-ripeml at u-1.phicoh.com> wrote: >> I wonder, if a host has a global IPv6 address that is not derived from any >> kind of transition technology or tunnel, and setting up a TCP connection is >> either slow or fails, then what percentage is due to an issue close to the >> host and what percentage close to the target. >> >> I.e., if IPv6 is broken is there any reason to believe it is often enough >> due to ISP provided services that is would be worth reporting it in a >> roudabout way. > > I'd say that it is much more likely to be broken close to clients, at > least for Alexa web sites.. We cannot generalise this without empirical data. There is also v6 brokenness (or slowness) in ALEXA websites also that not hosted by large CDNs. -- Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Postdoctoral Researcher Jacobs University Bremen, Germany ===================================
- Previous message (by thread): [ipv6-wg] Happy Eyeballs bias
- Next message (by thread): [ipv6-wg] Happy Eyeballs bias
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]