[DNSOP] Review of draft-ietf-dnsop-nsec-aggressiveuse-08

Jouni Korhonen <jouni.nospam@gmail.com> Mon, 27 March 2017 17:49 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: ops-dir@ietf.org
Cc: dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149063698126.30570.4959246116267967756@ietfa.amsl.com>
Date: Mon, 27 Mar 2017 10:49:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xoZJjhzzUpBfM4jMVuqc5bMJbE8>
Subject: [DNSOP] Review of draft-ietf-dnsop-nsec-aggressiveuse-08

Reviewer: Jouni Korhonen
Review result: Has Nits

I think would be ready if it passed IDnits. I found the document good
read and found no sinkholes in it. Pointing up two implementations was
also great.

The Proto Write-up seems not be up to date with what IDnits says e.g.,
when it comes to downrefs, which is what the IDnits complain about.

A couple of editorials:

Lines 118-119 says: "This takes this.." I would reword to something
like:
   "This document takes using NXDOMAIN information for more effective
caching further."

Lines 396 and 397 uses "is NOT" and "IS making". I would use lower
case here. No reason to use capitalized and still non-RFC2119
language.

Line 407 is would be great to indicate since which version of Unbound
support has been in place.

[DNSOP] Review of draft-ietf-dnsop-nsec-aggressiv… Jouni Korhonen
Re: [DNSOP] Review of draft-ietf-dnsop-nsec-aggre… fujiwara