> On Jun 2, 2016, at 10:49 AM, David Benjamin <david...@chromium.org> wrote:
>
> I'm not sure I follow. The specification certainly spells out how version
> negotiation is supposed to work. That hasn't stopped servers from getting it
> wrong. Fundamentally this is the sort of thing where bugs don't get noticed
> until we make a new TLS version, and we don't do that often enough to keep
> rust from gathering.
A better way to keep rust from gathering is to not instutionalize fallback,
force the broken sites to deal with the issue. While 2% is noticeable, you
can probably drive 1.3 version intolerance out of the ecosystem relatively
quickly if Chrome implements fallback for a limited time (say 6 months after
TLS 1.3 RFC is done) and with a diminishing probability (60% first month, 10%
less each month thereafter), season to taste.
--
Viktor.
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
