I am not sure whether that draft is applicable here as there is
another draft for the Internet of Things. If that draft was
applicable, I read it as meaning that:
(a) A new protocol has TLS v1.3 is the default setting.
(b) A new protocol may specify TLS v1.2 as a non-default setting.
That's a bit confusing to me. There is some text in RFC 8446,
Section 4.2.1, which defines a "supported_versions" extension. That
text offers a better view of how the TLS might work.
I am confused by multiple uses of “that draft.” The uta-require-tls13 draft doesn’t say the above; it adds RFC 2119 words and has some paragraphs explaining when to use TLS
1.3 and 1.2. So I assume you mean the “[other] draft for the Internet of Things.” Which draft is that? Perhaps those authors might find the explanations in the require-tls13 document helpful.
The draft states that it discusses post-quantum cryptography and then
goes on to say that it is only possible to get that in TLS v1.3. It
might an effective call to action for a non-technical audience.
And that is one goal – stated in meetings, but probably not written down in email or otherwise – of this document.
|
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
