Deb Cooley has entered the following ballot position for draft-ietf-dnsop-structured-dns-error-25: 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-dnsop-structured-dns-error/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for addressing my discuss (although I would have appreciated an actual response so I didn't have to go searching for the change). My comment on Section 10.1 still stands. While QUIC relies on the TLS handshake, it is not normally specified as 'use TLS 1.3' or later. Also, consider changing the RFC8446 reference to RFC9846, as it was published early this week. ------------------------------------------- Thanks to Joe Salowey for their secdir review - and follow up messages. Section 10.1, para 1: DOQ is mentioned parenthetically, is QUIC (RFC9000) an acceptable transport mechanism? _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
