Re: [urn] Formal request for URN for ITU

worley@ariadne.com (Dale R. Worley) Sat, 07 July 2018 02:41 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0DA130DFA for <urn@ietfa.amsl.com>; Fri, 6 Jul 2018 19:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level:
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 2IEhUaXPUyLJ for <urn@ietfa.amsl.com>; Fri, 6 Jul 2018 19:41:24 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D148C1277C8 for <urn@ietf.org>; Fri, 6 Jul 2018 19:41:24 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id bd3ZfSxAHCL7sbdA3fdp7Z; Sat, 07 Jul 2018 02:41:23 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id bdA2frzP8AkphbdA2fv6KR; Sat, 07 Jul 2018 02:41:23 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w672fL8B015467; Fri, 6 Jul 2018 22:41:21 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w672fKbA015464; Fri, 6 Jul 2018 22:41:20 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: John C Klensin <john-ietf@jck.com>
Cc: scott.mansfield@ericsson.com, urn@ietf.org
In-Reply-To: <E552A135F191B2BCF6E724AF@PSB> (john-ietf@jck.com)
Sender: worley@ariadne.com
Date: Fri, 06 Jul 2018 22:41:20 -0400
Message-ID: <874lhb4vjj.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfEqFAixz7uK8xEStpc+ofBqHszitBuqfliwSwhai8rp1YP/89Z6ULMKwTAoIR46XkH0ydB3jq4RBLjHaefvXbWVLksA/5CBy5jVNchewEiBOY6odF7S5 AdXTLkKuXJT4hvkfD6HK6atJuaRACqqRWczgknNVte4YlnyS8bZ401tfoFYW497I1+xkJ5u4QF3+4GfvgsslVZn2nn+Q5fx2Pihrh0Swf1vCjqby4aLrmwkd gNjT2cL6kHXpacpDkMTrNrKXYO4cSit4jTt6ovCEgmYbUotr9E3linaWnZYcVUJ3Nrc+AwuhBKhlCw3OxHK++w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/G-VMMxdEtOeRBpQ2fuIrXyF8Kbc>
Subject: Re: [urn] Formal request for URN for ITU
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2018 02:41:27 -0000

John C Klensin <john-ietf@jck.com> writes:
> A suggestion, partially in support of getting this done rather
> than dragging it out further.
>
> Let's take the request at face value: The ITU wants an NID and
> namespace for ITU uses, which the General Secretariat will take
> responsibility for but T-Sector will managed.  At least in the
> near term, the only things that namespace is likely to be used
> for are YANG-related.  In the longer term, I hope the ITU will
> be alert enough to the possibilities of disruption and confusion
> to be careful about what other sub-namespaces might be used an
> to consult with this list and others before doing that.

I think I'm echoing John here when I say that in this conversation we've
touched on a lot of complicated tangential issues, but none of them are
relevant to approving this request.

There have been a bunch of concrete "issues" raised, but as far as I can
tell, all of them are of the form "Have you considered that alternative
XYZ might be better?"  And it appears that the people behind the
registration either have already considered those questions or are
currently resolving them.

So it seems to me that all we're waiting for is for Scott to provide the
final version of the registration request (and aligning that ITU
internal document).

Am I mistaken?

Dale