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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 04 February 2014 08:41 UTC

Return-Path: <bortzmeyer@nic.fr>
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 B584F1A03A4 for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] 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 2vZuOsMK1Lju for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:41:16 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 79ECD1A039E for <dnsop@ietf.org>; Tue, 4 Feb 2014 00:41:16 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9CD0B28052C; Tue, 4 Feb 2014 09:41:15 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 973AA280526; Tue, 4 Feb 2014 09:41:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 94BD6960002; Tue, 4 Feb 2014 09:40:45 +0100 (CET)
Date: Tue, 4 Feb 2014 09:40:45 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <marka@isc.org>
Message-ID: <20140204084045.GA17756@nic.fr>
References: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20140203212333.1259EE44493@rock.dv.isc.org>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Paul Hoffman <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: Tue, 04 Feb 2014 08:41:18 -0000

On Tue, Feb 04, 2014 at 08:23:33AM +1100,
 Mark Andrews <marka@isc.org>; wrote 
 a message of 62 lines which said:

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

Hmmm, the experience of many developers is that, no, it is not easy to
get advice from the IETF. Some did not even bother but those who did
were often turned down immediately. 

Let's play an experiment. In 2014, Joe Developer has a bright idea of
using cryptographic keys as domain names (yes, I know, there is
already the zkeys of GNUnet), he is going to write code to implement
it and wants a suffix for that, to be sure his domain names won't
collide with the ICANN root. Knowing nothing about Internet
governance, not having 185 000 US $ and a zillion lawyers at his
disposal to request a TLD, not being Apple, with the ability to squatt
a TLD and deploy it massively, he sends an email to dnsop or
namedroppers asking about advice. What happens?

1) (Most likely) He gets no reply at all because nobody knows him and
he never appeared in an IETF meeting

2) He gets a few messages saying "that's a bad idea, don't do that,
for reasons explained in [insert a long list of RFC]"

3) He gets a ton of messages saying it is a stupid idea and he is
endangering the security and stability of the Internet

4) He gets a sensible advice, based on a careful study of his
proposal, and given by people who forgives him for making a few
mistakes such as not being able to know what is the difference between
IETF and ICANN

In the first three cases, what will he do? He will follow the usual
Internet/free software method, implement and distribute and we'll see
what happens. And then it will be too late to change what's in his
code.