Re: [DNSOP] Lars Eggert's No Objection on draft-ietf-dnsop-nsec3-guidance-08: (with COMMENT)

Wes Hardaker <wjhns1@hardakers.net> Thu, 12 May 2022 17:04 UTC

From: Wes Hardaker <wjhns1@hardakers.net>
To: Lars Eggert via Datatracker <noreply@ietf.org>
Cc: The IESG <iesg@ietf.org>, Lars Eggert <lars@eggert.org>, draft-ietf-dnsop-nsec3-guidance@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
References: <165226482674.16269.10057802528259757612@ietfa.amsl.com>
Date: Thu, 12 May 2022 10:04:49 -0700
In-Reply-To: <165226482674.16269.10057802528259757612@ietfa.amsl.com> (Lars Eggert via Datatracker's message of "Wed, 11 May 2022 03:27:06 -0700")
Message-ID: <yblzgjmheby.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/an5UgP4nMakBB2QrmcdYAGUbFYg>
Subject: Re: [DNSOP] Lars Eggert's No Objection on draft-ietf-dnsop-nsec3-guidance-08: (with COMMENT)
Precedence: list

Lars Eggert via Datatracker <noreply@ietf.org> writes:

>      DNS Error (EDE) {RFC8914} EDNS0 option of value (RFC EDITOR: TBD).
> {RFC8914} looks like a Markdown citation bug.

Yep.  Fixed.

> ### Stray characters
> 
> The text version of this document contains these HTML entities, which might
> indicate issues with its XML source: `&#269;`, `&#352;`, and `&#268;`

Actually it's the markdown source -- I'll get the names fixed though.

> ### Grammar/style
> 
> #### "Table of Contents", paragraph 1
> ```
> . . . . . . . . . . 10 Appendix D. Github Version of This Document . . . . .
>                                    ^^^^^^
> ```
> The official name of this software platform is spelled with a capital
> "H".

Good point.  Better yet though, I've added a note that the rfc editor
should remove that section anyway.

These are done (but more following):

> #### Section 1.1, paragraph 1
> ```
> lag [RFC5155], which specifies whether or not that NSEC3 record provides pro
>                                ^^^^^^^^^^^^^^
> ```
> Consider shortening this phrase to just "whether". It is correct though if you
> mean "regardless of whether".
> 
> #### Section 2.3, paragraph 1
> ```
> w, ftp, mail, imap, login, database, etc) can be used to quickly reveal a lar
>                                      ^^^
> ```
> A period is needed after the abbreviation "etc.".
>


> #### Section 5, paragraph 1
> ```
> y Covering NSEC Records and DNSSEC On-line Signing", RFC 4470, DOI 10.17487/R
>                                    ^^^^^^^
> ```
> Do not mix variants of the same word ("on-line" and "online") within a single
> text.


I'm very confused now.  That section looks nothing like you above text,
nor is that text anywhere.  And ditto with this one:

> #### Section 7.1, paragraph 2
> ```
> NSSEC zone enumeration algorithm", n.d.. Appendix A. Deployment measurements
>                                       ^^
> ```
> Two consecutive dots.


Were you perhaps reading a different reference or something?


> #### "Appendix A.", paragraph 2
> ```
>  Vixie * Tim Wicinski Appendix D. Github Version of This Document While this
>                                   ^^^^^^
> ```
> The official name of this software platform is spelled with a capital
> "H".

I've marked that section to be deleted by the RFC Editor, but fixed that anyway.

-- 
Wes Hardaker
USC/ISI

[DNSOP] Lars Eggert's No Objection on draft-ietf-… Lars Eggert via Datatracker
Re: [DNSOP] Lars Eggert's No Objection on draft-i… Wes Hardaker
Re: [DNSOP] Lars Eggert's No Objection on draft-i… Wes Hardaker
Re: [DNSOP] Lars Eggert's No Objection on draft-i… Lars Eggert