IETF Logo Mail Archive

Re: [urn] gbs Name space identifier

worley@ariadne.com (Dale R. Worley) Thu, 17 October 2019 01:37 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 11180120047 for <urn@ietfa.amsl.com>; Wed, 16 Oct 2019 18:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.216
X-Spam-Level:
X-Spam-Status: No, score=0.216 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 wM52vMn3uNNZ for <urn@ietfa.amsl.com>; Wed, 16 Oct 2019 18:37:16 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 B2CB5120019 for <urn@ietf.org>; Wed, 16 Oct 2019 18:37:16 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id KsojiWYJXkltDKuj5ivDFp; Thu, 17 Oct 2019 01:37:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1571276235; bh=w6MZG8we27942YL2MNlDkwn8b6d235j190G/VsEUAKE=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Md1MJvyfZGl4oQ7zVa+z40Df1SL2Pj2QY8OQG3bzbtiL9mnNgvyMvg17XoKwuw/Ue r5LoSY20U2M2ia8g4nCGfbUr9tIxhGWu5ELo44yA3d/Py734ChEkmYGOoqLJQPlm8S AjzLVL1vyu2CAhkZSTyxEO5q5qqGZRGBJQO8cUy9UH8tCkJtUySXH6nWFQS8lln1H1 dKEHgVSUkYvovE1aE0eLVdvrpSzBI94f6wvsWQqlijVqE4j8qYz8vkp3x1zuuC4eHy P4FxQJN7YG03wtMhZn8U+VoYsW70K/sIg2xpajtoem8+ezbFaMCyK2TbUW02onRwkb Z+kE1a/cqkXIA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-19v.sys.comcast.net with ESMTPA id Kuj2iWBU54l1cKuj3idrM2; Thu, 17 Oct 2019 01:37:14 +0000
X-Xfinity-VMeta: sc=-100;st=legit
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 x9H1bBCF011127; Wed, 16 Oct 2019 21:37:11 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x9H1bBQb011124; Wed, 16 Oct 2019 21:37:11 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
Cc: philiprbrenan@gmail.com, lars.svensson@web.de, urn@ietf.org
In-Reply-To: <HE1PR07MB3097B87B52D645973095F252FA9C0@HE1PR07MB3097.eurprd07.prod.outlook.com> (juha.hakala@helsinki.fi)
Sender: worley@ariadne.com
Date: Wed, 16 Oct 2019 21:37:10 -0400
Message-ID: <87pniwm9tl.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/tyqMZTj9wLlmFUrWLlSvvP0uZ1I>
Subject: Re: [urn] gbs Name space identifier
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2019 01:37:18 -0000

"Hakala, Juha E" <juha.hakala@helsinki.fi> writes:
> IMO one of the main challenges with namespace registration requests
> has been that the authors themselves usually know well the intended
> scope the proposed namespace. Alas, it may be difficult to communicate
> this information to reviewers who might not be familiar with the
> context.

True.  But of course, one of the purposes of a URN registration is to
communicate to the public the intended scope of the proposed namespace.
(RFC 8141, section 6.4.1, item 2)  We're here to help registrants do
that.

Dale

v2.23.0 | Report a Bug | By Email