Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt

Dave Crocker <dhc@dcrocker.net> Wed, 21 March 2018 18:44 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 6016812778D; Wed, 21 Mar 2018 11:44:13 -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=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 eyw1hVFXEhhY; Wed, 21 Mar 2018 11:44:11 -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 A76D912DA03; Wed, 21 Mar 2018 11:43:40 -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 w2LIj2jR002643 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 11:45:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1521657902; bh=xXbquoysDEKnd1LpSPr+Qesn8VzQLnbjsM2Sfc9iI8I=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=LnO2iRdNI0WVOYXHfMjh61gMibYmERRn+WSUt3Q487CFIkBZEbJav7uuK3n9yiDst COzONG4VmCORW9Yzmyv0iP7E7H8zwTOEkmEfidaRWQsged//DJ0dxyUXZdxG1426sw XzIClBifvVH6VyC8IqWvsf/FrNFMRydkoG3hpWQ0=
To: dnsop@ietf.org, Applications and Real-Time Area Discussion <art@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> <5AB27439.40801@redbarn.org> <72e481c6-b8f7-4c75-d187-b49b5fa9a735@dcrocker.net>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <6d3c77a3-2326-a4b4-1e99-50fe4647d7c8@dcrocker.net>
Date: Wed, 21 Mar 2018 11:43:34 -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: <72e481c6-b8f7-4c75-d187-b49b5fa9a735@dcrocker.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/d_T6jov2wKuSqby-W5j85LxLbAI>
Subject: Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.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: Wed, 21 Mar 2018 18:44:13 -0000

On 3/21/2018 11:17 AM, Dave Crocker wrote:
> Much of the discussion of the current topic -- previously and now -- has 
> tended to stray from the pragmatics, whereas that is the only thinking 
> driving my concerns and suggestions.  In particular, some people seem to 
> have a mystical -- or equally impractical -- view of how name collisions 
> will be avoided between independent registries making assignments out of 
> the same name space.
> 
> I prefer to take as simple an approach as possible: have a single 
> registry control all allocations out of a name space.


It occurs to me that some folk might not have a perfect memory of a 
dnsop working group agreement from Aug, 2017.  So here's a tag into it:

    https://www.ietf.org/mail-archive/web/dnsop/current/msg20708.html

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net