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

Ray Bellis <ray@bellis.me.uk> Tue, 01 March 2016 16:46 UTC

Return-Path: <ray@bellis.me.uk>
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 6F53B1B2F32 for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 08:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 VOLI_yC-3ya5 for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 08:46:33 -0800 (PST)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9161F1B2F36 for <dnsop@ietf.org>; Tue, 1 Mar 2016 08:46:33 -0800 (PST)
Received: from [46.227.151.81] (port=53047 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1aanRN-000679-M5 (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Tue, 01 Mar 2016 16:46:29 +0000
To: dnsop@ietf.org
References: <20160301163905.71179.qmail@ary.lan>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <56D5C767.4010603@bellis.me.uk>
Date: Tue, 01 Mar 2016 16:46:31 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160301163905.71179.qmail@ary.lan>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/eRPOrfv5JyMdSjh2PgnZoaojuts>
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
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 16:46:35 -0000


On 01/03/2016 16:39, John Levine wrote:

> The other which I prefer is simply to put the four _proto tags into
> the new underscore registry.  Add a note that they have subnames from
> the RFC 6335 services registry, and for anew new protocol tags try to to
> keep the protocol names consistent with the keywords in the protocol
> number registry.

This, exactly.

I'd suggest that perhaps the keywords from the protocol registry (or a
canonical representation thereof, for those that don't match LDH) should
actually be reserved ?

> I see the universe of underscore tags falling into three categories.
> 
> 1.  Tags that mean something under a hostname.  This includes the
> _proto tags and things like _domainkey and _vouch.
> 
> 2.  Tags that only mean something under a _proto tag.  This is 
> the set of service names in the RFC 6335 registry and _nnn (port number)
> used to name TLSA records.
> 
> 3.  Tags that only mean something under some other underscore tag.
> This is a very small list, _adsp._domainkey and _report._dmarc are
> the only ones I know.
> 
> It would be useful to define the registry for the first kind of tags.
> The second already has a registry, the third is uninteresting since it
> has no collision issues.

All that, too.

Ray