Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

"John Levine" <johnl@taugh.com> Thu, 07 May 2015 15:42 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 616771ACC81 for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 08:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.664
X-Spam-Level: *
X-Spam-Status: No, score=1.664 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, LOTS_OF_MONEY=0.001, 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 bhSVtcDDEopE for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 08:42:06 -0700 (PDT)
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 63C811A8941 for <dnsop@ietf.org>; Thu, 7 May 2015 08:42:05 -0700 (PDT)
Received: (qmail 55562 invoked from network); 7 May 2015 15:42:07 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 May 2015 15:42:07 -0000
Date: Thu, 07 May 2015 15:41:41 -0000
Message-ID: <20150507154141.53015.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <D170E3E4.1011F2%jason_livingood@cable.comcast.com>
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/pt1H5eqqwOXKxDrG2G9Fm0YdwdU>
Cc: Jason_Livingood@cable.comcast.com
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
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: <http://www.ietf.org/mail-archive/web/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: Thu, 07 May 2015 15:42:07 -0000

>Beyond that, does it end up being a cheap way to avoid the ICANN
process of creating a new gTLD. For example, I am not aware that
>anything prevents the ToR project from applying to ICANN for the
>.onion gTLD.

ICANN has a whole bunch of rules that mandate that once you've paid
the $185,000, you have to deploy a DNSSEC signed zone on multiple
servers, implement elaborate reservation and trademark claiming rules,
takedown processes, WHOIS servers, and so forth.  In the recent TLD
application round there was one applicant that only wanted to reserve
the domain (they were apparently concerned that someone else would
squat on .CONNECTORS) but they dropped out early so it's unclear what
would have happened if they tried to move ahead.  I was on one of the
technical evaluation panels and I believe we failed them due to their
lack of any plan to comply with the rules.

THe only special purpose TLD that resolves globally is .ARPA, and
everyone agrees what it does.  The rest of them by design don't
resolve globally.  Some resolve locally (.local), some not at all
(.test .example .invalid.)

In this case, .onion falls on the IETF side of the line since it's
definitely not supposed to resolve globally.

R's,
John