Thanks Amanda for the early review, raised PR https://github.com/tlswg/tls-key-update/pull/104 to address the comments. Please see inline
On Thu, 12 Mar 2026 at 06:21, Amanda Baber via RT <[email protected]> wrote: > Dear Authors, > > Before the IETF meeting, we check working group agendas for documents with > IANA-related issues. We have notes about this document: > > https://datatracker.ietf.org/doc/html/draft-ietf-tls-extended-key-update-10 > > Section 13.1: > > There isn’t a registry called “TLS Flags.” Is this the “TLS ExtensionType > Values” registry at > https://www.iana.org/assignments/tls-extensiontype-values? If so, the > “DTLS-Only” field needs to be provided as well, and the labels “Flag Name” > and “Messages” need to be changed to “Extension Name” and “TLS 1.3,” > respectively. "TLS flags" registry will be created by https://datatracker.ietf.org/doc/draft-ietf-tls-tlsflags/ -Tiru > > Section 13.2: > > The link points to > https://www.iana.org/assignments/tls-extensiontype-values, but the “TLS > HandshakeType” registry is part of the other TLS registry group at > https://www.iana.org/assignments/tls-parameters. > > Section 13.3: > > 1) The link here also points to > https://www.iana.org/assignments/tls-extensiontype-values, but the text > refers to the other TLS registry group ("Transport Layer Security (TLS) > Parameters" ). > > 2) In the first sentence of 13.3, the second occurrence of “registry” > should be changed to “registry group.” > > If you have any questions, just let us know. If you'd like to talk in > person, you can find us next to the RFC Editor's table from Monday through > Thursday. You can also request another review at any time by contacting us > at [email protected]. > > For more information about IANA Considerations section requirements, > please see > > https://www.iana.org/help/protocol-registration > > Best regards, > > Amanda Baber > IANA >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
