Re: the names that aren't DNS names problem, was Last Call: <draft-ietf-dnsop-onion-tld-00.txt>

John Curran <jcurran@istaff.org> Thu, 23 July 2015 21:47 UTC

Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1EA1AD35A for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2015 14:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 idbl0HSe2wQI for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2015 14:47:19 -0700 (PDT)
Received: from outbound1a.ore.mailhop.org (outbound1a.ore.mailhop.org [54.213.22.21]) by ietfa.amsl.com (Postfix) with SMTP id 1EA751B2A8F for <ietf@ietf.org>; Thu, 23 Jul 2015 14:45:23 -0700 (PDT)
Received: from [192.168.1.6] (unknown [108.51.98.21]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 23 Jul 2015 21:44:56 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: the names that aren't DNS names problem, was Last Call: <draft-ietf-dnsop-onion-tld-00.txt>
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAKr6gn2413-2XW8d_stw0dTmP-KsmGgFgQ3tVXEgXrXmnCiQow@mail.gmail.com>
Date: Thu, 23 Jul 2015 17:45:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E97605B-C11E-4349-90FC-109E4983112C@istaff.org>
References: <20150720192219.53802.qmail@ary.lan> <55ADF2A7.3080403@cisco.com> <A0418F96-1D79-4BE9-A72A-7A47641E4AF3@gmail.com> <CAKr6gn1apWx2M7V-O6ea2kvor7Di6=jYMh-uY2ouTsgjkV6vLw@mail.gmail.com> <20150722084204.GA15378@laperouse.bortzmeyer.org> <CAKr6gn2413-2XW8d_stw0dTmP-KsmGgFgQ3tVXEgXrXmnCiQow@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zz9HlEfkVHIQylnyJvuZlkux7WU>
Cc: ietf <IETF@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 21:47:21 -0000

On Jul 22, 2015, at 6:28 AM, George Michaelson <ggm@algebras.org> wrote:
> I merely noted that there are voices (myself included) who think a revision might be most useful if it abnegated the right to make these decisions and said "the root zone vests with other people: ask other people to do things”

George -

A interesting assertion, given that the root zone is the entire top-level of the
identifier space and would specifically include "assignments of domain names
for technical uses”.  I will observe that the latter is a right which the IETF has 
already reserved for itself, ceding to ICANN the general purpose assignments,
i.e. that which "present policy issues” (at least as described in the IETF/ICANN 
MOU [RFC2860])

That’s not to say that the IETF can’t revise this position as desired, only that 
it should be recognized as a change from documented state.  It might also be
good to consider the principle of whether it is ever good practice for the IETF 
to completely delegate an registry identifier space without retaining some 
ability for making specialized/technical assignments…)

/John

Disclaimer: my views alone.  email contains 100% reused electron content.