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] New on RIPE Labs: The Trouble with NAT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Wed Oct 26 17:39:16 CEST 2016
On Wed, Oct 26, 2016 at 3:54 PM, Sander Steffann <sander at steffann.nl> wrote: > So, how about we go the other way. We want IPv6 to be taken more seriously. What about if we change the algorithm the other way over time: give IPv6 more and more of a head start. That way IPv6 stability and performance become more important over time, without causing brokenness. Something like: > > HE head start = 300 + (months after 2017-01-01) * 30 > > That would provide some incentive to make sure that IPv6 is properly deployed and managed. Well, if you keep increasing the timeout you'll eventually make the failover time worse than it would have been w/o HE. Basically the timeout should be long enough to keep Ipv6 preferred in most of 'non-broken' cases but short enough so if IPv6 is broken, users do not notice the failover. -- SY, Jen Linkova aka Furry
- Previous message (by thread): [ipv6-wg] Happy Eyeballs bias
- Next message (by thread): [ipv6-wg] New on RIPE Labs: The Trouble with NAT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]