IETF Logo Mail Archive

Re: [DNSOP] Alternative Special-Use TLD problem statement draft

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 06 April 2016 11:57 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FA612D985 for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 04:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 abzOzgZY9oG0 for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 04:57:31 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (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 5B0EC12D9AE for <dnsop@ietf.org>; Wed, 6 Apr 2016 04:57:31 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 4E3023283E; Wed, 6 Apr 2016 13:57:29 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id 02EAEF01172; Wed, 6 Apr 2016 13:52:43 +0200 (CEST)
Date: Wed, 06 Apr 2016 08:52:43 -0300
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Philip Homburg <pch-dnsop@u-1.phicoh.com>
Message-ID: <20160406115243.GA14413@laperouse.bortzmeyer.org>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <m1anlSH-0000IqC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <m1anlSH-0000IqC@stereo.hq.phicoh.net>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 15.10 (wily)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/4yLKyaDUB8_vtsAD9JJ_dU385X4>
Cc: dnsop@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 06 Apr 2016 11:57:34 -0000

On Wed, Apr 06, 2016 at 01:17:00PM +0200,
 Philip Homburg <pch-dnsop@u-1.phicoh.com> wrote 
 a message of 43 lines which said:

> In fact, there is quite a bit of history already in some programming
> languages (for example java) to just register a DNS domain to get a private
> part of the global name space.
> 
> So anybody who wants to play with an experimental naming service can just
> register my-naming-service.net. And use that string in any name switch code.

Strong dissensus here. The problem is there is no safe way to have AND
KEEP such a name. You depend on the registry's policy, which may suit
you or not, and, if the registry uses RRR, you depend on the
registrar's behavior. One mistake by Go Daddy or Network Solutions and
you lose your namespace. One complaint to a private "court" such as
UDRP and you lose your namespace.

It may work for a big company like Sun with a lot of lawyers. It does
not for the typical free software project such as .onion or the people
in the queue (.gnu, .bit, etc).

v2.23.0 | Report a Bug | By Email