Re: [DNSOP] [art] Another look - draft-ietf-dnsop-attrleaf-05.txt

Paul Vixie <> Sat, 31 March 2018 18:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8D777127077 for <>; Sat, 31 Mar 2018 11:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id btbMY74Esh69 for <>; Sat, 31 Mar 2018 11:46:07 -0700 (PDT)
Received: from ( [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2B925127076 for <>; Sat, 31 Mar 2018 11:46:07 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dd04:78fb:edc1:47b1] (unknown [IPv6:2001:559:8000:c9:dd04:78fb:edc1:47b1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id E3F197594D; Sat, 31 Mar 2018 18:46:06 +0000 (UTC)
Message-ID: <>
Date: Sat, 31 Mar 2018 11:46:04 -0700
From: Paul Vixie <>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: "John R. Levine" <>
References: <> <> <> <> <> <alpine.OSX.2.21.1803211104210.9553@ary.local> <> <5F44FA5B42805C52479DE491@PSB> <> <1DF1564CC2B88726B2B54CF4@PSB> <> <4C79BE1080735A41C8697C8D@PSB> <alpine.OSX.2.21.1803260915260.19119@ary.local> <0DC55A40A5F920C5F41AB044@PSB> <> <alpine.OSX.2.21.1803262042080.19530@ary.home> <> <alpine.OSX.2.21.1803310814090.2524@ary.qy>
In-Reply-To: <alpine.OSX.2.21.1803310814090.2524@ary.qy>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] [art] Another look - draft-ietf-dnsop-attrleaf-05.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 31 Mar 2018 18:46:09 -0000

John R. Levine wrote:
> Catching up:
> ...
>> if you view the use of _tcp by more than one rrtype as a coincidence
>> rather than as evidence for the need for a registry, then we can
>> simply define the global registry out of existence (where it has been
>> until now) and ensure that every rrtype's registry of "_" names is
>> public and easily found on the IANA web site.
> I don't think it's a coincidence, but as you noted people will do what
> they do. One registry should make it easier for sensible people to look
> and say aha, _foo already means something for BAR records so I will use
> a different name for unrelated tags for BAZ records. Or for unsensible
> people, we can at least be aware of what they do.

in one sense there is a registry but in another sense there are 
registries for each RR type whose applications will use underscored 
names for extended subtyping.

what this means is, if someone sees _TCP in use for some rr type, and 
they needed something like this for their own new rr type, they should 
be encouraged to either use _TCP if they find it's the best fit, or use 
something else if they find that a best fit. they should not worry 
either away about either reusing, or not reusing, an existing name.

so while i agree that having a set of per-type registries will inform 
future application developers, my expected use case is the opposite of 
what you said here.

it's vital that the relevant technical constraint be restated at every 
level of underscore documentation, and that is, there is no relationship 
other than coincidence between a given _LABEL used by one rr type and 
that same label used by some other rr type. i know that we think of 
names having rrsets, and they do; however, in practical terms of whether 
conflicts will arise, we can in this case think of an rrset having its 
own parent _LABEL.

dave may profit by referring to the "let's all stop returning ANY 
results" draft, since it's only if ANY actually worked, that we would 
see performance problems from _LABEL reuse across types. but note, even 
in that performance-degrading situation, there would be no *conflicts*, 
only coincidences.

P Vixie