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

Warren Kumari <> Sat, 03 November 2018 23:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1679129C6B for <>; Sat, 3 Nov 2018 16:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OUkajlO0n7jD for <>; Sat, 3 Nov 2018 16:56:37 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CE8CD1292AD for <>; Sat, 3 Nov 2018 16:56:36 -0700 (PDT)
Received: by with SMTP id r10-v6so5568538wrv.6 for <>; Sat, 03 Nov 2018 16:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=no/bHtx1QjG6rGo8IF44qOnFdrbdtarCaj4zPL+vQFw=; b=b0Tt2lHuM68pwcM/9uWn/JY1pcazE5+ugUDxQvdmuS4CPFGxt6DNNU19ilnoacu6Bv UghCce5CZwPkEyXAzcUAqID2lRzG7p2BxZ9vxCUu7jPcwRAYoKN/+/iiq/d8XHCDRTrS DEYU2uCFwK3HI5iT7pVwLVb3W0GexOjzLPmMWysFNyWINnfrxy5XSitB6JZOz6RsTzBo g1VJULMmOn4B/jrEsM7MgQEQLtEBdW6kXpiwSzXCd2n+6s/18Xqvq5zt9xaBrbF4ErQc Z20gFqh/ZNqi+Ri5sVSzhma3zjY8238yNP8f4kUa6ulwr/5MjSRjIWC7JH/Jb68LNmeX +caQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=no/bHtx1QjG6rGo8IF44qOnFdrbdtarCaj4zPL+vQFw=; b=IH67MeAWTpUb7wXKuGDTE9CHiJBba11N8FEPC2r6COzk01CKI5P1Wg7KThY4qO688T FvRbeAd6IBz6nR2Fh8iJYkkuWjtFx8bsYd80ht1mJ3gGDNZ/KaQjtL5aTQ4TPZa6V0cb JTvo+5L8uEC0OEfdn2J414mNENO5zSa9ZXFgbawzO7CQKHMtk4SQIrH/+5N7LR5PLIWA OAy7sqRhSjUIknaNpCsORsJsBZZTS/CVeLAJ8Mk9bfPwh1mDcw/Oe+HugtcQZkTEkcAZ OfMd5yX6qEMNewXeDN/CjNDLjWK1LPO4BGC7sxm5FkPKcw9Dh044P4dF8I7fb3pmTgTK ppEA==
X-Gm-Message-State: AGRZ1gJr7k67cN7nfdpRGu7M/IkjCfsCiy+7hQEn0pYMX/rnKzGwvYXp IzB+6/nVbnFpcRJoxPo6tRHdDc5p5XHwP0VCRx3V+9LGz/M=
X-Google-Smtp-Source: AJdET5eeB6ZxlwHNIyopnMGTLIO8Voj+el1GEiPeycJ5+2GABQUXj+LQm0weEgKRsG5pZz2JBi8Dv2dS8mg/MOQD2mw=
X-Received: by 2002:adf:dc87:: with SMTP id r7-v6mr15973704wrj.143.1541289394511; Sat, 03 Nov 2018 16:56:34 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Warren Kumari <>
Date: Sun, 04 Nov 2018 06:55:58 +0700
Message-ID: <>
To: dnsop <>
Content-Type: multipart/alternative; boundary="000000000000db34980579cb66eb"
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-15.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 03 Nov 2018 23:56:40 -0000

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.

7.2.  References -\- Informative

Also nit (I think):
Adam Roach, Petr &#352;pa&#269;ek, Ond&#345;ej Sury

Otherwise I think this one looks cooked.

On Sun, Nov 4, 2018 at 3:23 AM <> 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
>         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:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> DNSOP mailing list

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