Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-15.txt

[Warren Kumari <[e-mail]>]

Nit:
Section 1.5:
"For "TXT" records, there is no consistent, internal syntax that to permits
distinguishing among the different uses."
Spurious 'that' or 'to'.

I'm also somewhat confused by the quoting in:
"In the case of the "SRV" "RR" and "URI" "RR", distinguishing among
different types"  (and in "defining "RR"s that might" ) - I'm not sure if
it is intentional, but it doesn't align with much of the rest of the
formatting, and is (IMO) confusing around the first part.)


Probably nit: Section 2:
"Only global underscored names are registered in the IANA Underscore
Only the global underscored names "_service1", "_service2", Global
table.  (From the example, that would mean registering "_service3",
"_service4", and "_authority" are registered in the IANA _service1,
_service2, _service3, _service 4, and _authority.)"

First sentence repeats.

Nit:
7.2.  References -\- Informative

Also nit (I think):
Adam Roach, Petr Špaček, Ondřej Sury


Otherwise I think this one looks cooked.
W


On Sun, Nov 4, 2018 at 3:23 AM <[e-mail]> 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 Scoped Data Through "Underscore" Naming of
> Attribute Leaves
>         Author          : Dave Crocker
>         Filename        : draft-ietf-dnsop-attrleaf-15.txt
>         Pages           : 14
>         Date            : 2018-11-03
>
> Abstract:
>    Formally, any DNS resource record may occur under any domain name.
>    However some services use an operational convention for defining
>    specific interpretations of an RRset, by locating the records in a
>    DNS branch, under the parent domain to which the RRset actually
>    applies.  The top of this subordinate branch is defined by a naming
>    convention that uses a reserved node name, which begins with an
>    _underscore.  The underscored naming construct defines a semantic
>    scope for DNS record types that are associated with the parent
>    domain, above the underscored branch.  This specification explores
>    the nature of this DNS usage and defines the "DNS Global Underscore
>    Scoped Entry Registry" with IANA.  The purpose of the Underscore
>    registry is to avoid collisions resulting from the use of the same
>    underscore-based name, for different services.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-attrleaf-15
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-attrleaf-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-attrleaf-15
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf