Re: [DNSOP] Barry Leiba's Abstain on draft-ietf-dnsop-onion-tld-00: (with COMMENT)

"Patrik Fältström " <paf@frobbit.se> Sat, 22 August 2015 07:09 UTC

Return-Path: <paf@frobbit.se>
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 A7DD31A0146; Sat, 22 Aug 2015 00:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 6pOvlHkCWTxC; Sat, 22 Aug 2015 00:09:28 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EB071A0123; Sat, 22 Aug 2015 00:09:28 -0700 (PDT)
Received: from [192.168.1.12] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id D90F620043; Sat, 22 Aug 2015 09:09:25 +0200 (CEST)
From: Patrik Fältström <paf@frobbit.se>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Sat, 22 Aug 2015 09:09:25 +0200
Message-ID: <0E910391-9F2A-4908-854F-D5A4BBEF70B0@frobbit.se>
In-Reply-To: <55D778CE.4000704@cs.tcd.ie>
References: <20150821183707.22252.20048.idtracker@ietfa.amsl.com> <55D778CE.4000704@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_264498C3-D878-4218-ACE0-8E45725E4C37_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/hzJO_JEWHNQ4Mx372kg95wD9L44>
Cc: tjw.ietf@gmail.com, dnsop-chairs@ietf.org, draft-ietf-dnsop-onion-tld@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-onion-tld.ad@ietf.org, draft-ietf-dnsop-onion-tld.shepherd@ietf.org, The IESG <iesg@ietf.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [DNSOP] Barry Leiba's Abstain on draft-ietf-dnsop-onion-tld-00: (with COMMENT)
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: Sat, 22 Aug 2015 07:09:29 -0000

On 21 Aug 2015, at 21:15, Stephen Farrell wrote:

> Do ICANN have any process for allocating special-use names that will
> not be used in the DNS?

ICANN today do not have any process for doing anything regarding anything in the domain namespace except managing the strings that where applied for in the previous round of ability to get new TLDs.

ICANN has initiated discussions internally on "what must be done before a potential next round of TLDs".

It is not possible to know, of course, what those discussions will lead to.

I.e. you have been able to apply for a TLD that is not only allocated for you in the namespace, you also get it delegated in the DNS in the root that is managed under the contract with NTIA.

You have never been able to request strings for special use that is not created as a TLD.

The policy for the previous round of TLDs included a list of strings that one could not apply for.

On top of that ICANN have made decisions for a few of the strings, where the decisions are:

- Delay delegation indefinitely (sort of, there are many more words)

- Delay delegation as long as the string is viewed as being in the category of high risk strings (according to an evaluation process...etc etc)


To conclude, today you can in practice not go to ICANN and request any string any kind of status except the TLDs allocated or the strings that are part of the current new gTLD round.


<personal view>
My personal view is that the outcome of these discussions in the IETF is very important input to the policy process in ICANN because I think the most important thing is that the processes must together cover the complete namespace used for, among other things, DNS.
</personal view>

   Patrik