Re: [DNSOP] *.DNS metaTLD [ref: additional special names]

Christian Grothoff <christian@grothoff.org> Wed, 05 March 2014 15:04 UTC

Return-Path: <christian@grothoff.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 B32351A0641 for <dnsop@ietfa.amsl.com>; Wed, 5 Mar 2014 07:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level:
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 sVkwYOX39G_c for <dnsop@ietfa.amsl.com>; Wed, 5 Mar 2014 07:04:39 -0800 (PST)
Received: from smtp1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by ietfa.amsl.com (Postfix) with ESMTP id 774171A063E for <dnsop@ietf.org>; Wed, 5 Mar 2014 07:04:39 -0800 (PST)
Received: from [131.159.20.32] (pixel.net.in.tum.de [131.159.20.32]) by mail.net.in.tum.de (Postfix) with ESMTP id 194FB188D02E for <dnsop@ietf.org>; Wed, 5 Mar 2014 16:04:34 +0100 (CET)
Message-ID: <53173D01.8050508@grothoff.org>
Date: Wed, 05 Mar 2014 16:04:33 +0100
From: Christian Grothoff <christian@grothoff.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <F88E53A6-A9CC-4F44-A986-AEB8F02EEFA1@okturtles.com> <7923940A-298A-49A2-8153-4777C95DDA77@hopcount.ca> <20140302230243.GA17774@laperouse.bortzmeyer.org> <FDBDECCE-35BE-48A8-B3ED-79ED5E89D633@hopcount.ca> <20140305145036.GC19170@laperouse.bortzmeyer.org>
In-Reply-To: <20140305145036.GC19170@laperouse.bortzmeyer.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/YPEjKxCMPA0n_14QTiKavgRM93I
Subject: Re: [DNSOP] *.DNS metaTLD [ref: additional special names]
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: Wed, 05 Mar 2014 15:04:42 -0000

On 03/05/2014 03:50 PM, Stephane Bortzmeyer wrote:
> On Mon, Mar 03, 2014 at 01:09:24PM +0000,
>  Joe Abley <jabley@hopcount.ca> wrote 
>  a message of 32 lines which said:
> 
>> It's clear that it's possible to arrange very stable registration of
>> domains, sufficient at least for some very valuable web properties
>> to base their businesses on.
> 
> When you are a big company like amazon.com or google.com with money,
> lawyers and so on. Not when you are a free software project ran by
> volunteers.
> 
>> I suggest that it's entirely plausible for someone to choose a
>> DNS-namespace anchor for their non-DNS namespace that is as stable
>> as they want, depending on their needs.
> 
> Many people who lost their domain name would like to know how to do
> that.

Yes, and while you're at it, please tell the people from
thepiratebay.org --- their ability to keep a stable DNS namespace anchor
has been abysmal recently.