On Fri, Jul 15, 2022 at 19:48 Peter Gutmann <pgut001@xxxxxxxxxxxxxxxxx> wrote:
Andrei Popov <Andrei.Popov@xxxxxxxxxxxxx> writes:
>The TLS 1.3 adoption document you reference seems to be based solely on Web
>browser data:
Firstly, this comment is not true. The document covers many interactions. There are non-browser clients, embedded products, and server-to-server interactions in there.
This seems to be near-universal when TLS is discussed, see several previous
examples of this on this list. Just as any new medical breakthrough
announcement needs to have the word "in mice" appended to it, so any
discussion of TLS usage should have "on the web" appended to it unless it's
explicitly not so.
I am not sure what to make of this comment that mixes a science reference with a reference to the French Revolution.
I would say that it is common IETF behavior to claim that clients can’t be updated, so everyone must shoulder the burden of backward compatibility. Browsers show this is not the case, but this also true of my watch, router, and power strip.
Maybe specifications shouldn’t do backflips to require support for 15yr old protocols. I think it is fine to describe the results of dropping support. That’s just the truth.
thanks,
Rob
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
