Alissa Cooper has entered the following ballot position for draft-ietf-dnsop-attrleaf-fix-04: Discuss
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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I think this document needs to state explicitly which updates apply to which existing RFCs. That is, I would expect to see in sections 2.1, 2.2, and 2.3 the list of which documents are updated by each section. I realize this can be intuited, but typically for avoidance of doubt authors specify precisely which updates apply to which documents. This will also clear up the unused references that idnits is pointing out. I would also like to understand why this is going for BCP. There is effectively no shepherd write-up for this draft (it's just a copy of the write-up for draft-ietf-dnsop-attrleaf and talks about this document as the "companion" document) so there is no explanation there. One effect of this being BCP is that it adds a huge number of documents to the downref registry. It's not clear to me that the upside of that is bigger than the downside. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Sections 2.1, 2.2, 2.3: I don't understand why the paragraphs "If a public specification that defines ... MUST be entered into this registry, if it is not already registered" are needed, since the same normative requirement is generically stated in draft-ietf-dnsop-attrleaf. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
