IETF Logo Mail Archive

Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld

"John R Levine" <johnl@taugh.com> Sat, 06 June 2015 01:36 UTC

Return-Path: <johnl@taugh.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 9580F1A8991 for <dnsop@ietfa.amsl.com>; Fri, 5 Jun 2015 18:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 Wl2ojmujNksM for <dnsop@ietfa.amsl.com>; Fri, 5 Jun 2015 18:36:01 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 445AE1A1A82 for <dnsop@ietf.org>; Fri, 5 Jun 2015 18:36:00 -0700 (PDT)
Received: (qmail 58073 invoked from network); 6 Jun 2015 01:36:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e2d8.55724e88.k1506; bh=RZwsZSJfUdgOIE3uwEZwrt56ZFLQ9/CeiV7ptE3g2Mw=; b=KmwRT+DbRyqQhrBgS5pCYhzSV53V5/HSCCv1LRie0cQgS4EMYgwgEC9mWFBFUZb+BtlVHq3fk9rOFnZIcwwllBhJZL/T2EVWh1AoOmrKT6fmdhXLYmAbjtgs/dFqUzx0r/kFkga0p4rCkZrjLra8+Qp2qnLMJicGzU5t0PbmYhADCZ8zlkRpLHgPkSDFqp3FqJ/EjRTrhP91NgTY5G+oFoyRUaglXnHa39ILlaoU4SbbgW0ubv5Lu/5/cuRQRrFf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e2d8.55724e88.k1506; bh=RZwsZSJfUdgOIE3uwEZwrt56ZFLQ9/CeiV7ptE3g2Mw=; b=N/s7934qgUfR2UaSYSyR8ZnUuY/fn9Ume2oHttcbP175wbC19Nj3FGbX6Oakq/hrSIXcDhWwD5DGg84ecMMAegJ0SNj/gm3B5vFDQjeuNpT50g4SWVu+hr/NQ/Mx9pXgDkVOxyhEsGG0m/5m1G+SZfguwgt0xNjIOiqT15TxIrq2tJLkx5nZUF6U8OGlHB09bUs5aF93+pCBprJvRoJnrRq7ZiEKzFdCviDZPBd7a/M8kr0NRQITYq12EUoQhTRD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 06 Jun 2015 01:36:08 -0000
Date: Fri, 05 Jun 2015 21:36:27 -0400
Message-ID: <alpine.OSX.2.11.1506052131210.60108@ary.local>
From: John R Levine <johnl@taugh.com>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAHw9_iLzirFg7HdTJzeNnFZZe+6NxEjyOMSbKazCN85OkAmnQw@mail.gmail.com>
References: <20150604155936.GJ94969@mx2.yitter.info> <20150604195302.45322.qmail@ary.lan> <CAHw9_iLzirFg7HdTJzeNnFZZe+6NxEjyOMSbKazCN85OkAmnQw@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/JEl5J7ELxpz9VfIR0m4xvs6KS7Y>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld
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, 06 Jun 2015 01:36:02 -0000

>> As I mentioned before, given that the whole point of .alt is that
>> people are implementing things that look like DNS names but are
>> resolved in some other way, the winner of any such conflict is the one
>> with widely used running code.
>
> Yah. If I'm launching a new namespace that resolves based upon
> <something>, I have an incentive to choose a string that isn't already
> being used by some other large, well known project, in the same way
> that it would be silly for me to write a new UNIX program that does
> something like cowsay (but with kittens) and call it 'cat'.

Exactly.  The ICANN approach is what I might call the gold rush model -- 
people dash out to grab likely looking territory and squat on it before 
anyone else does.  This is more like homesteading -- there's a practically 
unlimited amount of territory, anyone can get some, but it you want to 
keep it, you have to live on it and improve it.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email