Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

hellekin <hellekin@gnu.org> Thu, 07 May 2015 14:16 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 B0C131A8A48 for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 07:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5b8tcvDrX6wX for <dnsop@ietfa.amsl.com>; Thu, 7 May 2015 07:16:00 -0700 (PDT)
Received: from fencepost.gnu.org (fencepost.gnu.org [IPv6:2001:4830:134:3::e]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AFC71A8A81 for <dnsop@ietf.org>; Thu, 7 May 2015 07:15:51 -0700 (PDT)
Received: from ol168-138.fibertel.com.ar ([24.232.138.168]:58721 helo=raiz.hellekin.gnu) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1YqMaY-0002z8-Ns for dnsop@ietf.org; Thu, 07 May 2015 10:15:48 -0400
Message-ID: <554B736A.4050807@gnu.org>
Date: Thu, 07 May 2015 11:15:06 -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: <D5D3A5AC-41B5-4872-B973-2752275D651E@gmail.com> <D170E3E4.1011F2%jason_livingood@cable.comcast.com>
In-Reply-To: <D170E3E4.1011F2%jason_livingood@cable.comcast.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/GuG3QAhBcGihpDFDi9q59WLFl9U>
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
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: Thu, 07 May 2015 14:16:01 -0000

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

On 05/07/2015 10:56 AM, Livingood, Jason wrote:
> 
> Beyond that, does it end up being a cheap way to avoid the ICANN
> process
>
*** It makes sense to follow that process for systems that use the DNS,
not for Special-Use Domain Names.  If you would read the P2PNames and
.onion drafts, you would instantly become aware of many things that
would prevent the Tor Project from registering a gTLD, first of all,
.onion is not a gTLD.

> By ‘redundant’ do you mean the IETF should take no action?
>
*** Given that ICANN already decided "to reserve the names permanently",
an action of the IETF would only confirm that these names should be
reserved by ICANN--which makes such action redundant.  I don't see
anything remotely related to any "uncertainty [that] could inhibit
experimentation/investment in the home networking space".

> 
> so the IETF should probably have quite simple and brief criteria and
> try to limit this strictly – and perhaps even make it a one-time
> activity.
> 
*** I think such criteria exist and are defined in RFC 6761.

> 
> Why not just a new RFC?
>
*** Why not using the existing RFC?

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

iQJ8BAEBCgBmBQJVS3NhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9FyoP/22mi2rZQki1XUiYjrLg4MwH
92+ycEsG6nrNoBrCPpP4G/i6S1n91jrXVRUf/wrzfTE1S32CePjg3I5wuhBnraWN
V166w4Ow9ni6+et1ZoIOHvZI13JO7lnlm1JvQSVBUL2aSuH/fm/jXnu8VxtUNpyF
L0uZtwRayTfq1hu3HI7pKRsXBZmM8xJZ0SZ8tLjoF/v9A4eXShCjzItins2v3vzE
Oq4CoBy9VeffB66Wa3GiH/C0Gu9I/GP56/MI9ncjtK74qXG/Bbq0wfJXM1Z/lh3V
DdleCOvWZ+69JUyXR0PxyDpPvao5jX6vK7fKbtb0HxODSSeyAxLAjaj7XGr4LPuY
pd1l5qV6MPikqHsixRTeIDw1JT8vEK5Oal1SjnTpunWhYfn6MrYyUDCKvEnOVzG4
dg4OefxStyYi3XJPwFlRP8W6ZrdLjW/4XaG04gKaxQpoGkccDk80g0cDP9u0fcXP
/nKiy2s7s1ry/NC4+0vfvUk2UW28u73DSnLyF4CCka6oIHG4DG8/x+tTnNjPIk3h
P9F38boBulkOxWS+jfd9SQlaRTzCOC5ImPb6KxVBElGdFfsCxC+753H674ZQLdvv
ZGz8sRjXB54qKUjicdjyZ/zKrWOS+oTnqQPg/5PRy6gi3irA1rQjkmu3JBlN6+xo
tvaeIvfAT/qhFYMI4LF6
=qVM/
-----END PGP SIGNATURE-----