I’m reviewing the html document as I have forgot how to read XML bloat, 

Affiliation: do I really need one ? 
OLD: 
Retired/Unaffiliated

NEW: 
Retired/formerly Cloudflare 
or 
NEW: 

Comment: 
I hate reading RFC’s where lower case of RFC2119 words appears in a section 
that has RFC2119 words, see the 3 used of should in section 3.5 that 
reads like a specification section not as guidance section
Section 3.5 paragraph 1
OLD: 
that should not appear 
NEW:
that SHOULD NOT appear

Section 3.5 paragraph 1
OLD:
response should be. 
NEW: 
response ought to be.

Section 3.5 paragraph 2
OLD: 
resolver should not forward
NEW:
resolver SHOULD NOT forward

Section 3.5 paragraph 3
OLD:
type that should not appear

NEW: 
type that ought not appear

Section 4. paragraph 3
OLD: 
The NSEC3 parameters should be set to algorithm 1
NEW: 
The NSEC3 parameters SHOULD be set to algorithm 1

Section 7.1 
OLD: 
insists that pseudo-types must be clear 
NEW:
insists that pseudo-types are not set 

Section: 2 paragraph 3 
OLD: 
in addition to the required RRSIG
NEW: 
in addition to the mandated RRSIG

Other points:
Section 4: redundant word confuses message 
OLD: 
This protection is already better provided
NEW:
This protection is better provided

Section 3.1 bad guidance on TTL value 
OLD: 
a.example.com. 3600 IN NSEC \000.a.example.com. RRSIG NSEC NXNAME

NEW: 
a.example.com. 300 IN NSEC \000.a.example.com. RRSIG NSEC NXNAME

Section 3.4 (bad TTL guidance) 
OLD: 
sub.example.com. 3600 IN NSEC sub\000.example.com. NS RRSIG NSEC

NEW:
sub.example.com. 300 IN NSEC sub\000.example.com. NS RRSIG NSEC


I will wait for others to comment on those suggested changes before giving my 
approval 

Olafur

> On Aug 13, 2025, at 15:19, Rebecca VanRheenen 
> <rvanrhee...@staff.rfc-editor.org> wrote:
> 
> Hi Christian,
> 
> Thanks for the reply! We noted your approval on the AUTH48 status page for 
> this document (https://www.rfc-editor.org/auth48/rfc9824). Thank you also for 
> reviewing Med’s suggestions for the question about inclusive language; we 
> updated the document accordingly.
> 
> We will now wait for Ólafur’s review and approval. He let us know that he 
> will be traveling until mid August and will review once he returns.

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to