Re: [DNSOP] [apps-discuss] Draft of interest in DNSOP: draft-ietf-dnsop-attrleaf

Dave Crocker <dhc@dcrocker.net> Mon, 29 August 2016 01:58 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 77EF312D0E1 for <dnsop@ietfa.amsl.com>; Sun, 28 Aug 2016 18:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.209
X-Spam-Level:
X-Spam-Status: No, score=-1.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 MalqrjaKqHH3 for <dnsop@ietfa.amsl.com>; Sun, 28 Aug 2016 18:58:58 -0700 (PDT)
Received: from simon.songbird.com (unknown [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 C54BD12D10B for <dnsop@ietf.org>; Sun, 28 Aug 2016 18:58:58 -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 u7T1xBXm018479 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2016 18:59:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1472435951; bh=KOOj7mdJUHEKKGGA2W9LArokOfNie7N8lQ/F1hXBfoQ=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=K5bfTP379cSEzC3ArkwvTxlek0/IRk5Jeu0ajr0EpX8PCrhnH5aEnyq2WTauqm+pQ ysvcNNo91t7j+OTRll0YQOn2398Myhk5IBqb1S0fptPH34jmXWdWi71sv4dRf2vNd7 X4t4b2jgPWhuLbDrUMBTPzoM9QdMTu9ytFvtEvsw=
To: John Levine <johnl@taugh.com>, dnsop@ietf.org
References: <20160829014200.4338.qmail@ary.lan>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <9030a78a-7bb9-38a0-6477-8456c23c7161@dcrocker.net>
Date: Sun, 28 Aug 2016 18:58:30 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160829014200.4338.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uDAYjxhXkMTNG0C5MgB0kypkDuY>
Subject: Re: [DNSOP] [apps-discuss] Draft of interest in DNSOP: draft-ietf-dnsop-attrleaf
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 29 Aug 2016 01:58:59 -0000

On 8/28/2016 6:42 PM, John Levine wrote:
>> atrik's and John 's postings notwithstanding, I'm still concerned about
>> >the proposed way of handling this, namely to rely on IANA to do a manual
>> >check of the two registries the URI RR might call on.  First, it does
>> >not seem reasonable to me to impose that burden on the IANA staff and
>> >second a manual process like that is almost certain to produce errors.
> Well, either you can persuade Patrik and Olaf to revise RFC 7553 to
> add a _enumservice psedudo-transport to disambiguate, or you can't.
> When I look at the enumservice registry, I see that it's not very big
> and doesn't change very often.
>
> Rather than speculating about how hard this would be for IANA, why
> don't you ask them.  Do they have any other groups of registries that
> they have to monitor for name collisions?  How much harder is that
> than the checking they have to do in a large registry like ports and
> services to be sure they don't reuse a name?


Asking will give us a measure of 'willingness', not a measure of 
'long-term perfection'.  This difference is fundamental.  I'm worried 
about the latter, while I consider the former to be a distraction.

Simply put, specifying a smal task that requires humans to perform 
perfectly at random, very (very) infrequent times, is a plan designed to 
fail.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net