https://tlswg.org/tls13-spec/auth48/rfc9846.html#appendix-C.4-3 is the offending text.
Right now, this is in the section that talks about tracking. (Another reason to prohibit reuse, I guess.) In practice, this language probably needs to move to the body of the document. And we would, as Ekr notes, prohibit enforcement. noting that previous versions of the specification did not outright prohibit share reuse. And the appendix can change from a requirement to a reference to the reuse prohibition. All of which is a relatively minor change. If Ekr is willing to share a PR, that might help smooth things along :) On Mon, Mar 16, 2026, at 20:49, Simon Josefsson wrote: > "Martin Thomson" <[email protected]> writes: > >> TLS 1.3 is in AUTH48. So this isn't trivial from a procedural >> perspective. However. I think that this is trivial from a text >> perspective. I think that it's worthwhile if possible. > > What actual text are you thinking of? > > This all seems reasonable, but the devil is in the details, and there > could be reasonable corner-cases that would be affected by an overly > broad prohibitation. > > /Simon > > Attachments: > * signature.asc _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
