Well hard for them to establish an ipv6 connection, none of the domains for
the urls I posted have an record :-)
-J
On Mon, Dec 5, 2022 at 1:02 PM Tom Beecher wrote:
> But IPv6Foo , ast least as far as I could tell by quickly looking at the
> code, cannot tell you if an IPv6 connection WO
But IPv6Foo , ast least as far as I could tell by quickly looking at the
code, cannot tell you if an IPv6 connection WOULD have worked, but IPv4 is
where it ended up.
With Happy Eyeballs, if the IPv4 TCP session finishes up only a couple ms
faster than the IPv6 ones, the v4 one wins out. That does
With IPv6Foo you can click on the icon and it will show you a table listing
what URLs are serving some piece of a given page with v6 and v4.
LinkedIn for example shows the main feed page served via v6 but there are a
couple of pieces with v4 from these sites
- dpm.demdex.net
- lnkd.demdex.net
- p
Often lost in the 'debate' about V6 adoption is that for a 100% native IPv6
experience to work, there are multiple other components that have nothing
to do with the network that ALSO have to work correctly. Any issues with
these are likely going to cause fallback to v4.
It's very difficult to know
Nothing you have said has changed my thoughts or opinions on this proposal.
It still has many direct technical deficiencies , not to mention continuing
to rely on a status change of 240/4, of which there is no forward movement
on actually happening.
I no longer have interest in continuing the conv
5 matches
Mail list logo
