Gunter Van de Velde 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: ---------------------------------------------------------------------- # Gunter Van de Velde, RTG AD, comments for draft-ietf-dnsop-compact-denial-of-existence-06 # The line numbers used are rendered from IETF idnits tool: https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-dnsop-compact-denial-of-existence-06.txt # In this review you find a simple to resolve DISCUSS and a general review with non-blocking COMMENTs # DISCUSS # ======= # The Requirement's Language (BCP14) sections seems missing? I am sure this is an accidental oversight. BCP14 text looks as follows: " 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. " ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # General Review # ============== ## idnits point to a downref RFC 7129 (ISE stream) that is not in the downref register. It was mentioned during LC. # I am rarely working with DNS technology and hence i tend to get lost easily in related acronyms. Would a terminology/reference section make sense for these (NSEC, NSEC3, Empty Non-Terminal names, RRSIGs, etc)? Kind Regards, Gunter Van de Velde Routing Area Director _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
