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

SM <sm@resistor.net> Tue, 03 December 2013 22:41 UTC

Return-Path: <sm@resistor.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 858221AE164 for <dnsop@ietfa.amsl.com>; Tue, 3 Dec 2013 14:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] 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 E9WEpW8lSYYp for <dnsop@ietfa.amsl.com>; Tue, 3 Dec 2013 14:41:20 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D88E1AE082 for <dnsop@ietf.org>; Tue, 3 Dec 2013 14:41:20 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rB3MdaRO023667; Tue, 3 Dec 2013 14:39:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1386110386; bh=LkuOeLwl97xSzSaakrkpqDQYxmsiqIalUan3WS8u7QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FSstuLOdSGuIOHjIZ+qBrpyMAQaPhAclpfEnOa4e/B9ZAPgvFdCflZSGYoWDsJWgi o0WB2Gj/GyA6lhOQHacaI1QwQ73vCqiZRx5LsPuZag9/PFvKMqRZLGJPTymTfY4JkK TMK5ON/kcmlHzrjHoZjqghD8xXExEgiyn/FuKcEs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1386110386; i=@resistor.net; bh=LkuOeLwl97xSzSaakrkpqDQYxmsiqIalUan3WS8u7QA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bCTY8fCkwiTmCSFhi3yOIV6epKjxsb8ii3PvMsWJqXpdsMseq4zDmSOdoYYzc7Lpp QtpFYDRIKz/O7vWXUevLqI9hzahny7SYvwLoTLpueSEaejB1LHUZuxM3zZrOFJlHoy q1LqXGeb4vk76HT26maMYPDrURv5UJf9mdbi2eQo=
Message-Id: <6.2.5.6.2.20131203140954.0d138140@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 03 Dec 2013 14:38:39 -0800
To: Jacob Appelbaum <jacob@appelbaum.net>
From: SM <sm@resistor.net>
In-Reply-To: <529E0C68.6070002@appelbaum.net>
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> <6.2.5.6.2.20131203073816.0d146ab8@resistor.net> <529E0C68.6070002@appelbaum.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Christian Grothoff <christian@grothoff.org>, dnsop@ietf.org, "hellekin (GNU Consensus)" <hellekin@gnu.org>, Paul Wouters <paul@cypherpunks.ca>
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: Tue, 03 Dec 2013 22:41:21 -0000

Hi Jacob,
At 08:52 03-12-2013, Jacob Appelbaum wrote:
>In terms of informational RFCs, I think it is clearly a good idea to
>document what is realistically in use.

Yes.

>I assume that .local did not always have history? However, I think that
>there are clearly many p2p systems with a history as well - .onion is
>nearly ten years old now.

I was referring to the history within the IETF.  The (draft) proposal 
took over ten years to be published.

>What would make it a good explanation?

I'll read the draft again and comment.  Seriously, it is difficult to 
tell what would be a good explanation.  I would describe it as "the 
person has thought about the issues and can provide good answers for them".

>What is a better alternatively? Shall we ignore the IETF and ICANN
>entirely? Shall we give up on IETF and shell out the cash to ICANN?

It is premature to give up on getting the draft published by the 
IETF.  I would answer "no" to the second question. :-)

>The P2P systems push the boundary - the informational RFC merely
>documents it and ensures that the IETF is the best place to find that
>information.

I'd say put the process discussion on hold, focus on the technical 
content; then discuss the draft within the IETF.

Regards,
-sm