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

Christian Grothoff <grothoff@gnunet.org> Sun, 01 December 2013 18:31 UTC

Return-Path: <grothoff@gnunet.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 95D6F1AE064 for <dnsop@ietfa.amsl.com>; Sun, 1 Dec 2013 10:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] 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 03NILj7qJHox for <dnsop@ietfa.amsl.com>; Sun, 1 Dec 2013 10:31:03 -0800 (PST)
Received: from smtp1.informatik.tu-muenchen.de (smtp1.informatik.tu-muenchen.de [131.159.0.99]) by ietfa.amsl.com (Postfix) with ESMTP id 1414C1AE094 for <dnsop@ietf.org>; Sun, 1 Dec 2013 10:31:03 -0800 (PST)
Received: from [192.168.178.20] (pd95c0f92.dip0.t-ipconnect.de [217.92.15.146]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 0C9BA1A37A2E; Sun, 1 Dec 2013 19:30:58 +0100 (CET)
Message-ID: <529B8061.5070206@gnunet.org>
Date: Sun, 01 Dec 2013 19:30:57 +0100
From: Christian Grothoff <grothoff@gnunet.org>
Organization: GNUnet Project
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <20131201164841.GB12135@sources.org> <BF87877A-8989-4AA4-9ED1-52C82E1BC538@nominum.com> <alpine.LFD.2.10.1312011206480.12923@bofh.nohats.ca> <20131201175318.GD12135@sources.org>
In-Reply-To: <20131201175318.GD12135@sources.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 06 Dec 2013 10:34:45 -0800
Cc: dnsop WG <dnsop@ietf.org>, Paul Wouters <paul@cypherpunks.ca>, Ted Lemon <ted.lemon@nominum.com>, Jake Appelbaum <jacob@appelbaum.net>
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: Sun, 01 Dec 2013 18:39:33 -0000

On 12/01/2013 06:53 PM, Stephane Bortzmeyer wrote:
>> Why was .gnu on that list? 
> 
> The GNUnet top-level was named .gads at a time. I do not know the
> reasons for the change.

The reason was that Jake strongly disliked ".gads" and suggested
".gnu" to Richard at IETF 87 and we all agreed that this would
make sense (shorter, easier to understand / remember, etc.).

>> people can plugin onion.alt, gnu.alt, etc, and are guaranteed that
>> the .alt domain will never actually be delegated by the root.
> 
> Avoiding a collision with an ICANN domain is not the only rationale
> for RFC 6761. The main idea is to have a registry of domains which
> require special handling by software (for instance, "do not use DNS,
> send to mDNS").

... and as I tried to point out, proposing ".alt" merely moves this
problem one level down.

>> But can an RFC even do anything here?  Whether you agree with ICANN
>> procedures for new gTLDs or not, if I write some software that
>> becomes popular using a .paul pseudo domain, when does it become
>> valid for me to request it under RFC 6761?
> 
> RFC 6761 does not say anything about that. Do note a TLD has already
> been registered under RFC 6761, .local. Some people may say that, when
> you are a big US company, just hijack the TLD, deploy the software,
> and the IETF will ruberstamp you. But if you are just ordinary people
> working to improve the Internet, you have no chance of even being
> seriously considered.
>
>> What precedent would tor/gnu/zkey/etc set?
>
> Precedent? And .local, what was it?

Unless of course our draft is excepted, which would show that IETF
is not entirely owned by companies and it willing to work with
free software developers, researchers and document issues for
normal users.  Call me an idealist, but that was my hope when
we wrote the draft.  Some at IETF have also asking the Tor
project to document it's protocols as RFCs, I guess trying to
demonstrate that IETF cares about security and privacy.

>> Does IETF even have any say in such matters? Isn't this up to IANA or
>> ICANN? What about trademarks? What about lawsuits by Gnu Inc or Onion
>> Corp who want their gTLD?
> 
> RFC 6761 "Hence, the act of defining such a special name creates a
> higher-level protocol rule, above ICANN's management of allocable
> names on the public Internet." So basically, RFC 6761 says that IETF
> has the right to create TLD at will. 

I'd say "IETF asserts the right", as I'm personally not sure which German
or EU law gives the IETF (or ICANN) any rights in this matter (and
no, not everybody lives in the US and is subject to US law), but I
do of course agree with the sentiment. Still, I see this primarily
as a technical issue (document! _informational_ RFC), and not a legal
one.


Happy hacking!

Christian