Re: [art] draft-ietf-dnsop-attrleaf

Adam Roach <adam@nostrum.com> Thu, 10 August 2017 02:38 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2567D131D1E for <art@ietfa.amsl.com>; Wed, 9 Aug 2017 19:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHVHfyOIAm3U for <art@ietfa.amsl.com>; Wed, 9 Aug 2017 19:38:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964E9131CBF for <art@ietf.org>; Wed, 9 Aug 2017 19:38:10 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7A2c76F055317 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 9 Aug 2017 21:38:08 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: dcrocker@bbiw.net
Cc: art@ietf.org
References: <20170803003526.2349.qmail@ary.lan> <8cbaba50-a7d8-94b1-8cd0-fa8310e0b17d@bbiw.net> <47fcd0be-e4b6-2efc-266a-2eaef6243346@nostrum.com> <04c36ea8-dbf4-1e01-4982-dd07863a18b1@dcrocker.net>
From: Adam Roach <adam@nostrum.com>
Message-ID: <066763ab-1121-0c57-5a66-48349c4cc101@nostrum.com>
Date: Wed, 09 Aug 2017 21:38:02 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <04c36ea8-dbf4-1e01-4982-dd07863a18b1@dcrocker.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tXK6-lOdqA44-rics9Ol5u3kHfg>
Subject: Re: [art] draft-ietf-dnsop-attrleaf
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 02:38:12 -0000

On 8/9/17 8:15 PM, Dave Crocker wrote:
> On 8/9/2017 4:25 PM, Adam Roach wrote:
>> I would recommend documenting and registering the underscore leaf 
>> nodes used by TXT records as a completely separate concern and in a 
>> different IANA table
>
>
> Adam,
>
> (Leaving for later, all other comments about the note, other than to 
> say thanks for reading the draft, thinking about it, and commenting...)
>
> Your above seems to be calling for two registries that assign out of 
> the same namespace.  (Being specified in the same document doesn't 
> matter if there are two tables.)
>
> I'm hoping I've seriously misunderstood, since the entire goal of my 
> simplification proposal is to avoid exactly that.
>
> Please to set me right. 

So, I'll reiterate explicitly what I've only implied to this point: I'm 
not a DNS expert; I've simply dealt with protocols that use DNS, and 
I've managed DNS zones.

What I do know is that I can ask for an RR of type FOO for 
something.example.com and get a response with an answer, and I can ask 
for an RR of type BAR for something.example.com, and get a response with 
no answers. I've internalized this as FOO and BAR being different things 
-- different scopes, effectively -- but (based on your and John Levine's 
and Mark Andrew's responses) clearly have an incorrect mental model of 
what's considered "namespaces," at least as compared to people who deal 
with DNS in more detail.

So ignore the aspect of my proposal that suggested two tables. I think 
the remainder is sound, which probably just resolves to cleaning up the 
table so that it contains only seven entries and removing discussion of 
NAPTR RRs.

/a