[urn] A comment on draft-ietf-urnbis-rfc2141bis-urn-02

Bengt Neiss <bengt.neiss@kb.se> Wed, 14 March 2012 08:36 UTC

Return-Path: <prvs=0420a0dbfd=bengt.neiss@kb.se>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6500521F86EE for <urn@ietfa.amsl.com>; Wed, 14 Mar 2012 01:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.228
X-Spam-Status: No, score=-1.228 tagged_above=-999 required=5 tests=[AWL=1.020, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zObdj70PPotW for <urn@ietfa.amsl.com>; Wed, 14 Mar 2012 01:36:17 -0700 (PDT)
Received: from mspkb002.kb.se (mspkb002.kb.se []) by ietfa.amsl.com (Postfix) with ESMTP id 86B7521F86DC for <urn@ietf.org>; Wed, 14 Mar 2012 01:36:16 -0700 (PDT)
Authentication-Results: mspkb002.kb.se header.from=bengt.neiss@kb.se; domainkeys=neutral (no sig)
From: Bengt Neiss <bengt.neiss@kb.se>
To: "urn@ietf.org" <urn@ietf.org>
Thread-Topic: A comment on draft-ietf-urnbis-rfc2141bis-urn-02
Thread-Index: Ac0BvTMxBBzUezMySK+yL8oiu8BsCA==
Date: Wed, 14 Mar 2012 08:36:12 +0000
Message-ID: <F52230A186DA59469E8E21CF80FE6D4D0F24911E@SRVVM305.kb.local>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
Content-Type: multipart/alternative; boundary="_000_F52230A186DA59469E8E21CF80FE6D4D0F24911ESRVVM305kblocal_"
MIME-Version: 1.0
Received-SPF: none
Subject: [urn] A comment on draft-ietf-urnbis-rfc2141bis-urn-02
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 14 Mar 2012 08:36:18 -0000

Hi all,

Just a comment on the text of the new text (RFC2141bis-urn-02)

I am concerned about the phrase "special meaning" in the text in the section "2.3.2. The percent character, percent encoding" as follows

"Namespaces MAY designate one or more characters from the URN
character repertoire as having special meaning for that namespace.
If the namespace also uses that character in a literal sense as well,
the character used in a literal sense MUST be encoded with "%"
followed by the hexadecimal representation of that octet.  Further, a
character MUST NOT be percent-encoded if the character is not a
reserved character."

Does "special meaning" mean "reserved character (should be treated as a reserved character within that namespace)" and thus MUST be percent encoded if it is used in a literal sense within the NSS?

In section "4.4 Additional considerations" in RFC3188bis-nbn-urn-03 the following text can be found:

"Hyphen MUST be used as the delimiting character between the prefix

 and the NBN string.  Within the NBN string, hyphen MAY be used for

 separating different sections of the identifier from one another."

My interpretation of this text is that URN's can look like "urn:nbn:se:kb-1234-5678"
Is hyphen in this text a character with a "special meaning"?

Depending on how the text about "special meaning" is interpreted the text about the use of hyphen in the NBN namespace might violate the section in RFC2141bis.

I think the phrase "special meaning" needs some clarification.



Bengt Neiss
Kungl. Biblioteket / National Library of Sweden
Phone: +46 (0)10 709 35 41