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

"John Levine" <johnl@taugh.com> Tue, 01 March 2016 16:57 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 B346D1B2F5F for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 08:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 mb7TBfcJrVdD for <dnsop@ietfa.amsl.com>; Tue, 1 Mar 2016 08:57:50 -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 AA8491B2F44 for <dnsop@ietf.org>; Tue, 1 Mar 2016 08:56:58 -0800 (PST)
Received: (qmail 76334 invoked from network); 1 Mar 2016 16:56:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 1 Mar 2016 16:56:55 -0000
Date: Tue, 01 Mar 2016 16:56:33 -0000
Message-ID: <20160301165633.71260.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <56D5C767.4010603@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/RsCW7n8sttsOho4ukg0rjo8pqQo>
Cc: ray@bellis.me.uk
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:57:50 -0000

>> 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 ?

If you take a look at that registry, it's a stroll down memory lane.
You'll find NVP-II from RFC 741 in 1977, PUP and XNS-IDP from Xerox in
1980, and other great hits from networking history.

I really doubt that people are going to ever publish _pup SRV records
other than perhaps on April 1.

R's,
John