Hi,
I just submitted draft-ietf-tls-rfc8446bis-06.
Here is a summary of the Changes since -05. I believe the following
changes are largely uncontroversial and were widely reviewed.
* Advice on key deletion (PR 1282)
* Clarify what unsolicited extensions means (PR 1275)
* close_notify should be warning (PR 1290)
The following got somewhat less review, but I merged in order to get
this in before the deadline. If people feel strongly that I got it
wrong, then please speak up. I also closed a few PRs on these
same topics in favor of the PRs below.
* Discuss the privacy implications of external key reuse (Issue
1287)
* Clarify that you need to ignore NST if you don't do resumption
(Issue 1280)
* Port in text on key update limits from RFC 9147 (Issue 1257)
* Reference RFC 8773 (PR 1296)
* Add some more information about application bindings and cite
6125-bis (PR 1297)
There is one remaining issue, which I was undecided on how to handle:
Security considerations of using same cert for TLS client and server
https://github.com/tlswg/tls13-spec/issues/1291
My sense is that this has seen less analysis than other properties
of TLS 1.3 and we should say that, but I'm open to other approaches.
I don't think the MAY in PR 1292 is sufficient guidance.
Aside from this issue, I believe that this document is ready for
WGLC. If we come to an agreement on how to handle Issue 1921 I
can submit a new draft immediately, or we can treat it as
a LC comment.
-Ekr
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
