Fixed via: https://github.com/tlswg/rfc8447bis/pull/70
Yep!
Fair point, but this one had legs. 1) I went through each of the entries that we are setting to do “D”. Most but not all had links to explain why they got a “D”. This PR at the end includes additions where I think they are needed. The only one that is weird is the curves, because what we did was suggested at IETF 118 that anything under 128-bits should be D. So, this is the draft that’s going to knock ‘em out. We could add that here or just point to the presentation. The PR points to the presentation. 2) This I-D has a very long list of cipher suites. Many of these are in -deprecate-obsolete-kex. -deprecate-obsolete-kex is pinned on this I-D. We’re going to leave those in this draft, but put them in another table and add to the reference column to refer to this draft where we taken them out for being NULL, weak, etc. 3) We should make it clear that when “D” is set that enough information be included to determine why it’s “D”. Added this to the PR ***NOTE the addition of the MUST": When marking a registry entry as “D”, either the References or the Comments Column MUST include sufficient information to determine why the marking has been applied. Here’s a link to the PR: spt |
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
