I have reviewed draft-ietf-tls-rfc8446bis-11.
I think it is becoming commonplace to list errata incorporated into the
document as informative references (eg [Err6151]) and then list in the
Abstract or Introduction which errata the bis document resolves. Please
consider doing this.
I have just gone through all Reported errata against 8446 and confirmed
there are no unresolved errata after going through them all.
Otherwise, I only have two nits:
RFC8996 seems to be a broken reference ? Might be a tooling issue but it is
already broken in the xml file on the datatracker.
[RFC8937] describes a way way for security protocol
A duplicate "way" needs to be removed.
I'm starting a 4 week IETF Last Call on this document now, so the Last Call
won't end during the IETF week.
Paul
_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org
