Re: [DNSOP] SRV-related _underscore registry (was Re: Call for Adoption: draft-crocker-dns-attrleaf)

Dave Crocker <dhc@dcrocker.net> Tue, 01 March 2016 15:22 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715981B2D04 for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 07:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 VgHRJGviNQZf for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 07:22:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5CA91B2D03 for <dnsop@ietf.org>; Tue, 1 Mar 2016 07:22:49 -0800 (PST)
Received: from [192.168.1.87] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u21FMmh3019145 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <dnsop@ietf.org>; Tue, 1 Mar 2016 07:22:49 -0800
To: dnsop@ietf.org
References: <20160229180756.55888.qmail@ary.lan> <56D4BEB3.3060409@dcrocker.net> <alpine.OSX.2.11.1602291705250.30909@ary.lan> <56D4C70A.2050701@bellis.me.uk>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <56D5B3BC.6050206@dcrocker.net>
Date: Tue, 01 Mar 2016 07:22:36 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D4C70A.2050701@bellis.me.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 01 Mar 2016 07:22:49 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/XgboFQjOnAezFUyAszZmzeYEawk>
Subject: Re: [DNSOP] SRV-related _underscore registry (was Re: Call for Adoption: draft-crocker-dns-attrleaf)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Mar 2016 15:22:53 -0000

On 2/29/2016 2:32 PM, Ray Bellis wrote:
> On 29/02/2016 22:27, John R Levine wrote:
>
>> The existing port and service registry already has all of the _service
>> names, and is updated as people invent new services.  What's the benefit
>> of duplicating it rather than just pointing to it?
>
> +1


So this commentr sequence is tending to convince me to have the document 
stay away from saying anything about SRV's subordinate _underscore name 
field, _Service.

However for _Proto, there remains a basic problem with the current SRV 
arrangement, in the face of an _underscore registry:  name collision.

If SRV continues to specify _Proto choices from a separate IANA 
registry, there there are two, /independent/ places for doing 
_underscore registrations.  That model ensures name collisions.

While I doubt that all 7000 service names, or even a small fraction of 
them, get used for SRV, whatever percentage does get used is likely to 
be a large-ish number.  So, yeah, having to duplicate the registration 
is problematic.

In the case of _Proto names, the set is tiny, so the burden of 
explicitly registering these names in an _underscore registry is not 
onerous, given that it is the only way to ensure that name collisions 
are avoided.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net