On 6/22/16 at 5:24 PM, martin.thom...@gmail.com (Martin Thomson) wrote:
To be clear about this, I expect that browsers will do some fairly
horrific things in response to this. We will attempt to use 0-RTT,
get TLS 1.2 and abort as described.
But then we will do the shameful thing and fall back to 1.2. Plotting
out the alternatives, I don't really see a better option.
Well, it seems like a browser could try TLS 1.3 without 0-RTT first.
If it connects with 1.3 non-0-RTT, then it could mark the host
as not supporting 0-RTT for a day or so and after that time
retry to see if the host has been fixed.
Cheers - Bill
-----------------------------------------------------------------------
Bill Frantz | Since the IBM Selectric, keyboards have gotten
408-356-8506 | steadily worse. Now we have touchscreen keyboards.
www.pwpconsult.com | Can we make something even worse?
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
