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

"Darcy Kevin (FCA)" <kevin.darcy@fcagroup.com> Fri, 13 November 2015 18:53 UTC

Return-Path: <kevin.darcy@fcagroup.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 A3CE41B2F2B for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 10:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 mox6KkiXDkZy for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 10:53:31 -0800 (PST)
Received: from odbmap07.extra.chrysler.com (odbmap07.out.extra.chrysler.com [129.9.107.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 456BC1B2C3D for <dnsop@ietf.org>; Fri, 13 Nov 2015 10:53:31 -0800 (PST)
Received: from shbmap09.shdc.chrysler.com (Unknown_Domain [151.171.73.109]) by odbmap07.extra.chrysler.com (Symantec Messaging Gateway) with SMTP id F4.2F.06707.9A136465; Fri, 13 Nov 2015 13:53:30 -0500 (EST)
X-AuditID: 81096b23-f79046d000001a33-dd-564631a95d53
Received: from MXPA1CHRW.fgremc.it (Unknown_Domain [151.171.20.17]) by shbmap09.shdc.chrysler.com (Symantec Messaging Gateway) with SMTP id 26.79.17818.9A136465; Fri, 13 Nov 2015 13:53:29 -0500 (EST)
Received: from mxph4chrw.fgremc.it (151.171.20.48) by MXPA1CHRW.fgremc.it (151.171.20.17) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Fri, 13 Nov 2015 13:53:29 -0500
Received: from mxph4chrw.fgremc.it (151.171.20.48) by mxph4chrw.fgremc.it (151.171.20.48) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Fri, 13 Nov 2015 13:53:29 -0500
Received: from mxph4chrw.fgremc.it ([fe80::cc0c:cb4f:1b3f:2701]) by mxph4chrw.fgremc.it ([fe80::cc0c:cb4f:1b3f:2701%18]) with mapi id 15.00.1076.000; Fri, 13 Nov 2015 13:53:29 -0500
From: "Darcy Kevin (FCA)" <kevin.darcy@fcagroup.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] Registry of non-service _prefix names?
Thread-Index: AQHRHj1FrG0EtIoocU2MJdhtZTWrF56aRvDQ
Date: Fri, 13 Nov 2015 18:53:28 +0000
Message-ID: <bca2bdd2396f42f19426bce69665c3cc@mxph4chrw.fgremc.it>
References: <20151113180033.4668.qmail@ary.lan>
In-Reply-To: <20151113180033.4668.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [151.171.20.202]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCIsWRmVeSWpSXmKPExsUyfbVnru4qQ7cwg75tjBZ331xmcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxq3Nn1gLnohWrLv4jrWB8ZVgFyMnh4SAicSUrWdZIWwxiQv3 1rN1MXJxCAlcYpRof7CIEabo2v43rBCJk4wSh3b/Y4dw1jFKzDu8EME58P4bVNlORokph4+z g/SzAfUvvHKXGcQWEVCVuPDvO1MXIweHsIC1xImlqhBhG4mTy8+wQthGErvn3QcrZwEq//Tl OlicV8BJYunF92C2kIC+xMO701lAbE4BA4kL07rAbEagH76fWsMEYjMLiEvcejKfCeIFAYkl e84zQ9iiEi8f/4P62UBi69J9LBC2kkTHzWVsEL06Egt2f4KytSWWLXzNDHGDoMTJmU9YIG5Q lehf+5Idovceu8S8LzETGGVmIVk9C8moWUhGzUIyagEjyypG6fyUpNzEAgNzvdSKkqJEveSM osrinNQiveT83E2MwGhu5MxW3sE4Za7lIUYBDkYlHl4FBbcwIdbEsuLK3EOM0hwsSuK8Mnyu YUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYef+/tV4mfF3a8ULU0nh/7f+LmxM5J9z/9qRu bhjb8nb/EM82ZrusXdVvrDIvGxp+F1zL+jn3yGM5DZ+q2Wkv3PcWqLHqb7dUSxVZwVzqYeMu 8ozZbZFuQcwDy3Z/tT32VkcelFVOjj5+egqXdP8Mucsc8bFpy9mbs4+I5D0+r7A2InxLcpwS S3FGoqEWc1FxIgBlw9jfxwIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCKsWRmVeSWpSXmKPExsUyfbWIoO5KQ7cwgz1zLCzuvrnM4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujFubP7EWPBGtWHfxHWsD4yvBLkZODgkBE4lr+9+wQthiEhfu rWfrYuTiEBI4yShxaPc/dghnHaPEvMMLEZwD77+xQjg7GSWmHD7ODtLPBjRr4ZW7zCC2iICq xIV/35m6GDk4hAWsJU4sVYUI20icXH6GFcI2ktg97z5YOQtQ+acv18HivAJOEksvvgezhQT0 JR7enc4CYnMKGEhcmNYFZjMCnfr91BomEJtZQFzi1pP5TBAvCEgs2XOeGcIWlXj5+B/UawYS W5fuY4GwlSQ6bi5jg+jVkViw+xOUrS2xbOFrZogbBCVOznzCAnGDqkT/2pfsExglZyFZNwtJ +ywk7bOQtC9gZFnFKFWckZSbWGBgqVeckZKsl5xRVFmck1qkl5yfu4kRHIGeOTsY/y+0PMQo wMGoxMP7S8UtTIg1say4MvcQoyQHk5Ior7s2UIgvKT+lMiOxOCO+qDQntfgQowQHs5IIr6oE UI43JbGyKrUoHyYlzcGiJM6rUuAQKCSQnliSmp2aWpBaBJOV4eBQkuDlMABqFCxKTU+tSMvM KUFIM3FwggznARr+XB9keHFBYm5xZjpE/hWjONCZwryaIO08wKSIJCMBdK0Ir8AkV5CmkkSE lFQDo3RH5h/hIE3e5U4916aVH2QVtrhZd/xzjZmZmGF9Vv/97buNff33H1RfO3+b4uMd++I+ b1P6UJzQ2eFiLKXdduy2yN68qLQq/8Mb8h5O6lxbnrkl4mqu+lUrMYln5zwF3nRrVLftyGu6 s7/rcjVPvMWZ6V/VP3puPMmmtOBscNDndwUHpl6pUWIpzkg01GIuKk4EAFT7Fs5HAwAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/ixvRNbIoqzrlCNTfQodG6YyXGZA>
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: Fri, 13 Nov 2015 18:53:32 -0000

Seems there's some hair-splitting here over the definition of the word "service".

While RFC 6335 assumes, more than it defines, what a "service" encompasses, it offers the following "functional" definition of the kind of things which need and use "service name"s:

Service names are the unique key in the Service Name and Transport
   Protocol Port Number registry.  This unique symbolic name for a
   service may also be used for other purposes, such as in DNS SRV
   records [RFC2782].  Within the registry, this unique key ensures that
   different services can be unambiguously distinguished, thus
   preventing name collisions and avoiding confusion about who is the
   Assignee for a particular entry.

Seems like "PGP and S/MIME key publication" would fall under this definition of things-which-need-and-use-service-names, so why not just go ahead and register the names through http://www.iana.org/form/ports-services? Don't be intimidated by all of the references on the application form, to port numbers, since RFC 6335 makes it quite clear that the registry supports "port-less" service names ("Application designers also have the option of requesting only an assigned service name without a corresponding fixed port number if their application does not require one", "This document defines rules for assignment of service names without associated port numbers, for such usages as DNS SRV records [RFC2782], which was not possible under the previous IANA procedures"). If one scrolls to the bottom of http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml about 800 "port-less" entries will be found.

									- Kevin

-----Original Message-----
From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of John Levine
Sent: Friday, November 13, 2015 1:01 PM
To: dnsop@ietf.org
Subject: [DNSOP] Registry of non-service _prefix names?

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?

R's,
John


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop