[DNSOP] namespace and substring reservations (was Re: Another look - draft-ietf-dnsop-attrleaf-05.txt)

Dave Crocker <dhc@dcrocker.net> Mon, 26 March 2018 21:47 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBA4128D2E; Mon, 26 Mar 2018 14:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 1T1fSDZxU2OW; Mon, 26 Mar 2018 14:47:08 -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 2661512D88A; Mon, 26 Mar 2018 14:47:08 -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 w2QLmWrb002276 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 26 Mar 2018 14:48:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1522100912; bh=0tk1N/LJDU1kyxNHH4VXgzjH8JsvNXfdymQoMC3hgHY=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=py7G0bTrKYNj2FY7uQEtTWf7m0eubhF1Cu1zwNKLWHkTiEVbh5RLDVht/WjWHBshU J4t5vA4b41KC8o6cT8Vnu62kGSWo+r5se5dczjVZJlBb6z+O3oh9Rw7VUVi6PorjhJ K6x4Tv+Acnvl4FEQRwcEDAdL66F1AW+UID+dZ5mU=
To: Paul Vixie <paul@redbarn.org>, John C Klensin <john-ietf@jck.com>
Cc: art@ietf.org, dnsop@ietf.org
References: <f7b85bac-b050-5003-2df0-a48b1ef2f929@dcrocker.net> <e1f41670-ada8-eaac-468c-c712b338a10b@dcrocker.net> <alpine.OSX.2.21.1803201804440.8940@dhcp-8344.meeting.ietf.org> <A7711F58-5145-49E8-9158-B2F94D0EABBF@redbarn.org> <7c168dc1-2ea7-d47e-78b7-0380e5d0aa84@dcrocker.net> <alpine.OSX.2.21.1803211104210.9553@ary.local> <5244d327-f8ea-1590-c663-1d92e0b194c4@dcrocker.net> <5F44FA5B42805C52479DE491@PSB> <alpine.OSX.2.21.1803211507380.9666@dhcp-935d.meeting.ietf.org> <1DF1564CC2B88726B2B54CF4@PSB> <5AB89C4C.7090300@redbarn.org>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <5c62b1db-3f62-2d7e-01a5-04bae451b0f5@dcrocker.net>
Date: Mon, 26 Mar 2018 14:47:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5AB89C4C.7090300@redbarn.org>
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/dnsop/kXGvP1Bh0ThxSJ2Yb0D4dr4TjZM>
Subject: [DNSOP] namespace and substring reservations (was Re: Another look - draft-ietf-dnsop-attrleaf-05.txt)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 21:47:16 -0000

On 3/26/2018 12:07 AM, Paul Vixie wrote:
> 
> 
> John C Klensin wrote:
>>    it is not clear to me that
>> the set of labels starting with "_" constitute a namespace, any more
>> than the set of labels starting with "xn--" do. It is just a naming
>> convention that identifies the labels as keywords with defined
>> meaning.


1. This seems to require a very precise definition of the term 
namespace, but doesn't cite it.  Here's mine -- although it's different 
from Wikipedia's:

    An integrated (probably contiguous) range of values from which names 
can be chosen.

And elaborated:

      A set of rules for assigning names out of a common space of values.


2. If "_" at the beginning of a DNS label does not define a namespace in 
the current DNS, then it can't be subject to any distinct set of rules. 
In actual practice, the use of "_" as the first character is now fully 
entrenched.  Debating what to call the space it controls doesn't change 
established practice.


3. I don't understand how xn-- can be any less reserved for exclusive 
use. That is, I believe the convention of using xn-- has reserved that 
string for only that use and that the document choosing that string has 
formally made that restriction.


The goal of the current draft is to bring the space of names starting 
with underscore under unified control.  With the publication of a draft 
like this, the use of underscore as the first character makes its use 
reserved.

All of this has to do with name /assignment/, but makes no changes on 
name /resolution/.  Name resolution remains blissfully unaware of any 
rules about name assignment or 'meaning'.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net