Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bcp-02.txt

Hi everyone

Referring back to a little earlier in today's agenda, I've just raised a
two-word PR #9 <https://github.com/paulehoffman/draft-hoffman-dnssec/pull/9>
which
aims to remove a possible misinterpretation of the BCP text by a less
experienced reader.

The PR says:

The current text can be interpreted incorrectly. It essentially says "*DNSSEC
is formally version 3 .... however, earlier versions of DNSSEC were ...
significantly less visible ... Here DNSSEC means the version of the
protocol initially defined in ...*"

The use of the word "*initially*" in the last sentence, in conjunction with
some low-numbered RFC numbers, can lead the reader to think that you are
referring to version 1.

This PR aims to make it clearer that we are pointing to version 3.

Current text:

What we today call "DNSSEC" is formally version 3 of the DNSSEC
specification.

However, earlier versions of DNSSEC were thinly deployed and significantly
less

visible than the current DNSSEC specification. Throughout this document,
"DNSSEC"

means the version of the protocol initially defined in {{RFC4033}},
{{RFC4034}}, and {{RFC4035}}.

Proposed text for the last line:

means version 3 of the protocol initially defined in {{RFC4033}},
{{RFC4034}}, and {{RFC4035}}.

Is this better?

Chris

On Sun, 10 Jul 2022 at 10:33, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations WG of the
> IETF.
>
>         Title           : DNS Security Extensions (DNSSEC)
>         Author          : Paul Hoffman
>   Filename        : draft-ietf-dnsop-dnssec-bcp-02.txt
>   Pages           : 10
>   Date            : 2022-07-10
>
> Abstract:
>    This document describes the DNS security extensions (commonly called
>    "DNSSEC") that are specified RFCs 4033, 4034, 4035, and a handful of
>    others.  One purpose is to introduce all of the RFCs in one place so
>    that the reader can understand the many aspects of DNSSEC.  This
>    document does not update any of those RFCs.  Another purpose is to
>    move DNSSEC to Best Current Practice status.
>
>    This document is currently maintained at
>    https://github.com/paulehoffman/draft-hoffman-dnssec.  Issues and
>    pull requests are welcomed.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-bcp/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-dnssec-bcp-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-dnssec-bcp-02
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>