Murray Kucherawy has entered the following ballot position for draft-ietf-dnsop-compact-denial-of-existence-06: 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/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-compact-denial-of-existence/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Kudos to Andy Newton (incoming ART AD) for spotting these issues that need either discussion or correction: (1) This document uses BCP 14 keywords without citing BCP 14. It also uses some BCP 14 keywords ("recommended") in all-lowercase form, which might be worthy of review. (2) Section 3.1 Paragraph 2: The Next Domain Name field SHOULD be set to the immediate lexicographic successor of the QNAME. The Type Bit Maps field MUST only have the bits set for the following RR Types: RRSIG, NSEC, and NXNAME. (The immediate lexicographic successor is the typical case of the "DNS Name Successor" defined in [RFC4471]). The reference to RFC4471 is informative, but this makes it look like it should be normative. But that would make it a downward reference, since this is seeking Proposed Standard status. How does the WG want to handle this? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Why the "SHOULD" in Section 3.1? What is the impact if I don't do that? Why might I legitimately choose not to do that? "SHOULD" implies there are answers to these questions. Some nits: * Section 1 varies between single and double quotes; is this intentional? * In Section 3.1, s/immedidate/immediate/ * Not at all necessary, but I suggest breaking Section 10 into a subsection for each action. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
