Re: [art] draft-ietf-dnsop-attrleaf
Dave Crocker <dcrocker@bbiw.net> Thu, 10 August 2017 02:50 UTC
Return-Path: <dcrocker@bbiw.net>
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 98B1E132395 for <art@ietfa.amsl.com>; Wed, 9 Aug 2017 19:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbiw.net
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 uOxyBe2p1iky for <art@ietfa.amsl.com>; Wed, 9 Aug 2017 19:50:04 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F1C0127735 for <art@ietf.org>; Wed, 9 Aug 2017 19:50:04 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v7A2oXMk009914 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 9 Aug 2017 19:50:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1502333434; bh=lOlw6gyC3l+mE4k4xOvAdonXQaJALRgi75fmii402d8=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=cGbpoDARdyzINMWF0cDc9LHQ3yQncGlIQiQeF4Ke1maxhe+b/ANmb3blM8NRFe93V 3HHwfPzT6rbnuXIRHzt3bMlMgWLPkPAfjjTC1UHcaOHaBjFesKGPQg3dAxQBHRX9TJ AGFtqRVXNYhKoWVuAocgbrF3OWvefVwl3ChA4w70=
To: Adam Roach <adam@nostrum.com>
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> <066763ab-1121-0c57-5a66-48349c4cc101@nostrum.com>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <6b5f8522-4390-9cc5-a246-bd13cdf96296@bbiw.net>
Date: Wed, 09 Aug 2017 19:49:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <066763ab-1121-0c57-5a66-48349c4cc101@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/T4DbIpeyTafs4KWx0Vji3e8Aw9I>
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:50:06 -0000
On 8/9/2017 7:38 PM, Adam Roach wrote: > 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. Ahh, interesting. This might point to a need for some additional explanatory (and maybe even denotational) text in the draft. (I work from the theory that confusion in one serious reader is likely an indicator that others will suffer the same fate.) So: Scope is meant as a static property, not one dependent on the nature of the query. It is an artifact of the DNS name. Hence, some.example.com defines the scope, independent of any RR under it. And in case it's relevant to add this: The namespace of the proposed registry covers all node names that begin with an underscore and are the 'highest' occurrence of an underscore name. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [art] draft-ietf-dnsop-attrleaf tjw ietf
- Re: [art] draft-ietf-dnsop-attrleaf John Levine
- Re: [art] draft-ietf-dnsop-attrleaf Cullen Jennings
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf John C Klensin
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf John Levine
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf John R Levine
- Re: [art] draft-ietf-dnsop-attrleaf Mark Andrews
- Re: [art] draft-ietf-dnsop-attrleaf John R Levine
- Re: [art] draft-ietf-dnsop-attrleaf Dave Crocker
- Re: [art] draft-ietf-dnsop-attrleaf John Levine
- Re: [art] draft-ietf-dnsop-attrleaf Dave Crocker
- Re: [art] draft-ietf-dnsop-attrleaf John R Levine
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf John R Levine
- Re: [art] draft-ietf-dnsop-attrleaf Mark Andrews
- Re: [art] draft-ietf-dnsop-attrleaf John R Levine
- Re: [art] draft-ietf-dnsop-attrleaf Dave Crocker
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf Dave Crocker
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf Adam Roach
- Re: [art] draft-ietf-dnsop-attrleaf Mark Andrews
- Re: [art] draft-ietf-dnsop-attrleaf Tim Wicinski