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

Ted Lemon <Ted.Lemon@nominum.com> Thu, 07 May 2015 14:41 UTC

Return-Path: <Ted.Lemon@nominum.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 996EC1A90BF for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 07:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 1x83wIviluEi for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 07:41:45 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F4051A90C7 for <dnsop@ietf.org>; Thu, 7 May 2015 07:41:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 0D1CBDA0085; Thu, 7 May 2015 14:41:40 +0000 (UTC)
Received: from [10.0.20.206] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 7 May 2015 07:41:40 -0700
References: <D5D3A5AC-41B5-4872-B973-2752275D651E@gmail.com> <D170E3E4.1011F2%jason_livingood@cable.comcast.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <D170E3E4.1011F2%jason_livingood@cable.comcast.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <731F710D-DA6D-4745-BBB9-207B23652018@nominum.com>
X-Mailer: iPad Mail (12F69)
From: Ted Lemon <Ted.Lemon@nominum.com>
Date: Thu, 07 May 2015 10:41:38 -0400
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/Iz0-OwWc9vfril5bUufgXQvsSR0>
Cc: Suzanne Woolf <suzworldwide@gmail.com>, "dnsop@ietf.org" <dnsop@ietf.org>
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 14:41:46 -0000

On May 7, 2015, at 9:56 AM, Livingood, Jason <Jason_Livingood@cable.comcast.com> wrote:
> 
> 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. So from one perspective, would more people just deploy into an unused namespace and then later lay claim the the namespace retroactively based on their use (gTLD-squatting)? This could be quite messy at scale, and I am not sure the IETF has a process to deal with and consider competing uses. 

I think this is an unfortunate way to look at the issue.   We have a clear process for allocating special-use domain names.   If TOR had come to us and asked for one, would you argue that they should pay ICANN $180k to get it?   Where would that money come from?   They don't need a delegation.   They just need for the name to be registered as a special-use name.   This is not at all the same situation as someone coming to us asking to get a _delegation_ for a TLD based on the special-use domain name process.   Special-use doesn't apply in that case, and we would reject it.   So your argument amounts to a straw man.

I think part of the reaction to this proposal at the moment is that the process _wasn't_ followed.   And so we are rightly concerned that future candidates for special-use names will also not follow the process, leading us to have to revisit this conversation.   However, that is actually exactly wrong.

In reality, the more pushback we give for a reasonable and legitimate request for a special-use domain now, the more likely it is that when someone needs one in the future, they will give up before they try, as the ToR people did.   What we should be doing is judging those requests that seem legitimate and responding expeditiously, not creating a huge process black hole into which such requests will be swallowed.