John Scudder has entered the following ballot position for draft-ietf-dnsop-dnssec-bcp-05: Yes
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-dnssec-bcp/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks, Paul, for this useful and easy-to-read document. Thanks also to Tim Wicinski for putting in the work to build the excellent evaluation table. ## COMMENT ### Section 1 ~~~ This document lists many (but not all) of the RFCs that should be considered by someone creating an implementation of, or someone deploying, modern DNSSEC. ~~~ Why not list all the ones that should be considered? That seems like a bit of a tease! But maybe (probably?) you meant that the list is not guaranteed comprehensive, in which case perhaps something like this ~~~ This document lists RFCs that should be considered by someone creating an implementation of, or someone deploying, modern DNSSEC. Although an effort was made to be thorough, it would be unwise for the reader to assume this list is comprehensive. ~~~ could be used. But maybe you meant exactly what you wrote, in which case, OK. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
