Re: [DNSOP] Working Group Last Call on "Aggressive use of NSEC/NSEC3"

Warren,

On 04-10-16 18:56, Warren Kumari wrote:
> On Thu, Sep 22, 2016 at 11:04 AM, John Levine <johnl@taugh.com> wrote:
>>> Please review the draft and offer relevant comments. Also, if someone
>>> feels the document is *not* ready for publication, please speak out with
>>> your reasons.
>>
>> I think it's ready to publish with one small caveat.  In section 5.1,
>> the text in the box says "resolvers MAY use NSEC/NSEC3 resource
>> records" and the text in the next paragraph says "the resolver SHOULD
>> use NSEC/NSEC3/wildcard records".  There's a similar MAY in the box in
>> section 7.
>>
>> The authors SHOULD make up their minds.  Assuming they really believe
>> this is a good idea, change the MAY's to SHOULD.
>
> Doh. Thanks.
> This was simply sloppiness on my part.
>
> (my editor shows pre-formatted / figure text on a yellow background,
> and my eye's now assume that that is protocol layout, so I skip over
> it :-)).
> Fixed and pushed to repo in
> https://github.com/wkumari/draft-ietf-dnsop-nsec-aggressiveuse/tree/12b2d9d46a50502e20d33cfa8f2db89ccb6dadff
> - will publish new version with these integrated soon.

To summarize my things:

1. Inconsistent SHOULD and MAY.
2. Get rid of RFC 2119 keywords for configuration recommendations.
3. Reference for "currently around 65% of queries to Root Name servers 
result in NXDOMAIN responses." (and replace currently with "at the time 
of writing")
4. The PR
5. Rewording sections 5.2 and 5.3 by either a repeating exercise (see 
suggested text, or cross-referencing (see Tony's mail).

I think points 2, 3, and 5 were not yet addressed.

Best regards,
   Matthijs

>
> W
>
>
>>
>> R's,
>> John
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>
>
>