Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]

Warren Kumari <warren@kumari.net> Mon, 02 December 2013 15:50 UTC

Return-Path: <warren@kumari.net>
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 EEA801ACC7D for <dnsop@ietfa.amsl.com>; Mon, 2 Dec 2013 07:50:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 tpekgGJbzvvB for <dnsop@ietfa.amsl.com>; Mon, 2 Dec 2013 07:50:43 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA0F1AC829 for <dnsop@ietf.org>; Mon, 2 Dec 2013 07:50:43 -0800 (PST)
Received: from [192.168.0.187] (c-98-244-98-35.hsd1.va.comcast.net [98.244.98.35]) by vimes.kumari.net (Postfix) with ESMTPSA id CAFAF1B40039; Mon, 2 Dec 2013 10:50:40 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_8229F489-846C-4D47-8291-2AA501EC219A"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <529C593E.4090702@sidn.nl>
Date: Mon, 02 Dec 2013 10:50:35 -0500
Message-Id: <9850B4A9-1500-4E1A-A369-2D1977EE7E25@kumari.net>
References: <20131201164841.GB12135@sources.org> <529C593E.4090702@sidn.nl>
To: Marco Davids <marco.davids@sidn.nl>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-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, 02 Dec 2013 15:50:45 -0000

On Dec 2, 2013, at 4:56 AM, Marco Davids (SIDN) <marco.davids@sidn.nl> wrote:

> On 12/01/13 17:48, Stephane Bortzmeyer wrote:
> 
>> For the record, I've reviewed
>> draft-grothoff-iesg-special-use-p2p-names-00, I find it well-written
>> and clear and I fully support it. Registering these names would be a
>> very good idea.
> 
> Would it be worthwhile to add .bit to the list (Namecoin)?

And I would like .pony as well please.

The concern that we run into is deciding where to draw the line -- can I just start using .wkumari in some random namespace and ask for it to be reserved?

Either these are "real" DNS names and should follow the "normal" DNS process (whether or not we like that process), or they are not, and don't really belong in the DNS.
I get that there are some "special cases" -- would it be feasible to reserve *one* name (.p2p? .namespace?) and have things like this migrate over time under names within that? (.gnu.namespace)? Or simply move these under some existing namespace.

W


> 
> --
> Marco
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
No man is an island, But if you take a bunch of dead guys and tie them together, they make a pretty good raft.
                --Anon.