Re: [urn] Formal request for URN for ITU

John C Klensin <john-ietf@jck.com> Thu, 05 July 2018 17:52 UTC

Return-Path: <john-ietf@jck.com>
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 2766D130F0D for <urn@ietfa.amsl.com>; Thu, 5 Jul 2018 10:52:24 -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 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 BmjDWxu0HuZv for <urn@ietfa.amsl.com>; Thu, 5 Jul 2018 10:52:22 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7453A130E80 for <urn@ietf.org>; Thu, 5 Jul 2018 10:52:22 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fb8QX-000POS-8p; Thu, 05 Jul 2018 13:52:21 -0400
Date: Thu, 05 Jul 2018 13:52:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Mansfield <scott.mansfield@ericsson.com>
cc: urn@ietf.org
Message-ID: <8B4DF361D74A8722EF1299D2@PSB>
In-Reply-To: <CY1PR15MB02351FC6CF76DE7066B2153D8B400@CY1PR15MB0235.namprd15.prod.outlook.com>
References: <HE1PR07MB30973FDE0B164C8DD774BE58FA410@HE1PR07MB3097.eurprd07.prod.outlook.com> (juha.hakala@helsinki.fi) <871sci6elu.fsf@hobgoblin.ariadne.com> <CY1PR15MB023507708A716A8BEEE8DEEB8B400@CY1PR15MB0235.namprd15.prod.outlook.com> <E552A135F191B2BCF6E724AF@PSB> <CY1PR15MB02351FC6CF76DE7066B2153D8B400@CY1PR15MB0235.namprd15.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/-U4e97gWzcOAZkgjfw3BXZPeNHA>
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: Thu, 05 Jul 2018 17:52:25 -0000


--On Thursday, July 5, 2018 17:44 +0000 Scott Mansfield
<scott.mansfield@ericsson.com> wrote:

> Thanks John,
> 
> Exactly right on your points below.  I don't want to get into
> hypotheticals and I was trying to point out what is driving
> the ITU's request.  I like your point about providing some
> text that will ensure the ITU considers the impact of
> expanding the use of the namespace outside of the current
> known use-cases.
> 
> This is something I will have the ITU capture in an update to
> their internal document that the request points to.  There are
> a couple of updates already needed to that document.

And _that_ is, IMO, exactly where it should be... part of their
internal norms for how the namespace is managed rather than
promises they make to IANA or the IETF.   Even if there were no
other reasons, if someone in the ITU structure (either volunteer
or staff) comes along in a few years and starts thinking about
new sub-namespaces, we can be rather confident that document
will be consulted while I would be fairly pessimistic about
consultation of the IANA site (at least before a pointer to it
was found in that document).

> This will raise awareness in the ITU, and provide a pointer
> for others to see that the ITU will consider impacts when the
> use of the namespace grows.

Exactly.
Thanks
    john