Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

<jonne.soininen@broadcom.com> Mon, 03 February 2014 21:54 UTC

Return-Path: <jonne.soininen@broadcom.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 E5BC81A019F for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 13:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001] 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 sXQijdmDapk3 for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 13:54:44 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.116]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6941A015D for <dnsop@ietf.org>; Mon, 3 Feb 2014 13:54:44 -0800 (PST)
Received: from [193.109.254.147:61850] by server-12.bemta-14.messagelabs.com id 50/1F-17220-32010F25; Mon, 03 Feb 2014 21:54:43 +0000
X-Env-Sender: jonne.soininen@broadcom.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1391464482!1741932!1
X-Originating-IP: [213.174.82.10]
X-StarScan-Received:
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3505 invoked from network); 3 Feb 2014 21:54:42 -0000
Received: from renexfe01.roe2.renesasmobile.com (HELO renexfe01.roe2.renesasmobile.com) (213.174.82.10) by server-16.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 3 Feb 2014 21:54:42 -0000
Received: from RENEXMB01.roe2.renesasmobile.com ([fe80::e58a:2b9f:54fe:ff5]) by renexfe01.roe2.renesasmobile.com ([fe80::ec94:bbb3:68e:a94a%18]) with mapi id 14.03.0174.001; Mon, 3 Feb 2014 23:54:42 +0200
From: <jonne.soininen@broadcom.com>
To: <marka@isc.org>, <jabley@hopcount.ca>
Thread-Topic: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
Thread-Index: AQHPISqKpqmZs4RLaEKxwrcTU52+xA==
Date: Mon, 3 Feb 2014 21:54:41 +0000
Message-ID: <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org>
In-Reply-To: <20140203212333.1259EE44493@rock.dv.isc.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.22.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C3D25FD9E31F5046B72324E72493AAAF@renesasmobile.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 03 Feb 2014 14:34:31 -0800
Cc: dnsop@ietf.org, paul.hoffman@vpnc.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
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: Mon, 03 Feb 2014 21:54:47 -0000

Hi everybody,

(just for full closure - I'm the IETF technical liaison to the ICANN
board, but taking that hat off here)


On 2/3/14 11:23 PM, "Mark Andrews" <marka@isc.org>; wrote:

>
>In message <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>;, Joe Abley
>writes:
>>
>> On 2014-02-03, at 11:15, Paul Hoffman <paul.hoffman@vpnc.org>; wrote:
>>
>> > On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>;
>> wrote:
>> >
>> >> "squatted" is not a bad word here. In the physical world, squatters
>> >> are often people who do not have the money to rent a home, because
>> >> some rich people put the price of the housing too high. Here, you
>>will
>> >> have trouble convincing the users of Tor or Namecoin that it is right
>> >> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
>> >> have to stay in the slums.
>> >>
>> >> [End of political rant, sorry]
>> >
>> > Your political rant is, however, off-base. Assume for the moment that
>> > the Tor folks had registered oniontld.fr for a relatively small
>>amount of
>> > money. It could have all of the attributes of .onion: you could
>>hard-wire
>> > it into local resolvers, some requests for it would leak to the DNS
>>and
>> > therefore possibly be trackable, and so on. For the purposes given in
>> > draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs would work
>> > just as well as squatted TLDs.
>>
>> I made that point somewhat earlier (but my example was onion.eff.org or
>> something).
>>
>> The reasonable response to my instance of that observation was that
>> there's a significant deployed base of users already making use of
>>.onion
>> [1], and we don't have a time machine that we're aware of [2] to allow
>> that to be fixed.
>>
>> Despite the enduring (and endearing, perhaps) optimism that the new gTLD
>> programme would eventually bear fruit, I don't think it's unreasonable
>>to
>> think that in 2002 [3] a new gTLD wasn't really a practical option to
>> choose not to take.
>>
>> So squatting doesn't sound right to me.
>
>They choose to use a TLD.  There were plenty of people saying "Do
>NOT use a TLD for your private namespace, use a namespace you own"
>in 2002 whether it was for a protocol or a internal network.
>
>For $20 a year or less they could have registered a name in just
>about any TLD and avoided the issue.

I think we have to distinguish here between the "new squatters" and the
"old squatters" and the reasons for "squatting". For instance in corp and
home, the installed base seems to be quite large. It comes from equipment
and hardware that might not be easily replaceable and not really under a
single organization's control. You cannot change that and ignoring it
might cause harm for the Internet.

The new technologies (gnu/onion/...) seem to be different. First of all,
they don't use DNS but something else. Therefore, there should be no
collisions. It seems more that delegating them to the DNS would harm those
technologies rather than DNS or Internet getting harmed. The only
relationship to the DNS seems to be that they happen to have a structure
that is similar to the FQDN.

Anyways, I have been following this discussion now for a while. It seems
to me that the discussion is not really converging. I would blame it at
least partly on RFC6761. Though, RFC6761 isn't that old, it was written in
a time before the new gTLD round was ongoing.

Rather than discussing the individual strings, maybe we should consider to
discuss the principles under which TLDs can be reserved for special use
and consider a re-spin or an update to RFC6761.

Cheers,

Jonne.

>
>> Joe
>> 
>> [1] https://metrics.torproject.org
>> [2] =
>> 
>>http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawking-time-travel_n_
>>1=
>> 643488.html
>> [3] http://en.wikipedia.org/wiki/Tor_(anonymity_network)#History
>-- 
>Mark Andrews, ISC
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop