IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Tue, 17 November 2015 02:06 UTC

Return-Path: <johnl@taugh.com>
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 B70DF1B3277 for <dnsop@ietfa.amsl.com>; Mon, 16 Nov 2015 18:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.667
X-Spam-Level: **
X-Spam-Status: No, score=2.667 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, KHOP_DYNAMIC=1.004, SPF_PASS=-0.001] autolearn=no
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 B3d8NI-mIqxx for <dnsop@ietfa.amsl.com>; Mon, 16 Nov 2015 18:06:10 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921421B3275 for <dnsop@ietf.org>; Mon, 16 Nov 2015 18:06:10 -0800 (PST)
Received: (qmail 8923 invoked from network); 17 Nov 2015 02:06:09 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 17 Nov 2015 02:06:09 -0000
Date: Tue, 17 Nov 2015 02:05:47 -0000
Message-ID: <20151117020547.19542.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <5649965A.1000106@bellis.me.uk>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/R23cztoHn3VbMGoc1skVnlYLSnM>
Cc: ray@bellis.me.uk
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: Tue, 17 Nov 2015 02:06:12 -0000

>>From my previous recollection of this, ISTR there was a suggestion that
>your draft only directly register "single-label" names, but with "_tcp",
>"_udp" et al listed in the registry as a link to RFC 6335?

It seems to me that this needs three columns, like this:

Name	Reference	Type
_tcp	RFC2782		Proto
_udp	RFC2782		Proto
_domainkey	RFC6376	App
_vouch	RFC5516	App

There's a short list of types.  Proto is a protocol that can have any
of the RFC6335 service names as a subnode on SRV or NAPTR records.
App is an application that names TXT records and generally has no
prefixed subnodes, or if it does it's just a handful that are
mentioned in a footnote.  There may be other types, but probably
not many.

R's,
John

v2.23.0 | Report a Bug | By Email