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

Edward Lewis <edward.lewis@icann.org> Sat, 09 May 2015 11:29 UTC

Return-Path: <edward.lewis@icann.org>
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 900481A86F2 for <dnsop@ietfa.amsl.com>; Sat, 9 May 2015 04:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 lh4vY_9fDWsH for <dnsop@ietfa.amsl.com>; Sat, 9 May 2015 04:29:33 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE6651A86F1 for <dnsop@ietf.org>; Sat, 9 May 2015 04:29:33 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Sat, 9 May 2015 04:29:31 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Sat, 9 May 2015 04:29:31 -0700
From: Edward Lewis <edward.lewis@icann.org>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
Thread-Index: AQHQiM2EQzpJgAEHlEW+E40c5ALkTZ1xHF2AgAL/twA=
Date: Sat, 09 May 2015 11:29:30 +0000
Message-ID: <D173BA09.B755%edward.lewis@icann.org>
References: <D170E3E4.1011F2%jason_livingood@cable.comcast.com> <20150507154141.53015.qmail@ary.lan>
In-Reply-To: <20150507154141.53015.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.9.150325
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.237]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3514022966_45826276"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/3uYpzVP2HyY-wi1xy5G0DQFBQXs>
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: Sat, 09 May 2015 11:29:37 -0000

On 5/7/15, 11:41, "John Levine" <johnl@taugh.com> wrote:

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

My thought (as I wasn't in ICANN when the 2012 new TLD program was
established, etc.) is that the process in place was built to allow the
establishment of operating TLDs with all of "those" concerns.  As opposed
to being a process by which to reserve "strings" (labels) that would not
"be in" (delegated/have whois servers/registration interfaces/etc) the
root zone, i.e., for the purpose of squatting to prevent collisions.

The problem (the topic of discussion here) I see is that there are class
of strings that are intended to not be active in the DNS and further more,
the DNS isn't even meant to be consulted.  The closest process in place
today to achieving this is the Special Use Names registry - and I
emphasize "closest" recognizing that if it was "perfect" we wouldn't be
having an interim meeting in a few days time.

I may be wrong...but this is how I see view the topic.  (I.e., not a
statement on behalf of ICANN.)