Re: [DNSOP] Registry of non-service _prefix names?

Ray Bellis <ray@bellis.me.uk> Sat, 14 November 2015 06:58 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 953981B409B for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 22:58:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 GmVpo3augP73 for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 22:58:27 -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 A17BF1B4098 for <dnsop@ietf.org>; Fri, 13 Nov 2015 22:58:26 -0800 (PST)
Received: from [46.227.151.81] (port=59587 helo=Barbaras-MacBook-Pro.local) by hydrogen.portfast.net ([188.246.200.2]:587) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ZxUn3-0007w7-6f (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Sat, 14 Nov 2015 06:58:25 +0000
To: dnsop@ietf.org
References: <20151113180033.4668.qmail@ary.lan>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <5646DB90.30804@bellis.me.uk>
Date: Sat, 14 Nov 2015 06:58:24 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151113180033.4668.qmail@ary.lan>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/iGA-lO_p9286T8yT5uSLtAfGac8>
Subject: Re: [DNSOP] Registry of non-service _prefix names?
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: Sat, 14 Nov 2015 06:58:29 -0000


On 13/11/2015 18:00, John Levine wrote:
> Over in the dbound working group we have some proposals that would use yet another
> underscore prefixed name to avoid name collisions.  (It's not a substitute for a
> new RRTYPE; they need the prefix whether the data is TXT or a new type.)  In
> the mail world we have _domainkey and _dmarc and likely others.  DANE is
> proposing prefixes for publishing PGP and S/MIME keys.
>
> The services registry from RFC 6335 includes all the names for services, but
> not the prefixes for things that aren't services.  How hard would it be either
> to update 6335 to provide for non-service names, or a new non-service registry
> with the understanding that it shares the 6335 FCFS namespace?

Dave Crocker previously did some work on an I-D for a (portless) service 
type registry - I recall he and I discussed it back at the Orlando IETF.

It would be good to see that resurrected.

Ray