On Friday, 8 February 2019 04:31:18 CET Martin Thomson wrote:
> TLS 1.3 is pretty firm about what you can change in a second ClientHello.
> It lists a small set of allowed changes to extensions (cookie, PSK binder,
> key shares, early data, and padding). For the rest it says that nothing
> can ch
I'd like to hear from some people who plan to implement and deploy this.
Absent that, I'm not sure we should adopt it. Code points are free, so it
doesn't need to be a TLS WG item unless the TLS WG and community are going
to do substantial work on it.
-Ekr
On Fri, Jan 25, 2019 at 10:12 AM Christ
The following errata report has been submitted for RFC8446,
"The Transport Layer Security (TLS) Protocol Version 1.3".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5627
--
Type: Editorial
Rep
The following errata report has been held for document update
for RFC8446, "The Transport Layer Security (TLS) Protocol Version 1.3".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5627
--
St
