Re: [DNSOP] More after onion? was Re: Some distinctions and a request

hellekin <hellekin@gnu.org> Thu, 02 July 2015 14:10 UTC

Return-Path: <hellekin@gnu.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 6B0AD1A1BA4 for <dnsop@ietfa.amsl.com>; Thu, 2 Jul 2015 07:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level:
X-Spam-Status: No, score=-1.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_31=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 YWF4P7nH8SGL for <dnsop@ietfa.amsl.com>; Thu, 2 Jul 2015 07:10:51 -0700 (PDT)
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:4830:134:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3429D1A066B for <dnsop@ietf.org>; Thu, 2 Jul 2015 07:10:49 -0700 (PDT)
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1ZAfCL-0001sZ-AY for dnsop@ietf.org; Thu, 02 Jul 2015 10:10:47 -0400
Received: from fencepost.gnu.org ([208.118.235.10]:36774) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1ZAfCL-0001sO-7p for dnsop@ietf.org; Thu, 02 Jul 2015 10:10:41 -0400
Received: from ol168-138.fibertel.com.ar ([24.232.138.168]:50564 helo=raiz.hellekin.gnu) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <hellekin@gnu.org>) id 1ZAfCK-0001CZ-Ms for dnsop@ietf.org; Thu, 02 Jul 2015 10:10:40 -0400
Message-ID: <55954639.80602@gnu.org>
Date: Thu, 02 Jul 2015 11:10:01 -0300
From: hellekin <hellekin@gnu.org>
Organization: https://gnu.org/consensus
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <D1B951E7.C996%edward.lewis@icann.org> <B26365D7-11B3-441D-BED3-5FEFB671B0FA@gmail.com> <D1B966DB.C9AC%edward.lewis@icann.org> <DF014EDF-819B-47BB-817D-AB13D57A57E9@gmail.com> <CAHw9_iJQ+Ydu4m-dd8cMOvVtYkKdEYMO_bx1Z5GBX3jLVgq=Jg@mail.gmail.com> <CAL02cgQYxFq7C0mWbs92RzoELU-Di9juKc5Dg16SP_ze=BzXxw@mail.gmail.com> <20150701185537.768A3AE447@smtp.postman.i2p> <20150701223712.84403AE444@smtp.postman.i2p> <D1BAAC30.CA32%edward.lewis@icann.org>
In-Reply-To: <D1BAAC30.CA32%edward.lewis@icann.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 208.118.235.10
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/9J9gciO7nGIHw7dxMwtTvaGz-RM>
Subject: Re: [DNSOP] More after onion? was Re: Some distinctions and a request
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 02 Jul 2015 14:10:57 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 07/02/2015 10:05 AM, Edward Lewis wrote:
> 
> You're right.  To underscore, it's because of the groups that
> don't engage, and have no responsibility to do so, that the IETF
> has to "defend" itself.
> 
>> It wouldn't take much work
> 
> Keep in mind that the IETF isn't a "thing", it's a collection
> of people volunteering time.  What I mean to say, not much work,
> but it's like trying to jump out of the ocean back into a boat.
>

I could not agree more with Str4d.  Processes are not at fault: aren't
we having a rough consensus about the Internet as an open society?

For your information, draft-grothoff-iesg-special-use-p2p-names-00 was
published on *November 14, 2013* [0]. It has been submitted to 4
revisions to date, without counting the newly split drafts at the
request of DNSOP list members into a draft per system (.bit [1], .exit
[2], GNS [3], and .i2p [4]).

As a final comment to help you catch up with "the process", the .alt
draft [5] first appeared on June 06, 2015, and the original mention of
.onion was removed from its fifth revision following my request to
confirm that .onion was not covered by this draft (per the draft
author.) I think you know this because your comments were also included
in this version of the .alt draft.

I am very surprised that you did not read the P2PNames draft, and hope
you will now read the 5 drafts that came from it (I include .onion [6]
to the 4 mentioned above).

Regards,

==
hk

P.S.: As Christian Grothoff mentioned, I was interested in making these
5 drafts leanier, following the .onion model, and bring the (common)
details into an informational RFC instead. If you think 5 drafts are too
much reading, that might help, especially as there's a lot of redundancy
from one to the next.

[0]:
https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-nam
es/00/
[1]:
https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-bit
/
[2]:
https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-exi
t/
[3]:
https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-gns
/
[4]:
https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-i2p
/
[5]: https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/
[6]: https://datatracker.ietf.org/doc/draft-appelbaum-dnsop-onion-tld/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJVlUYyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9zpIP/3QJF7Eni4RrzwAn5U3ITnqo
vsv/cTcVYTm2EybW3mFaY/UeE868HyHrsF0mXOIxwm/B6lFCAKA47B5m+zvqhRwA
I1euxD9L/KOoB/8//sE+JLzKffiwGPaI2MY6r3Wiqb5ivijy1sVVuwr8GV2QdvoD
Nvflcnu+iXX3IQJpZTDxrrmKjYIdgXxCxKPKYquf4kE3cMWv/5sEolYvTH1eHlLV
MBGzzKZntE487u0RGEiym0teE0xV3U09Ln7cpppMmKrrKs3UkcXfqFbB+fhKHP+N
J54Pif+ndiMeBAcYuoj4/OXtT+x1r3rOR8PLgUvdlYfBsJpjOlREAVqDP/c9R1sW
PWkSkrBmo1hTkQv5ZPt/EBc6Fiovq3k0ptnO3GXn4XOT1udXarlAXpZm7KvzY7Sc
DG6Q2EXM8//w4jwfC3mBt+jFEskijEh6G2sNo0z8lBsgyU9EZuSkUGMtT3c1nLaX
jnV0Qd90tpD9tP/dGk/U4S8V4Wg9fhBxlDbMYiEFRttaGdL4MGFXoSDcHLuqDTTX
QAtDx2kvR/yhLJY5OHO1qGvTjixcfMz82COrRCEsczH4psjS/iRziT1DlGX2aMQr
6kSOPq0EtabdfYwsHSETfh4KC1DfzzIEVlvFen3hs9sIrj631HACoZfMLNYcjbmH
vNO8NaLUMJsIIi9eniQ2
=0u6r
-----END PGP SIGNATURE-----