Re: [DNSOP] comments ( was Re: Call for Adoption: draft-crocker-dns-attrleaf)

"John Levine" <johnl@taugh.com> Mon, 29 February 2016 22:47 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 A5A3C1B3E86 for <dnsop@ietfa.amsl.com>; Mon, 29 Feb 2016 14:47:46 -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 fTl1isygY2JX for <dnsop@ietfa.amsl.com>; Mon, 29 Feb 2016 14:47:45 -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 26D111B3E88 for <dnsop@ietf.org>; Mon, 29 Feb 2016 14:47:45 -0800 (PST)
Received: (qmail 40627 invoked from network); 29 Feb 2016 22:47:43 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 29 Feb 2016 22:47:43 -0000
Date: Mon, 29 Feb 2016 22:47:21 -0000
Message-ID: <20160229224721.56560.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <56D4C10C.7070100@dcrocker.net>
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/XrYrxIOVl7vIveLe_QPBz_qM_Ic>
Cc: dcrocker@bbiw.net
Subject: Re: [DNSOP] comments ( 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: Mon, 29 Feb 2016 22:47:46 -0000

>> What are the requirements for entry into this registry. I would not want
>> to see a rush of people registering vanity names for pet projects,
>> taking away all the sensible one word entries. I see _mail is available :)
>
>Well, we know the concern about vanity use of DNS-related names is a 
>long way from silly, so alas I guess we have to worry about that.  grrr...

I'm not too worried about it, since unlike domain names, these are not
ones that are likely to be visible to users, or to be typed into browser
address bars.

>I'm inclined to suggest 'Specification Required'.  In my own view, an 
>internet draft ought to qualify, since they no longer disappear, but I 
>believe the community view is that it would require an RFC or the like.

RFC 6335 says that the ports and services registry is FCFS for entries
that don't ask for a port number, and the registration request is
required to have a reference that either describes it or says it's
proprietary with some minimal interface info, so it's close to
specification required.  That de facto reserves an underscore name,
and we haven't seen an unseemly gold rush.  Given the size of that
registry, I'd want a compelling reason to make the rules different.

R's,
John