IETF Logo Mail Archive

Re: [urn] gbs Name space identifier

worley@ariadne.com (Dale R. Worley) Fri, 25 October 2019 00:27 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 1E24D12001A for <urn@ietfa.amsl.com>; Thu, 24 Oct 2019 17:27:01 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 JLcXNHqTaSaF for <urn@ietfa.amsl.com>; Thu, 24 Oct 2019 17:27:00 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (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 22FEB120019 for <urn@ietf.org>; Thu, 24 Oct 2019 17:26:59 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id Nas3iANSVLeutNnRSikXGB; Fri, 25 Oct 2019 00:26:58 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1571963218; bh=7TGuTx63u8sMwmC6qpb3pXEByOixNeRyA7JfRF8NgFU=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=rrVWCdz12iXj0S8TpMTSRH8SHmaRGVoQLOvAUMRlHJpFEEsE8kFcPjtkBjaqgsFI7 azZ9iucUyb0rmEFbKA6Msh6rg/z0/Bly8623TStTO4fDYQD1+H6KidKKPjkrb1Vl6i I2nVZ8/aaqbBHyZArH30rFot5Dqhjy/gSam9RPlubqwB42E+omKvPIRDMSLOy/SDtM otZnJeTGponNa1N2sH/b91U/tg9DpQZGv84GOKq4QgCGdFuzEohb2ClSpwEuWqbYi3 vYpN7S+Bqg4+k2fz71nG1lo8jM2SBGDHa2wcDVI84v8vmtMJJOSE4npIIK2LUBeA62 /lpdwzYQfZxxg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id NnRQi0D2KXhhvNnRRi6xMB; Fri, 25 Oct 2019 00:26:58 +0000
X-Xfinity-VMeta: sc=-100.00;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 x9P0QtVJ028837; Thu, 24 Oct 2019 20:26:56 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x9P0Qs7G028816; Thu, 24 Oct 2019 20:26:54 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Philip R Brenan <philiprbrenan@gmail.com>
Cc: urn@ietf.org, lars.svensson@web.de
In-Reply-To: <CALhwFRn21H6fOoJ_tsrXcAUhJ0cRTcrVf5Y4YuK_QJZqaU0sqw@mail.gmail.com> (philiprbrenan@gmail.com)
Sender: worley@ariadne.com
Date: Thu, 24 Oct 2019 20:26:54 -0400
Message-ID: <87r231vfe9.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/pqFtAwlM79oI_KrrjiaTeYeH6RA>
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: Fri, 25 Oct 2019 00:27:01 -0000

Philip R Brenan <philiprbrenan@gmail.com> writes:
> In the latest version (attached) I have adopted your suggestion that
> the definition of the <B> component should not be restricted to
> lowercase.  Instead the <B> component is defined, as you suggested, in
> a manner that makes it case insensitive. I have added a recommendation
> that the <B> component be presented to humans in lowercase where
> possible as I believe that this makes the <B> component less
> intimidating and thus more acceptable to people who are working on
> topics named using the proposed standard.

Yes, this looks good to me.

Dale

v2.23.0 | Report a Bug | By Email