Mohamed Boucadair has entered the following ballot position for draft-ietf-tls-tls13-pkcs1-06: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-tls-tls13-pkcs1/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi David and Andrei, Thank you for the effort put into this specification. I'm clearing my DISCUSS assuming that https://github.com/tlswg/tls13-spec/pull/1399/files change will be implemented during AUTH48 of draft-ietf-tls-rfc8446bis. ==Inherited from the COMMENTs in my previous ballot, fwiw=== # FIPS 186-4 ## Please add a reference ## s/with FIPS 186-4/with US FIPS 186-4 # TLS Registries CURRENT: IANA is requested to create the following entries in the TLS SignatureScheme registry, defined in [RFC8446]. Isn’t draft-ietf-tls-rfc8447bis authoritative here for registry matters? I would replace the 8446 citation with draft-ietf-tls-rfc8447bis. Cheers, Med [1] https://mailarchive.ietf.org/arch/msg/tls/dimNOvXqeIaYflBK7s51J43p80U/ _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
