There are currently 12 open PRs [1] against the DTLS 1.3 specification 
generated in response to Ben's review [2]:

- Require that cipher suites define a record number encryption algorithm (#166)
- PMTU estimates (#168)
- Updates to cookie text (#169)
- Clarify buffering and retransmission requirements (#171)
- Relax age out text (#172)
- Records with bogus epochs should be discarded, not generate alerts (#177)
- RCID excessive (#179)
- Alerts are unreliable (#180)
- Rationale for spare CIDs (#185)
- Forbid going from an empty CID to a non-empty CID (#194)
- Clarify mixing sequence and length settings on the same connection (#195)
- Use DTLS style version values, even for DTLS 1.3 (#196)

Please have a look and provide feedback! Barring objections, we plan to merge 
these on Monday, January 18. We'll then cut a new version of the draft and move 
forward.

Best,
Chris, for the chairs

[1] 
https://github.com/tlswg/dtls13-spec/pulls?q=is%3Apr+is%3Aopen+label%3Aconsensus-needed
[2] https://mailarchive.ietf.org/arch/msg/tls/FJM6OHfvLJP_pF5uUcR86pzrdYo/

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to