Hi Russ, Thank you for your response.
Because of the normative chance in the Appendix, please submit a new version of the draft with that updated text. From there, I can request AD approval, and I'll note your answers to version -12 and use those for the draft intake experiment -- so you don't have to answer it twice! I did have an additional question regarding the sourcecode question: >> 5) This document contains sourcecode: >> >> * Does the sourcecode validate? >> * Some sourcecode types (e.g., YANG) require certain references and/or text >> in the Security Considerations section. Is this information correct? >> * Is the sourcecode type indicated in the XML? (see information about >> sourcecode types). > > The use of the TLS Grammar is unchanged from RFC 8773. I see that all the sourcecode elements are set to the type "tls-presentation", except for the two elements in Section 7 that have no type set. Is there a type you would like these two to be set to? Here's the list of our current types: https://www.rfc-editor.org/rpc/wiki/doku.php?id=sourcecode-types Thank you, Sarah Tarrant RFC Production Center > On Sep 5, 2025, at 2:00 PM, Russ Housley <hous...@vigilsec.com> wrote: > > Yes, these are still accurate. That said, I just realized that Appendix A > needs an additional bullet: > > * The client MUST include the "supported_groups" extension in the > ClientHello message. -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
