
From nobody Tue Sep  1 00:31:27 2015
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF0A1ACD08 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 00:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.598
X-Spam-Level: *
X-Spam-Status: No, score=1.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, J_CHICKENPOX_37=0.6, MANGLED_OFF=2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 d2BalG1QQMvg for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 00:31:22 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0735.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6432A1A9171 for <urn@ietf.org>; Tue,  1 Sep 2015 00:31:20 -0700 (PDT)
Received: from AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (TLS) id 15.1.256.15; Tue, 1 Sep 2015 07:30:58 +0000
Received: from AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) by AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) with mapi id 15.01.0256.013; Tue, 1 Sep 2015 07:30:58 +0000
From: "Hakala, Juha E" <juha.hakala@helsinki.fi>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Melinda Shore <melinda.shore@gmail.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
Thread-Index: AQHQqv8vPdyydT05JUuwHnufbKXNbZ3GSVDggGEfZgCAAEPacA==
Date: Tue, 1 Sep 2015 07:30:58 +0000
Message-ID: <AMSPR07MB454C6DB429C2FECD283B24EFA6A0@AMSPR07MB454.eurprd07.prod.outlook.com>
References: <55804085.5000105@gmail.com> <5584CD07.4050906@gmail.com> <AMSPR07MB4542A8B2C582B8F1772FD0DFAA80@AMSPR07MB454.eurprd07.prod.outlook.com> <55E50FC2.8050106@andyet.net>
In-Reply-To: <55E50FC2.8050106@andyet.net>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=juha.hakala@helsinki.fi; 
x-originating-ip: [128.214.71.222]
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 5:+XtdByzXAFnfMXD3rQT3N/lOSi+wQW/dW7hk7v/TpFUCr+P2rxN7xjcMk7GPTBtxKVeAFVOQ5E2mQFW44Howpixi2bA3sJYINrCs+kHX8Zoozxpqmi+bd6fP+OkBiCREvjnUySOpORiiB1Ex79lv0w==; 24:rqftOOqS38CHr8yeDhgnwnmrCYzqkyMMlH2zkYWDSdRUTxg4fVtK29OQzS59RYZUABh465z5tsly24pFcRD+EYPshHgvYr12K9tcx007rLc=; 20:uXaz8i8tsZmG/QRzEubGuzvVsJQq/uFwojHmu2+iSg/XZiy0GUoZsag4FaPCTvCgWw9i3HIQhgmfAm69AUfJuQ==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB454AD7D741F3468D822B063FA6A0@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(5005006)(3002001); SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 06860EDC7B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(43784003)(51444003)(13464003)(189002)(199003)(2473001)(15198665003)(46102003)(122556002)(19580395003)(15395725005)(19580405001)(40100003)(5007970100001)(92566002)(189998001)(93886004)(5001860100001)(5001960100002)(5001830100001)(230783001)(74482002)(101416001)(5002640100001)(87936001)(5004730100002)(105586002)(76176999)(77156002)(106356001)(50986999)(102836002)(77096005)(15975445007)(33656002)(2656002)(62966003)(10400500002)(2900100001)(106116001)(86362001)(5001770100001)(54356999)(5003600100002)(4001540100001)(66066001)(2950100001)(81156007)(2501003)(76576001)(64706001)(68736005)(74316001)(97736004)(10090945008)(19477635001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB454.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: helsinki.fi does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: helsinki.fi
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Sep 2015 07:30:58.5751 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 98ae7559-10dc-4288-8e2e-4593e62fe3ee
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/wOhAG3f-Tw_mEa6YsrjAGYklrd8>
Cc: Tobias Weigel <weigel@dkrz.de>, "stella@isbn-international.org" <stella@isbn-international.org>, "isabelxiang@hotmail.com" <isabelxiang@hotmail.com>
Subject: Re: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Sep 2015 07:31:25 -0000

Hello Peter,=20

Comments inline below.=20

> -----Original Message-----
> From: Peter Saint-Andre - &yet [mailto:peter@andyet.net]
> Sent: 1. syyskuuta 2015 5:39
> To: Hakala, Juha E <juha.hakala@helsinki.fi>; Melinda Shore
> <melinda.shore@gmail.com>; urn@ietf.org
> Cc: Tobias Weigel <weigel@dkrz.de>; stella@isbn-international.org;
> isabelxiang@hotmail.com
> Subject: Re: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn=
-
> 12.txt
>=20
> > In the second paragraph of chapter 3.3 we say that unless defined for
> > a particular namespace, use of q-, r- and f-components is disallowed.
> >
> > This is OK for q- and r-components, but I am not sure if such
> > limitation is required for F-component, since it has no impact on URN
> > resolution. Moreover, F-component is not namespace specific but
> > depends on file format. It can be added to the URN:ISBN if the
> > identified book is e.g. a PDF document, but not to every URN:ISBN
> > (even if the ISBN identifies an e-book; printed books certainly do not
> > have URI fragments). So it is likely that f-component can never be
> > applied to all URNs in a certain namespace, but it may be possible to
> > apply it to some URNs in most (actionable) namespaces.
>=20
> As I recall, the purpose of the text you have cited was to maintain stric=
t
> compatibilty with RFC 2141 for all existing namespaces; only if a namespa=
ce
> explicitly allows q-, r-, and f-components after 2141bis is published sho=
uld it
> allow and use those components. This is an "opt-in"
> model, if you will, and seems like the safest approach (i.e., do not assu=
me that
> it's OK to add an f-component to an "old", 2141-compatible namespace just
> because 2141bis says that f-components are now allowed).
> This is a form of Postel's Law, I think.

The problem I have with this is that f-components can be added to existing =
URNs by anyone any time after the URN has been minted. For instance, in URN=
:ISBN namespace the use of components is not allowed at the moment, but we =
cannot prevent someone from adding an F-component to URN:ISBN if the identi=
fied book has URI fragments. To "legalize" this, I would revise the URN:ISB=
N namespace registration request and say that f-component can be used if th=
e file format of the identified book allows that. But similar comment could=
 be added to RFC2141bis, and it would apply to all existing URN namespaces =
retrospectively.=20

Keith's problem with components being namespace specific can be avoided if =
the implementers can agree on common syntax for r-component. This requires =
a registry of resolution services and service parameters, and syntax for as=
king for these services. Whether a resolver supports these services or not =
depends on the resolver. Even with the same namespace there will be diversi=
ty in this respect.=20

Within persistent identifier community there is a lot of diversity already =
as regards resolution services and syntax used for requesting those service=
s. Whether Handle, ARK and URN syntaxes can be aligned in the future remain=
s to be seen, but agreeing on how URNs use components could be the first st=
ep down on this road.   =20

>=20
> > The example in the last paragraph of chapter 3.3.1 uses a real ISBN
> > but in wrong (urn:example) namespace. It is better to replace the ISBN
> > with a random NSS such as "bar", because the URN is not actionable and
> > even if it were, the fragment would not be applicable.
>=20
> Yes, we'll fix that to prevent confusion.

Fine.=20
>=20
> > Although libraries' primary intention was to use q-component for
> > passing resolution related information to URN resolvers, I see no
> > problem in using r-component instead to this purpose. IMO it is good
> > design to make a difference between requests to resolvers
> > (r-component) and requests to resources themselves or applications
> > managing them (q-component). Identified resources will become
> > increasingly large and complex (scientific data sets are a good
> > example of this)  and it may be necessary to perform various
> > operations before the resource is ready to be sent to the user.
>=20
> Do you think that the text or example in Section 3.3.1 needs to change in
> order to make that clear?

Well, I would like to change the example a bit:=20

This could perhaps be accomplished by specifying the desired
   metadata field (e.g., "identifier") in the q-component, resulting in
   URNs such as
   "urn:example:foo?operation=3Dsearch&field=3Didentifier".
   However, this primary purpose is not intended to forestall other
   potential uses for q-components.

>=20
> > In 3.3.3 we say that f-component need not be semantically equivalent
> > to the URI fragment (component). IMO URN f-component is never
> > semantically equivalent with URI fragment since f-component does not
> > have a role in identification. We avoid making this difference
> > explicit by saying that f-component is intended to "distinguish
> > integral parts of resources", which is OK to me in spite of being
> > somewhat vague.
>=20
> I think that "constituent parts" might be clearer.

+ 1=20

>=20
> > If we want to be more specific we could say that what is being
> > distinguished are physical (encoded) parts of resources.
> > F-component cannot be applied to logical parts of resources unless
> > they coincide with physical ones. It might be a good idea to be more
> > specific about what f-component does because there is an increasing
> > need within my community (libraries, archives and museums) to identify
> > component parts of resources. If and when we start developing a new
> > standard identifier for logical components of resources (or if we
> > extend existing systems such as NBN in such a way that they do the
> > job) it is important to know precisely what the role of f-component
> > is. The present wording does not make that very clear.
>=20
> I am not well versed in information science, so I am sure how the distinc=
tion
> between logical and physical parts is applied in that field.
> However, from my own limited perspective I hesitate to say that f-compone=
nts
> are necessarily tied to physical representation because even though the
> "preface" and "chapter 3" and "afterword" might be constituent parts of a
> book, in an electronic book those parts are not represented physically as=
 they
> would be in a paper book.

Constituent parts of an electronic book can be represented physically in th=
e (XML/HTML/SGML/...) encoding of the document. Sometimes this kind of enco=
ding matches the physical representation of the printed book; it may also b=
e simpler or more detailed. Over the years there has been a tendency from s=
imple formats such as ASCII documents to more complex, structured document =
formats. Preface, chapters and afterword, perhaps even smaller components o=
f the text can be either identified separately (we use URN:NBN for this pur=
pose) or citing them may be enabled with the encoding of the document.=20
=20
>=20
> > The example in the last paragraph of chapter 3.3.3 uses a real ISBN
> > but in wrong (urn:example) namespace. It is better to replace the ISBN
> > with a random NSS such as "bar". URN:ISBN is actionable (as
> > http://urn.fi/URN:ISBN:978-952-10-7060-0) but urn:example is not. In
> > both cases fragment is not applicable.
>=20
> Yes, we will fix that too.

OK.=20
>=20
> > In chapter 6 (top of page 14) the draft states that "uniqueness
> > constraint means that an identifier within the namespace is never
> > assigned to more than one resource and never reassigned to a different
> > resource". We might consider saying "one resource (as defined in the
> > namespace)".  Every journal article published in e.g.
> > Scientific American has the same ISSN, since in the URN:ISSN namespace
> > "resources" are serials. In SICI (Serial Item and Contribution
> > Identifier) namespace resources are journal issues and articles.
> > URN:NBN could be used for identification of still images within these
> > articles.
>=20
> I see your point. How about this?
>=20
>     The "uniqueness" constraint means that an identifier within the
>     namespace is never assigned to more than one resource and never
>     reassigned to a different resource (for the kind of "resource"
>     identified by URNs assigned within the namespace).

Fine with me!=20

> > In chapter 6.1, the last paragraph of page 16 the draft requires that
> > particular attention should be paid to strings that might imply
> > association with well-known trademarks. More exhaustive formulation
> > would be "... well-known identifier systems and trademarks". In this
> > context we need to be even more concerned about NID strings like
> > "handle" and "doi" than "pepsi".
>=20
> Good point.
>=20
> > In 7.3.1 (Purpose of the URN registration) it is IMO necessary to
> > provide information whether resolution services are or will be
> > available, and if so, what the existing / anticipated services.
> > Registrants might even be able to provide examples for q- and
> > r-component semantics and syntax, even if they are registered
> > elsewhere later.
>=20
> That seems fine.
>=20
> > It might be a good idea to ask the registrants to clarify formal
> > status of the identifier (de jure standard / de facto standard /
> > other) and current / anticipated extent of its use (international /
> > national / local usage).
>=20
> In my experience and (see RFC 6648) the experience of the Internet
> community, it is not especially helpful to draw a distinction between
> standardized and unstandardized identifiers, because unstandardized
> identifiers have a tendency to leak into the space of standardized identi=
fiers.

Still, it would helpful to know the status of the identifier when the names=
pace was registered. Users should be able to see which namespaces are based=
 on standards and which are not. And registrants of non-standard systems co=
uld tell if there is a plan to standardize the identifier in the future.

IMO standardized identifiers such as ISBN are more reliable than other iden=
tifier systems, since the former usually have e.g. a stable user community =
and well formalized identifier assignment rules.    =20

> > Identifiers with statuses "other" and "local usage" should usually
> > have informal than formal namespaces registered for them.
>=20
> Here again, see RFC 6648.
>=20
> > The current scope question (number 4 on the list) is a little bit of a
> > mixed bag as it covers both geographical and organizational issues; it
> > might be better to target scope on various organizational issues only
> > (public / private sector, book trade / libraries, military / civilian
> > use etc.).
>=20
> It's not fully clear to me why some of those dimensions are relevant, but=
 in
> any case I think the answers would emerge from asking about the community
> of use. Thus I propose:
>=20
>         The scope and applicability of the URNs assigned within the
>         namespace; this might include information about the community of
>         use (e.g., a particular nation, industry, technology, or
>         organization), whether the assigned URNs will be used on public
>         networks or private networks, etc.

This is OK for me.=20
=20
> > As regards the current second (later perhaps third) question on the
> > list, I would drop the request for telling why it is preferable to use
> > URN rather than some other technology. IETF does not need to know
> > this. Also asking the registrant to explain why existing URN
> > namespaces are not a good fit sounds a bit negative. I would ask the
> > registrant to describe how the namespace to be registered relates to
> > existing URN namespaces and how the new namespace complements them.
>=20
> I like that more positive focus. How is this?
>=20
>        How the namespace relates to and complements existing URN
>        namespaces, URI schemes, and identifier systems.

Works for me.

All the best,=20

Juha

>=20
> Thanks again for the review.
>=20
> Peter


From nobody Tue Sep  1 03:25:26 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 586E41B3A6F for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 03:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 EAeqlJOL6_wX for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 03:25:24 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D21BD1B3E5F for <urn@ietf.org>; Tue,  1 Sep 2015 03:25:19 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4EA342039E for <urn@ietf.org>; Tue,  1 Sep 2015 06:25:19 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 01 Sep 2015 06:25:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=WneVaBUOfI4HKw0 /tYZOwoWfbOg=; b=WmZ2fkHD8FP1NSCYy+i/WH2EKPGIWyhxjANNYXpxgQbIz4+ 9mWqECJXohk7PTdLd2rmeFtABAqX1IxDwvE0O87gqwPb3lhUpfgSxdVhPkcvulsf hP+J+kNLyn8bYbW20F4cI1/6fhsVVnLyGQClKVEg6Q9ld9eDjkrQoaCQbsnU=
X-Sasl-enc: k1frsOvgMlRnqfkKTx5ONMx8UJgR5OdcWYIWqxViH0yu 1441103119
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id DFD5F680130; Tue,  1 Sep 2015 06:25:18 -0400 (EDT)
To: urn@ietf.org
References: <55804085.5000105@gmail.com> <5584CD07.4050906@gmail.com> <AMSPR07MB4542A8B2C582B8F1772FD0DFAA80@AMSPR07MB454.eurprd07.prod.outlook.com> <55E50FC2.8050106@andyet.net> <AMSPR07MB454C6DB429C2FECD283B24EFA6A0@AMSPR07MB454.eurprd07.prod.outlook.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55E57D0C.5090701@network-heretics.com>
Date: Tue, 1 Sep 2015 06:25:16 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <AMSPR07MB454C6DB429C2FECD283B24EFA6A0@AMSPR07MB454.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/OXYVxbP11oD9RYaH2q9i7U9_eAE>
Subject: Re: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Sep 2015 10:25:25 -0000

On 09/01/2015 03:30 AM, Hakala, Juha E wrote:
>> >As I recall, the purpose of the text you have cited was to maintain strict
>> >compatibilty with RFC 2141 for all existing namespaces; only if a namespace
>> >explicitly allows q-, r-, and f-components after 2141bis is published should it
>> >allow and use those components. This is an "opt-in"
>> >model, if you will, and seems like the safest approach (i.e., do not assume that
>> >it's OK to add an f-component to an "old", 2141-compatible namespace just
>> >because 2141bis says that f-components are now allowed).
>> >This is a form of Postel's Law, I think.
> The problem I have with this is that f-components can be added to existing URNs by anyone any time after the URN has been minted.

The same is also true of q-components (which are only meaningful if the 
resource permits "queries", but can be added by anyone), and 
r-components (since these are requests to the resolution service).

> Keith's problem with components being namespace specific can be avoided if the implementers can agree on common syntax for r-component. This requires a registry of resolution services and service parameters, and syntax for asking for these services. Whether a resolver supports these services or not depends on the resolver. Even with the same namespace there will be diversity in this respect.

agree.

Keith


From nobody Tue Sep  1 19:03:09 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF981AC3D9 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 egbYTTw6SdTQ for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:03:05 -0700 (PDT)
Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB0A11A90C7 for <urn@ietf.org>; Tue,  1 Sep 2015 19:03:05 -0700 (PDT)
Received: by ioii196 with SMTP id i196so4488928ioi.3 for <urn@ietf.org>; Tue, 01 Sep 2015 19:03:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=TkUIZQUdeIQZ50/+TMivDxznBlQmR2kZXVT7Winm7E4=; b=KFbhf6R7D/wZgghsAi4e4Z6mWkVTUoPkEiivshy9XLo89NuGL/iWvKrrwy3WVsD4Cl olMhNR0dzZlLsgMDdeXhxjKX9oyrQzpNft9FqZiNdTJKrm+0zosVFyqraBJJLqq6EmfX e95H2ZubnzPjburWmQ64Yny96WU2VPrt5TNgnfhinEpiiY+m7NGoXKiJkFbRHIEDsAN7 oo9ZbTkqDso3udOp7X6j+8m58Fww01qpCykWSFuxrF+eZrXIqZE0/Rr16JnHo4k0cOWM CkmqmHf+nhh4Q4BmtOepa3oq3qM9S3SDfy1ufS7A7GL2n8JA4EoRDoDgezXNRC2aShXJ sSJA==
X-Gm-Message-State: ALoCoQm6hH7uINDLI0U86Cs3s3F7YgV5gsj+2ncFfgyxrcHXXyCx6foM61B+UAeyELDxtUD7D0UW
X-Received: by 10.107.157.73 with SMTP id g70mr6430622ioe.32.1441159384916; Tue, 01 Sep 2015 19:03:04 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id ir3sm802915igb.12.2015.09.01.19.03.03 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 19:03:04 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, urn@ietf.org
References: <55804085.5000105@gmail.com> <5584CD07.4050906@gmail.com> <AMSPR07MB4542A8B2C582B8F1772FD0DFAA80@AMSPR07MB454.eurprd07.prod.outlook.com> <55E50FC2.8050106@andyet.net> <AMSPR07MB454C6DB429C2FECD283B24EFA6A0@AMSPR07MB454.eurprd07.prod.outlook.com> <55E57D0C.5090701@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E658D6.9020002@andyet.net>
Date: Tue, 1 Sep 2015 20:03:02 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E57D0C.5090701@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/XsZFv17FdEbdScJl2AedIQP-n8s>
Subject: Re: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 02:03:07 -0000

On 9/1/15 4:25 AM, Keith Moore wrote:
> On 09/01/2015 03:30 AM, Hakala, Juha E wrote:
>>> >As I recall, the purpose of the text you have cited was to maintain
>>> strict
>>> >compatibilty with RFC 2141 for all existing namespaces; only if a
>>> namespace
>>> >explicitly allows q-, r-, and f-components after 2141bis is
>>> published should it
>>> >allow and use those components. This is an "opt-in"
>>> >model, if you will, and seems like the safest approach (i.e., do not
>>> assume that
>>> >it's OK to add an f-component to an "old", 2141-compatible namespace
>>> just
>>> >because 2141bis says that f-components are now allowed).
>>> >This is a form of Postel's Law, I think.
>> The problem I have with this is that f-components can be added to
>> existing URNs by anyone any time after the URN has been minted.
>
> The same is also true of q-components (which are only meaningful if the
> resource permits "queries", but can be added by anyone), and
> r-components (since these are requests to the resolution service).
>
>> Keith's problem with components being namespace specific can be
>> avoided if the implementers can agree on common syntax for
>> r-component. This requires a registry of resolution services and
>> service parameters, and syntax for asking for these services. Whether
>> a resolver supports these services or not depends on the resolver.
>> Even with the same namespace there will be diversity in this respect.
>
> agree.

Yes, I see what you're both saying and I'm coming around to your point 
of view.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 19:48:32 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 195D41ACD8B for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 JS3GA0AyJ0r3 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:48:30 -0700 (PDT)
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70FDA1AC39A for <urn@ietf.org>; Tue,  1 Sep 2015 19:48:30 -0700 (PDT)
Received: by igcpb10 with SMTP id pb10so15876479igc.1 for <urn@ietf.org>; Tue, 01 Sep 2015 19:48:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=h92vh6ybWZTcg4WgWUXickdD9v2hJ2b6bNR2Ff1teTs=; b=DbxMGbIY+cIPKyqgSKvN5JxKXR7erc4YxJ024HOA3WlXmiwmvSeYCRIOV0ZS6sqQvN Qm4F5MU3XHTVZw9h9Betp8aTYA01UIZKdZEHE5F8LDyrziZtOHW3e157r/riBf4RP9XU JKUzvz013tQ9SggJ/xX+4eXqu++ZzaEIOBM3brRQr584cDHXnRhvpFiLVojnoAQJo6XT uaNz0pQMUtqjtrRjtu8TZqaOPjWrhRsESs7lR5jHNXf5jfYOD9uUbzmr7TPWETyb5vXU hnCOPKEmA7IdHcHEVUmOGrPwJZDZWxheiPYJ3Vpk8+Yt8TJLTdhEqqAXTaqKM/ChmMTv E6RQ==
X-Gm-Message-State: ALoCoQlEeYBfW8di83HYYmXqcwdvNyxfDiiNoCRQkl4KDo0ROigCX2gazAOKRojOhqT43ch0lO5w
X-Received: by 10.50.176.134 with SMTP id ci6mr1366357igc.10.1441162109655; Tue, 01 Sep 2015 19:48:29 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id h124sm17918129ioh.29.2015.09.01.19.48.28 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 19:48:28 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, John C Klensin <john-ietf@jck.com>
References: <559463C3.3030905@network-heretics.com> <4732B81F609179B87526E501@JcK-HP5.jck.com> <55B71ABF.7090508@network-heretics.com> <55CD57D6.2010603@andyet.net> <0A78DE19CA88E036C0B22104@JcK-HP8200.jck.com> <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E6637C.2060801@andyet.net>
Date: Tue, 1 Sep 2015 20:48:28 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/2cfzfXOxtQU6m0oVtv_x7MkYc_U>
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] encoding, component order, and related issues
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 02:48:32 -0000

On 8/14/15 6:23 PM, Keith Moore wrote:
> I never was convinced of a consensus on this issue (though it's hard
> to tell when there are so few active participants and people
> sometimes take a long time to reply).  But I'm also no longer
> convinced that this is a huge problem.

Keith, would you mind explaining exactly what 'this' refers to above? Do 
you think the lack of consensus is not a huge problem, that the number 
of active participants is not a huge problem, or that ordering the 
components as q-then-r (instead of r-then-q) is not a huge problem?

Peter

>
> Sent from my iPhone
>
>> On Aug 14, 2015, at 12:46 AM, John C Klensin <john-ietf@jck.com>
>> wrote:
>>
>>
>>
>> --On Thursday, August 13, 2015 20:52 -0600 Peter Saint-Andre - &yet
>> <peter@andyet.net> wrote:
>>
>>>> But I also realize that this is at least the third time I've
>>>> tried to fix this, and that the glitches that this causes will
>>>> probably be infrequent.   I also strongly suspect that this
>>>> will come up again in IETF-wide Last Call because I expect the
>>>> web types will want to go over this with a fine-toothed comb.
>>>> So while I still don't understand why you so strongly insist
>>>> that r-component has to follow q-component,
>>>
>>> My sense is that John feels this was a closed issue and that the
>>> WG had reached agreement on q-then-r, so why revisit it?
>>
>> Yes.  I'm happy to reconstruct and explain again the reasons for
>> preferring q-then-r, including why I think the "copying" argument
>> is mostly bogus in practice,  but I'm disinclined to spend
>> everyone's time doing so unless either the co-chairs say "actually
>> there was no conclusion earlier" or someone other than Keith feels
>> strongly about the other order and says so.
>>
>> john
>>
>>
>>


-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 19:48:34 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5301AC39A for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 r3EA4yqpxoXL for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:48:30 -0700 (PDT)
Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41EC1ACD88 for <urn@ietf.org>; Tue,  1 Sep 2015 19:48:30 -0700 (PDT)
Received: by ioii196 with SMTP id i196so5352110ioi.3 for <urn@ietf.org>; Tue, 01 Sep 2015 19:48:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=rDE0FC18VfQ9SQpqxzEgtNi0Nc43kLm3Y2xBrXK4wYY=; b=ghG8T2Jc/q6x9ufESUbvDzjsRDGoHSqVUUz2MCcH/mM53lo2NNAfHm4HXFCT5dM2r2 wO8h7vv4jCGZMfCcpUpd6OPHEhTtAbbekjkzgiNTRz2AFOQlobs3dkewJG7bk3FOecdg 0QXfxwUPWMj2/ex78hhhk1DYdtuFpDSmlbxjAHpDN2KCOY3wRLiDT2SOcW0GvrmJ6v4b 2U97QtPD1IGsaDn4zbIxIk/VmNEBRt6rF25k8EZYaEjU8oKA+zdaJn0UE8zNtA/rQoS1 Z/dIbU5cQAtErSMLdCOZ4faeHEezKMMJJpOcwAF33YBvjQkfG0EF+eCx6hfyQREsXe2r OWig==
X-Gm-Message-State: ALoCoQm83zWg+eaSKNSOMHQGXoUZytiaBwPtQTzZkokxzQVN6vrq+VHAcSGe7EVRG7ks4k5h7h3S
X-Received: by 10.107.29.74 with SMTP id d71mr9694842iod.27.1441162110029; Tue, 01 Sep 2015 19:48:30 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:5569:8ef8:b2cf:292d]) by smtp.googlemail.com with ESMTPSA id 67sm841732iol.7.2015.09.01.19.46.27 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 19:48:29 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, John C Klensin <john-ietf@jck.com>
References: <559463C3.3030905@network-heretics.com> <4732B81F609179B87526E501@JcK-HP5.jck.com> <55B71ABF.7090508@network-heretics.com> <55CD57D6.2010603@andyet.net> <0A78DE19CA88E036C0B22104@JcK-HP8200.jck.com> <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E662DF.2000103@andyet.net>
Date: Tue, 1 Sep 2015 20:45:51 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/JSUnXn-JoJPPBYy6mvTjBKDIU2I>
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] encoding, component order, and related issues
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 02:48:32 -0000

On 8/14/15 6:23 PM, Keith Moore wrote:
> I never was convinced of a consensus on this issue (though it's hard
> to tell when there are so few active participants and people
> sometimes take a long time to reply).  But I'm also no longer
> convinced that this is a huge problem.

Keith, what exactly does 'this' refer to above? Do you think the lack of 
consensus is not a huge problem, that the number of active participants 
is not a huge problem, or that ordering the components as q-then-r 
(instead of r-then-q) is not a huge problem?

Peter

>
> Sent from my iPhone
>
>> On Aug 14, 2015, at 12:46 AM, John C Klensin <john-ietf@jck.com>
>> wrote:
>>
>>
>>
>> --On Thursday, August 13, 2015 20:52 -0600 Peter Saint-Andre - &yet
>> <peter@andyet.net> wrote:
>>
>>>> But I also realize that this is at least the third time I've
>>>> tried to fix this, and that the glitches that this causes will
>>>> probably be infrequent.   I also strongly suspect that this
>>>> will come up again in IETF-wide Last Call because I expect the
>>>> web types will want to go over this with a fine-toothed comb.
>>>> So while I still don't understand why you so strongly insist
>>>> that r-component has to follow q-component,
>>>
>>> My sense is that John feels this was a closed issue and that the
>>> WG had reached agreement on q-then-r, so why revisit it?
>>
>> Yes.  I'm happy to reconstruct and explain again the reasons for
>> preferring q-then-r, including why I think the "copying" argument
>> is mostly bogus in practice,  but I'm disinclined to spend
>> everyone's time doing so unless either the co-chairs say "actually
>> there was no conclusion earlier" or someone other than Keith feels
>> strongly about the other order and says so.
>>
>> john
>>
>>
>>


-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 19:54:39 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6451B3755 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 YB-P3NS_iXA1 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 19:54:36 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97DB21B374F for <urn@ietf.org>; Tue,  1 Sep 2015 19:54:36 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id DEA2D20391 for <urn@ietf.org>; Tue,  1 Sep 2015 22:54:35 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 01 Sep 2015 22:54:35 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=1FJ6ejQdeI4EBkM hUeJN4DlJ7+I=; b=i7rr5c15wEkFSIz2wjnORTLaEbLADXAnFbdPxPrUA4IhKhq v/6N4h8GGQHbqT/nu3+ndHVRm5SDIrfrwrcmAVh/iBUfEnikER0/XCQ5Thk1K7vC PC0tT2Pn6ZS70DqKeOfAdE6J0i37T+hluQCNFkmFKhZqINc3W7zoI7HphMYg=
X-Sasl-enc: RiwMxfnFTuK90DWHEt5jhpgBnH9CnKfRRy3bm6ThRyCM 1441162475
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 81E47680167; Tue,  1 Sep 2015 22:54:35 -0400 (EDT)
To: urn@ietf.org
References: <559463C3.3030905@network-heretics.com> <4732B81F609179B87526E501@JcK-HP5.jck.com> <55B71ABF.7090508@network-heretics.com> <55CD57D6.2010603@andyet.net> <0A78DE19CA88E036C0B22104@JcK-HP8200.jck.com> <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com> <55E662DF.2000103@andyet.net>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55E664E7.6090209@network-heretics.com>
Date: Tue, 1 Sep 2015 22:54:31 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E662DF.2000103@andyet.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/yNHEFgLaBEAnxFAl-qiRQQUkx1M>
Subject: Re: [urn] encoding, component order, and related issues
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 02:54:38 -0000

On 09/01/2015 10:45 PM, Peter Saint-Andre - &yet wrote:
>> I never was convinced of a consensus on this issue (though it's hard
>> to tell when there are so few active participants and people
>> sometimes take a long time to reply).  But I'm also no longer
>> convinced that this is a huge problem.
>
> Keith, what exactly does 'this' refer to above? Do you think the lack 
> of consensus is not a huge problem, that the number of active 
> participants is not a huge problem, or that ordering the components as 
> q-then-r (instead of r-then-q) is not a huge problem?

I am no longer convinced that the inability of a q-component to 
represent '??' without percent-encoding one or both of those characters 
is a huge problem.




From nobody Tue Sep  1 20:20:40 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEDC41ACED7 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 20:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 tKguLeMq5Mvj for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 20:20:36 -0700 (PDT)
Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com [209.85.213.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 736FD1ACF6C for <urn@ietf.org>; Tue,  1 Sep 2015 20:20:36 -0700 (PDT)
Received: by igbni9 with SMTP id ni9so4190571igb.0 for <urn@ietf.org>; Tue, 01 Sep 2015 20:20:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=WL+5EvCF4ZEiZUO0pmJPRWUC2BDEanJv3AxCC5SS+gE=; b=TGmzWUKUniQhz63BJXr/nRD9FQSCancRUh6jVdo0c1InrtmICvjRHUzPwZu8KEKiSc RhBb39xHvZufYFwBPwkKnz8yRzUEhDv44QzJNZPjafPD33U3aDjMAdzfkxmD+Jn6ZuIb zESoMEUn7+mT4SytE5cykzec56zGnoFqnXfGBerrHUJrw3f0xBKyWXX3LHxrro25OJ7F M/tm0BsyTISNuO8yV5t3ScNKnHMgDEfAhMmjwTRHX6SOTNjq7opMFnr/6xMGJLtUCLyz dR96gQb0hW1KGPMjcP71+XMXhEqL0NedXPeySZeqRqK65iSlUVOC2IA7KskzaILpr1HV 0QyQ==
X-Gm-Message-State: ALoCoQkh2Hh8V9yyhmGSDjC5oRVv7EUjo246cn9VhsxWOzFxA/F6eSHamxsbog1EoJsoWylVhmbO
X-Received: by 10.50.66.197 with SMTP id h5mr1199518igt.82.1441164035594; Tue, 01 Sep 2015 20:20:35 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id k70sm3304071iod.11.2015.09.01.20.20.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 20:20:34 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E66B01.2070903@andyet.net>
Date: Tue, 1 Sep 2015 21:20:33 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <559463C3.3030905@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/YKrgR1QS_IEgZuYHnnetv_KS6rI>
Subject: [urn] Section 3 (was: Re:  review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 03:20:39 -0000

Hi Keith,

Thanks very much for the comprehensive review, and especially for the 
suggested text. Because your email is so long, I am going to break my 
reply into smaller chunks.

On 7/1/15 4:03 PM, Keith Moore wrote:

> *1.*  Section 3, first paragraph:
>
> The rationale for the syntax changes made in this document needs some work.
>
> IMO, "Semantic flexibility in the use of URNs within particular
> applications" is not a desirable goal for URNs, or maybe I just
> interpret those words differently than intended.  We need for URNs to be
> interpreted uniformly from one (client) application to the next.
> Perhaps this is just an ambiguity that needs to be cleared up, but the
> need to have client implementations interpret URN components uniformly
> from one client to the next (i.e. interoperability) should inherently
> constrain the semantics of URN components to some degree.

Agreed. The point, as I understand the quoted text, is that members of 
the URN-using community felt the need for greater flexibility in URN 
syntax (compared to RFC 2141) so that URNs could meet the needs of 
existing and future applications - more concretely, this implied the 
ability to use q-components, f-components, and now r-components. So this 
is about 2141 syntax vs. 2141bis syntax, not about "anything goes" 
within URNs.

> (I'll have separate comments for urnbis-semantics.)
>
> CURRENT:
>
> 3.  URN Syntax
>
>     The syntax of URNs as provided in [RFC2141] was defined before the
>     updated specification of URIs in [RFC3986].  In order to ensure
>     consistency with the URI syntax as well as semantic flexibility in
>     the use of URNs within particular applications (see
>     [I-D.ietf-urnbis-semantics-clarif] for further discussion), this
>     specification does the following:
>
>
> RECOMMENDED:
>
> 3.  URN Syntax
>
>     The syntax of URNs as provided in [RFC2141] was defined before the
>     updated specification of URIs in [RFC3986].*In order to facilitate****the use of URNs with parameters similar to URI queries and fragments,****permit parameters influencing URN resolution to be included with****URNs, and ease use of URNs with identifier spaces that **include****the '/' character,*  this specification does the following:

Your proposed text is helpfully concrete, so +1.

> (see also my note below about including "~" and "&" in NSSs)
>
> *2.*  Problems with grammar in section 3
>
> a) The grammar is both ambiguous (in that it permits the same string to
> be parsed in multiple/conflicting ways) and inconsistent with the
> text.   In particular, if "??" separates a q-string from r-string, then
> q-string should not permit "?" to appear twice in succession, and the
> currently specified grammar does.
>
> b) The grammar refers to "q-string" etc. but the text refers to
> "q-component" etc.  I could find no reason for the discrepancy.

Editorial oversight, I think.

> c) Also, the encoding problem for q-component still remains.    See below.
>
> CURRENT:
>
>
>        namestring    = assigned-name
>                        [ "?" q-string ]
>                        [ "??" r-string ]
>                        [ "#" f-string ]
>        assigned-name = "urn" ":" NID ":" NSS
>        NID           = (alphanum) 0*30(ldh) (alphanum)
>        ldh           = alphanum / "-"
>        NSS           = pchar *(pchar / "/")
>        q-string      = pchar *( pchar / "/" / "?" )
>        r-string      = pchar *( pchar / "/" / "?" )
>        f-string      = fragment
>
>     Note: The character "?" can be used without percent-encoding inside
>     q-components, r-components, and f-components.
>
>
> ALTERNATIVE 1 (keep order and separators the same but fix ambiguity):
>
>
>        namestring    = assigned-name
>                        [ "?" q-*component*  ]
>                        [ "??" r-*component*  ]
>                        [ "#" f-*component*  ]
>        assigned-name = "urn" ":" NID ":" NSS
>        NID           = (alphanum) 0*30(ldh) (alphanum)
>        ldh           = alphanum / "-"
>        NSS           = pchar *(pchar / "/")
>        q-*component*    =*pchar *( pchar / "/" / ( "?" ( pchar / "/")))*
>        r-*component*    = pchar *( pchar / "/" / "?" )
>        f-*component*    = fragment
>
>     Note: The character "?" can be used without percent-encoding inside
>     q-components, r-components, and f-components, but two adjacent "?"
>     characters MUST NOT appear inside a q-component.
>
>
> Basically, the change specifies that any "?" in a q-component must be
> followed by either a pchar or a "/".
>
> However, this suggested grammar still has the encoding problem that I
> mentioned earlier:   If q-component is interpreted as a query to be
> attached to a URL (which is what I thought we had agreed to, at least
> for URNs that resolve to URLs), there need to be clear rules for copying
> or converting that q-component text to the URL query text.   The above
> grammar does not permit multiple "?"s to appear adjacent in a
> q-component.   This implies that if there's ever some need to bundle a
> URN with a query that contains "??", the "??" must somehow be encoded so
> that (a) it doesn't violate the URN syntax grammar, and (b) the original
> query string is recovered when bundled with the URL.
>
> Simply assuming percent-encoding doesn't fully specify a solution,
> because while a query that contains "??" could be encoded as %3F%3F, a
> resource might reasonably interpret %3F%3F differently from "??"
>
> This is one reason that I believe it's much simpler, and more likely to
> be implemented correctly, to not constrain the syntax of q-components
> beyond the syntax of RFC 3986 queries.   And that implies either (a)
> putting r-component somewhere else than following q-component [e.g.
> ALTERNATIVE 2 below], or (b) using a different character sequence to
> separate r-component from q-component [e.g. ALTERNATIVE 3].   Then we
> can specify that if a URN with a q-component resolves to a URL, the
> q-component is simply copied to the URL query.
>
> RECOMMENDED ALTERNATIVE 2 (switch order of r-component and q-component):
>
>        namestring    = assigned-name
>                        *[ "??" r-component ] *                       *[ "?" q-component ] *                       [ "#" f-*component*  ]
>        assigned-name = "urn" ":" NID ":" NSS
>        NID           = (alphanum) 0*30(ldh) (alphanum)
>        ldh           = alphanum / "-"
>        NSS           = pchar *(pchar / "/")
>        q-*component*    *= *( pchar / "/" / "?" )*
>        r-*component*    *= pchar *( pchar / "/" )*
>        f-*component*    = fragment
>
>     Note: The character "?" can be used without percent-encoding inside
>     q-components, r-components, and f-components.

I have come to think that placing the r-component first has several 
advantages - it keeps the new URN-specific component syntactically 
separate from the existing URI components, everything after the 
r-component can be passed directly to a standard URL or query-string 
parser (without splitting things up or pulling out this strange new 
r-component thing from the middle), and as you note it enables the first 
character of a q-component to be "?".

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Tue Sep  1 20:21:38 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE861B2A17 for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 20:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 BTb-zfbEBjVm for <urn@ietfa.amsl.com>; Tue,  1 Sep 2015 20:21:36 -0700 (PDT)
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C6961B2A14 for <urn@ietf.org>; Tue,  1 Sep 2015 20:21:36 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so15879860igb.0 for <urn@ietf.org>; Tue, 01 Sep 2015 20:21:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Zj0P3Me2btVcFg6vvDN8A3uMEkbrkEHxByZs3/ZCS20=; b=F8cJaQ9JrgzJr5DlWd7mauUw927I6NiRoTz3IGfI80FVYrlJeCbYH5uqNcY2OBB1ck BnvYem9JBI0XGS4Omvnka1IRXgr7Z64WkujoAsZ+pOpwToe0G1hsBdHU5rYAF6bwl7Wa KRxLnbwslD9nShx+H5wFCsITbV7iXQ5f1WPc8pfWybYOZUD360sLkgQz74YGeT4xrsdB MtvnDZ6VUyuqVPsVlpwV015CtdJkWw39NxQUk29sL2GYjpKiu1B0GG1ganWQmy3b++h2 pSXP7nVWzEJwS68ct/uX/pCLazE45NtuR22X9BHslb5nGZogm4bh8CrbzNrcg5zGwscz U8ig==
X-Gm-Message-State: ALoCoQnJNgOD5iB8zpbrA/O9ddUPTcNrUXL6p1yfGnsnEXuksRmhIVelNOzyTvHu5vNjuE7byjcx
X-Received: by 10.50.117.106 with SMTP id kd10mr1249333igb.39.1441164095318; Tue, 01 Sep 2015 20:21:35 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id m124sm14052857iom.37.2015.09.01.20.21.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2015 20:21:34 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, urn@ietf.org
References: <559463C3.3030905@network-heretics.com> <4732B81F609179B87526E501@JcK-HP5.jck.com> <55B71ABF.7090508@network-heretics.com> <55CD57D6.2010603@andyet.net> <0A78DE19CA88E036C0B22104@JcK-HP8200.jck.com> <A14EB55E-C286-475C-9B1D-59266497D5AC@network-heretics.com> <55E662DF.2000103@andyet.net> <55E664E7.6090209@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E66B3E.6050702@andyet.net>
Date: Tue, 1 Sep 2015 21:21:34 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E664E7.6090209@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/necjJ7r4smDUk2GNHi2xQcZ1vHI>
Subject: Re: [urn] encoding, component order, and related issues
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 03:21:37 -0000

On 9/1/15 8:54 PM, Keith Moore wrote:
> On 09/01/2015 10:45 PM, Peter Saint-Andre - &yet wrote:
>>> I never was convinced of a consensus on this issue (though it's hard
>>> to tell when there are so few active participants and people
>>> sometimes take a long time to reply).  But I'm also no longer
>>> convinced that this is a huge problem.
>>
>> Keith, what exactly does 'this' refer to above? Do you think the lack
>> of consensus is not a huge problem, that the number of active
>> participants is not a huge problem, or that ordering the components as
>> q-then-r (instead of r-then-q) is not a huge problem?
>
> I am no longer convinced that the inability of a q-component to
> represent '??' without percent-encoding one or both of those characters
> is a huge problem.

OK, thanks for the clarification.

Peter



From nobody Wed Sep  2 00:25:37 2015
Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A741B48FA for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 00:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.141
X-Spam-Level: *
X-Spam-Status: No, score=1.141 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, MANGLED_OFF=2.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=0.001] autolearn=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 g-X_mxy343nY for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 00:25:31 -0700 (PDT)
Received: from nordpol.dnb.de (nordpol.dnb.de [193.175.100.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED021B4885 for <urn@ietf.org>; Wed,  2 Sep 2015 00:25:30 -0700 (PDT)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by nordpol.dnb.de (Postfix) with ESMTP id 19CE08ADAA for <urn@ietf.org>; Wed,  2 Sep 2015 09:25:29 +0200 (CEST)
X-AuditID: 0a453fe7-f79136d0000011d7-41-55e6a4686913
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 4C.B0.04567.864A6E55; Wed,  2 Sep 2015 09:25:28 +0200 (CEST)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Wed, 2 Sep 2015 09:25:28 +0200
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Usage of f-, q- and r-components
Thread-Index: AdDIQbL0NAceB7DfRNuZTediDm8aUwAl/SwABxxsXLA=
Date: Wed, 2 Sep 2015 07:25:27 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com>
In-Reply-To: <55B6FF2A.3060001@network-heretics.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.69.104]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA12TbUhTURzGOe7OXdeOna46T0szbwZROJOKRKUktBeSMmqmFdTV3bbhfGl3 E+2DLfOLo7SSDKeVU1GKKOlDaYnELMgIE/NLSRKk6z0jEbPMumcvdvXbn99znuc85xwOLWOG FRraVGTlLUWcmQ1WUsqMbVPxxjaPbkPj7y1Jl89+D0oDu9raZoKywGFlqp43m0p5S8LW40rj 0NseqmQsv6yzNckOHmU5QAiN0Sbc2mhX+GY1Hhy9E+wASppBjwEetLvkRGDQPYAn/+ocQEEH o3V4wkhoOIrFvZ5KrzUMbcSufgflALTIN+FZu9W3JBnXzjyWE0yhOOzxpBIM0R483f9H4duo CuAvH0ZkRAgRrV2Tzd4ZoGjc2fnCO8tQJL7rmZb7WiLc1uPjGEXgj+/m/DwWd3f1+tdvwBMD 1/3zetzu+izzbbwM9zeMURdAhFMS65RYnBKLU2JpBtRNECoUGhK1nF6r1+dp9fxd4Lv+912g ZijdDRANWBW8lefRMXKuVCgvdIN9dBAbAZ82iyg0r1hfbuQE4zGLzcwLbDgMbRUxnMd5NnMB uxJa597pmMh5KtiEElO+qdgmHLNZzG6AaZloVcUTq54rP8Vbin2BbrCCpthIePHhmYMMMnBW voDnS3hLQM2haRbDJy2icZmFN/BlJ0xma0AWfXWkJJIq3kKx8DQppJEKizsF0SFukEmrxGJX ST4USrhCwWTwZ4fBDqdIVQHqzY2G9SRXHYALM5+BA5pIaCNhiKww2ormu2rUMGe9KCyVCCRS swqO7BjXMcslfGHqJ7BbfKIwyJKLV4mf6H9HBn4kmy3xQ2/FKPiAVIzws8VZmeLbhsMrGePk wFbOKj3wdlJEFaD+A6cQqA7AhXEaO2jJ5arPyxPkX8piFCM1J68NOoMPmfRx1TPf2tPUa/qi ai5V1LZOzr5Mm9pR+pMZTTHuqe3+mhiqnU00vPqQ3ZG8dryxvq8y8+j94f4qdczO4aobrtym N72uutXumdu6vb8GXhekF2eFNazq2tzzfII6sj+zrKPpHKrL/lFhW/lVO8RSgpFLXCezCNw/ GPRFgmcEAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/uWA5WOmGgV7znRsvRBtnNbM52NY>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 07:25:35 -0000

Juha, Keith,

On Tuesday, July 28, 2015 6:04 AM, Keith Moore wrote:
=20
> On 07/27/2015 03:57 AM, Hakala, Juha E wrote:
> > Hello,
> >
> > Keith said:
> >
> >> 3. For the sake of interoperability between clients, interpretation of
> >> q-component, r-component, and f-component by client software needs
> to
> >> be consistent across all URNs that can resolve to URLs. The current
> >> text explicitly permits variant uses of these components, without
> >> setting any restrictions on such usage.
> > John responded:
> >
> > I think we have a real conundrum here and I don't know how to resolve i=
t.  I
> also think you are contradicting yourself.  That perception (correct or n=
ot) is a
> symptom of the problem.  On the one hand, we want and need to allow
> significant flexibility to namespace-definers, especially those who are t=
rying
> to overlay URNs on existing, standardized, and extensively-deployed
> namespaces.
> >
> > ---
> >
> > As a namespace-definer who is trying to overlay URNs on a few existing,
> standardized and widely used namespaces my take on this is that the
> problem may not be as severe as John seems to think. It helps - I think -=
 to
> discuss this issue in more practical terms, instead of trying to solve it
> theoretically.
> >
> > F-components look exactly like URI fragments and will be treated like
> them. Web browsers should never send them to URN resolvers, and if they
> do, resolvers should ignore the f-component. It will only be applied to t=
he
> identified and retrieved document.

+1

> > Things get more challenging with q-component. Let's have a practical
> example: a user wants bibliographic metadata in Dublin Core format of the
> book which has ISBN 978-3-598-24287-8.
> >
> > If the request is to be sent directly to the target database, then the =
syntax
> and semantics of the q-component will be dictated by the search protocol
> supported by the database. In this case the request can be sent to e.g.
> Library of Congress Online Catalog (http://catalog.loc.gov/). For machine=
 to
> machine interaction, it supports Z39.50 and SRU search protocols. In this=
 case
> SRU is appropriate, so the URN with q-component will look like this:
> >
> > urn:isbn:978-3-598-24287-
> 8?version=3D1.1&operation=3DsearchRetrieve&query=3D9783598242878&maximu
> mRecords=3D1&recordSchema=3Ddc
>=20
> This looks odd to me.  I understand the q-component to be reserved for
> information to be transmitted to the resource and interpreted by that
> resource.   So a q-component wouldn't normally be applicable to a paper
> book.   It looks to me like the parameters listed above would be more
> appropriate for r-component.
>=20
> >
> > The q-component looks complicated to those who do not know SRU. There
> is a lot that needs to be told to the bibliographic database which acts a=
s the
> target system: the service we are asking for, search term, number of reco=
rds
> to be retrieved and metadata format to be used. Luckily SRU search reques=
ts
> are machine generated; users should not see them at all.
> >
> > A URN resolver receiving this should know one or more SRU servers to
> which the send the request. When the LoC server location is added as SRU
> base URL to the q component, the URI becomes:
> >
> >
> http://z3950.loc.gov:7090/voyager?version=3D1.1&operation=3DsearchRetriev=
e&
> query=3D9783598242878&maximumRecords=3D1&recordSchema=3Ddc
>=20
> In contrast with the above example, this does not look odd to me, as
> this is a URL for a request to a resolution service.  There's nothing
> wrong with a resolution server accepting parameters via HTTP query
> string.   But a client using such a service for URN resolution needs to
> know how to map the r-component of the URN for which it is seeking
> information, onto that resolution service's protocol.   If the
> resolution service defined its protocol in a way to make this work, the
> client might simply copy the r-component from the URN directly to the
> query component of the HTTP URL used to query the resolution service,
> perhaps adding the assigned portion of the URN as an additional query
> parameter.
>=20
> To make this more concrete, the original URN might be:
>=20
> urn:isbn:978-3-598-24287-
> 8??request=3DI2C&protocol=3DSRU&maximumRecords=3D1&recordSchema=3Ddc

Yes, that's  my view, too. Although I'd drop the "protocol" and "maximimumR=
ecords" part and keep it to=20

urn:isbn:978-3-598-24287-7??request=3DI2C&recordSchema=3Ddc

since it's up to the URN resolver to decide how it will communicate with th=
e bibliographic information system (perhaps even using Z39.50).

> and the client might need to translate this to a URL like the following
> one to request the needed information:
>=20
> http://z3950.loc.gov:7090/voyager?version=3D1.1&operation=3DsearchRetriev=
e&
> query=3D9783598242878&maximumRecords=3D1&recordSchema=3Ddc
>=20
> Note that this requires some registry or other means by which
> r-component parameters that are widely used across different URN
> namespaces, need to be interpreted by the client (like "request" and
> "protocol" in the example above) and translated into whatever the
> resolution service needs, are distinguished from those parameters that
> are simply passed through to the resolution protocol.

Right.

> (Ideally, the URN would not need to specify any protocol-specific
> parameters, as this makes the URN dependent on a specific resolution
> protocol that is likely to change over time.

Yes, that's why I think that the r-component should not say anything at all=
 about which protocol to use...

> But I think it will take
> awhile to standardize r-component parameters and there will always be
> some need to specify parameters that are specific to a particular
> namespace or resolution service.)

Right, but that should be kept to a minimum.

> > The URN resolver may be aware of 1-n SRU servers, which can be fulfil t=
he
> user's demand. But the resolver does not need to know how to construct
> SRU search request; that has already been done on the fly by the OPAC or
> other bibliographic system the customer is using. Standard based queries =
/
> resulting q-components may look complicated but it is not hard for
> applications to create and understand them. It is far more difficult to d=
eal
> with cases when there is no standard search API and "screen scraping" has=
 to
> be used to create a search URI.

This is where we differ: In my opinion the resolver needs to know what "I2C=
" means, whom to ask for the URC and how to build the request. The reason i=
s that if the client already mandates what protocol to use we're in for ser=
ious problems when in future there is no bibiliographic lookup service that=
 supports SRU (or Z39.50) because everyone has moved on to BLOAT (Bibliogra=
phic Lookup Online Access Terminal) or whatever protocol is en vogue at tha=
t time. If URNs with r-components are intended to be persistent, they must =
only say _what_ is to be done, but not _how_.

> > Generally, q-component needs to be whatever the target system requires
> it to be. So if URNBIS says don't do <foo> in the q-component, then - if =
<foo>
> is something required by e.g. the SRU protocol which will be widely used =
to
> deliver one of the most important resolution services, the implementers w=
ill
> do <foo> in any case at least if there is no viable workaround such as us=
ing
> the r-component.
> >
> > Due to the existence of various standard APIs it should be easy to use =
r-
> component to deliver I2C service. All it takes is that the URN resolver c=
an
> migrate the r-component into appropriate URI such as SRU search, using
> default values for service related parameters if the user has not supplie=
d
> them.  For instance, using "I2C" from RFC 2483 as mnemonic for service "U=
RI
> to URC" and SRU syntax to require Dublin Core metadata, we get URN
> >
> > urn:isbn:978-3-598-24287-8??s=3DI2C&recordSchema=3Ddc

OK, so we arrived at the same solution here. That's good!

> > The resolver would need to know how to migrate this into a search URI
> supported by an appropriate target system. It may be SRU server,
> OpenSearch server, or something else. For the r-component above, Library
> of Congress Online Catalog would be fine. But if the user wants preservat=
ion
> metadata about the resource with r-component like this
> >
> > urn:isbn:978-3-598-24287-8??s=3DI2C&recordSchema=3Dpremis
> >
> > digital preservation system should be chosen instead of a bibliographic
> database. As a rule the latter do not contain preservation metadata in an=
y
> format, and do not support Premis which is the de facto format used for t=
his
> purpose (see http://www.loc.gov/standards/premis/). A user might also
> request that the identified resource is deleted from digital archive. The=
n SRU
> would not be the right protocol; instead, for instance French standard
> MEDONA (Mod=E9lisation des =E9changes de donn=E9es pour l'archivage) shou=
ld
> be used.
> >
> > In order to make r-component truly useful we need a service registry wh=
ich
> can be easily maintained. New services and service parameters are emergin=
g
> as a result of implementation of digital preservation systems and other n=
ew
> tools needed for management of digital resources. It would be impractical=
 to
> revise RFC 2483 and its successors each time something new (revised
> metadata format, novel functionality, etc.) is introduced.
> >
> > IMO the usefulness of r-component depends on the availability of
> standard-based APIs for relevant services. Resolving a URN should not be
> complex or error prone, and therefore it is important to be able to map t=
he
> service request and parameters in the r-component accurately into a URI. =
In
> a standard based environment such mappings should be relatively simple
> and stable; in a non-standardized environment it is likely to be neither.=
 Even
> finding out what services are supported in the target system can be
> complicated, depending on the quality of the documentation provided.
> >
> > With q-component it will be easier to use non-standardized functionalit=
y
> supported by digital asset management systems than with r-component. All
> that is needed is to cut and paste the relevant parts of URIs from the ta=
rget
> system to the client application. The downside is that URIs used for e.g.
> searching non-standard bibliographic databases tend to change. So althoug=
h
> the identifier (NSS part of the URN) of a resource is stable, the q-compo=
nent
> of the URI may change when the target system is updated.
> Your latter two URN examples are also using the r-component in a way
> that is consistent with my expectations.
>=20
> I get the impression that you envision using q-component for parameters
> that are specific to a particular resolution service, and r-component
> for resolution parameters that are standardized.   I also understand the
> need to distinguish between the two kinds of parameters, but I've
> assumed that both kinds of parameter would appear in r-component, with a
> registry or some sort of parameter naming convention used to distinguish
> between "generic" parameters that might need to be mapped into
> protocol-specific requests, and "protocol-specific" r-component
> parameters that would be passed directly to the resolution protocol.
>=20
> And I certainly agree with the need for a registry for r-component
> parameter names, and for standard resolution protocols.
>=20
> However, I want to reserve q-component to be strictly for parameters to
> be passed to a resource (for example, as "queries") and interpreted by
> that resource.   I believe it's important to retain the capability to
> use URNs to identify network-accessible resources that accept input
> parameters, and to associate those input parameters with the URN.

+1

[snip google example]

> I think it's important to reserve q-component for this purpose not only
> so that network-accessible resources that accept "queries" can have
> those queries included in a URN, but also, more generally, that "?" will
> behave in a way that is more-or-less consistent with familiar usage.

Yes.

Best,

Lars


*** Lesen. H=F6ren. Wissen. Deutsche Nationalbibliothek ***=20
--=20
Dr. Lars G. Svensson
Deutsche Nationalbibliothek
Informationsinfrastruktur und Bestanderhaltung
Adickesallee 1
D-60322 Frankfurt am Main
Telefon: +49-69-1525-1752
Telefax: +49-69-1525-1799
mailto:l.svensson@dnb.de=20
http://www.dnb.de


=20


From nobody Wed Sep  2 00:25:39 2015
Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DA21B490A for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 00:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 bNWKd88znzxu for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 00:25:30 -0700 (PDT)
Received: from nordpol.dnb.de (nordpol.dnb.de [193.175.100.40]) by ietfa.amsl.com (Postfix) with ESMTP id 80BFC1B48D8 for <urn@ietf.org>; Wed,  2 Sep 2015 00:25:30 -0700 (PDT)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by nordpol.dnb.de (Postfix) with ESMTP id 34B7D8ADE7; Wed,  2 Sep 2015 09:25:29 +0200 (CEST)
X-AuditID: 0a453fe7-f79136d0000011d7-42-55e6a468a61e
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 5C.B0.04567.864A6E55; Wed,  2 Sep 2015 09:25:29 +0200 (CEST)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Wed, 2 Sep 2015 09:25:28 +0200
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
Thread-Index: AQHQ5FVsqxlLif2aP0aKvwefw+Mr8J4o1uJA
Date: Wed, 2 Sep 2015 07:25:27 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D0BFAA8@dnbf-ex1.AD.DDB.DE>
References: <55804085.5000105@gmail.com> <5584CD07.4050906@gmail.com> <AMSPR07MB4542A8B2C582B8F1772FD0DFAA80@AMSPR07MB454.eurprd07.prod.outlook.com> <24637769D123E644A105A0AF0E1F92EF010D0A868F@dnbf-ex1.AD.DDB.DE> <55E4FF08.1000200@andyet.net>
In-Reply-To: <55E4FF08.1000200@andyet.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.69.104]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA12TWUwTQRzGMz2X2qlDyzFWMbohPkBAMD6QaLyiRqPBA2qMkejWXdvGcnW7 RNTE+0FUouJRGhXQRsQjErxQCYn1iJAIBogXKImFkloNRjTqg+JOt8XFt39+3//75pudLKU0 9mvNlKPIzbmKGCet0al0S+Z/z3D4gpasJze0Oe0fHitzTu3/oligWNbR91K7zOf7pVit2KCb y3JORxnnmjlvs87ef2hAXVIzaftzT7tmD/htqgBxFEazcdtFj0qak/CL9zc0FUBHGdFjgI82 HIwIRnQH4JFRSwXQUhqUhofthCagXPz0Y0DcoCgTWot76hdKOA/fe3sTSPMs/O1ri5asqFAq DgbnEgzRClxxolspHfQTYM/DQTUR4sTw86dHI16AUnBjY6eSzEqUjJuCP9RSS4R9LRLHKBGH An+ifDq+19wa3c/Cwx010TkdX6oLK6WD43Fb9YDqGEj0ymK9MotXZvHKLLVAdQUY+EJbdibD ZrKsNZPlmoD0EkPNoLJrsR8gCtB6eM0atBjVTBlfXugHqygFnQif1YrIYC1my+0Mb9/kEpwc TydAw0URwzFsFZzb6KnQ/SdgMSaPUV7gSxxbHMUCv0lwOf0AU0rRqs8gVpYp38G5iqVAP5hM qehkePzB3nwjsjFubhvHlXCumLqeomgMn1wQjfEuzsZt3+pwumOy6KsiJZFciRSaDneTQma5 8H8nBRXnByspvVjsHMmHfAlTyDts0WwTrPeKVB+jkdwUeJrkJsXg+Mx2kGdOhgIJQ2TDLhSN dTUnwfXpojBRJpBI8zTYu3TQYpwk4+NTP4Ll4hOZIE0+vF78n/51NMIQOWxCFEYqToH3ScXE KPs/a6X4tgnwzJJBcmE345ZfeBEpoo/R6IXnEJgUg+PjzHuAL18d2hlWvR5aUzAisL9v9VTW hjnUYLjvOTuUdtuXu7yq93NW2VU23J2w4FU1SqtPbTsyGkCcQbNu9MW+y4Fi211ra/Ond766 jK7P+W/CpuO9XT05uwLX2x6WVnbOsGruzg+dLJ0ZDPWdPbDqcPpwqc+D2Thb1o6NQu/Ogke1 tIq3M9lpShfP/AVs5LVAcgQAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/cxKNPhCH1OKMZKk6NkJheu9xZQs>
Subject: Re: [urn] Fwd: Fwd: I-D Action: draft-ietf-urnbis-rfc2141bis-urn-12.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 07:25:35 -0000

Peter,

On Tuesday, September 01, 2015 3:28 AM, Peter Saint-Andre - &yet wrote:
=20
> Hi Lars, thanks for the feedback and my continued apologies for the
> delayed reply.

No need to apologise given how long I often need before I get to review the=
 documents...

> On 7/5/15 1:37 PM, Svensson, Lars wrote:
> > Melinda et al.;
> >
> > My comments are even more minor than Juha's:
> >
> > 1) Introduction The first paragraph discusses the difference between
> > resource identifiers and abstract designators. In order to avoid
> > confusion we should make it clear that "resource" is meant as
> > "internet resource", since also abstract designators do identify
> > resources (but not internet resources). This comment also applies to
> > the document's abstract.
>=20
> I'm not sure. RFC 3986 says that "a resource is not necessarily
> accessible via the Internet", so limiting the scope of resources in the
> URN context to Internet resources seems perhaps incorrect. On the other
> hand, RFC 1737 does say that a URN is an "Internet resource identifier".
> I would slightly favor leaving the text as-is for now.

Is OK with me, particularly if we use RFC 3986 terminology as stated below.

> > 2) Terminology The first paragraph mentions that important terms are
> > taken from RFC 3986. I think it would help the interpretation if we
> > could list exactly what terms are to be interpreted in the RFC 3986
> > fashion (e. g. "resource").
>=20
> That's a good point. I might suggest...
>=20
> OLD
>=20
>     Several important terms used in this document, including some
>     "normalization" operations that are not part of the Unicode Standard
>     [UNICODE], are defined in the URI specification [RFC3986].
>=20
> NEW
>=20
>     Because this document attempts to harmonize the definition of URNs
>     with that of URIs, it borrows a number of important rules (such as
>     "normalization" operations that are not part of the Unicode Standard
>     [UNICODE]) from the URI specification [RFC3986], and also uses
>     several key terms (such as "resource" and "identifier") in
>     effectively the sense as the URI specification.
>=20
> I don't exactly want to say that some of these key terms are "defined"
> in RFC 3986 because I don't consider ostensive definition to be
> sufficient for protocol specifications.

Works for me.

> > 3) URN syntax The third paragraph discusses "rules not defined here"
> > and mentions "path-absolute" and "query", but I cannot find that
> > those two rules are used in the ABNF.
>=20
> Good catch. Those were used in a previous version, but are no longer used=
.
>=20
> > 4) Appendix A, =A7A.6 This section says that the use of p-components is
> > not allowed unless the registration explicitly says how. There are no
> > p-components any more.
>=20
> Correct. Will fix.

Thanks,

Lars


*** Lesen. H=F6ren. Wissen. Deutsche Nationalbibliothek ***=20
--=20
Dr. Lars G. Svensson
Deutsche Nationalbibliothek
Informationsinfrastruktur und Bestanderhaltung
Adickesallee 1
D-60322 Frankfurt am Main
Telefon: +49-69-1525-1752
Telefax: +49-69-1525-1799
mailto:l.svensson@dnb.de=20
http://www.dnb.de





From nobody Wed Sep  2 10:53:11 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA261B4D50 for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 10:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.401
X-Spam-Level: **
X-Spam-Status: No, score=2.401 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MANGLED_OFF=2.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 ncxV0ZXx25sN for <urn@ietfa.amsl.com>; Wed,  2 Sep 2015 10:53:08 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FBDC1B4CCD for <urn@ietf.org>; Wed,  2 Sep 2015 10:53:08 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 95BEF203F5 for <urn@ietf.org>; Wed,  2 Sep 2015 13:53:07 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 02 Sep 2015 13:53:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=JBMk+0DjDdljMr21PMmSx+zCWA0=; b=r0pcn bmAeM6Lsnkz+AKpuLfnGArPrX+fdTPeyswvUspd4La0FIRbtOq/MAWzLxAwWXpgH iv5hFTGQ+vo++jxMHmqbBT5c4KiRyOPuMymEsfVmiMhk8JTg9az8bMYW5yz7HwbJ wV5AqVrdt8PHTGJ1XnYMOnPAdCjlxpLEZKuIZM=
X-Sasl-enc: RqtijRr3Fk10IACA19simGdgfcUricxqx+wARRF3PPdV 1441216387
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 31786C00021; Wed,  2 Sep 2015 13:53:07 -0400 (EDT)
To: urn@ietf.org
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55E7377D.50702@network-heretics.com>
Date: Wed, 2 Sep 2015 13:53:01 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE>
Content-Type: multipart/alternative; boundary="------------060409050009000800090502"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/NPb6TtDfxRH79vzlcXkjF3YPBCI>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Sep 2015 17:53:10 -0000

This is a multi-part message in MIME format.
--------------060409050009000800090502
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 09/02/2015 03:25 AM, Svensson, Lars wrote:
> This is where we differ: In my opinion the resolver needs to know what "I2C" means, whom to ask for the URC and how to build the request. The reason is that if the client already mandates what protocol to use we're in for serious problems when in future there is no bibiliographic lookup service that supports SRU (or Z39.50) because everyone has moved on to BLOAT (Bibliographic Lookup Online Access Terminal) or whatever protocol is en vogue at that time. If URNs with r-components are intended to be persistent, they must only say_what_  is to be done, but not_how_.

I think we should make clear that only the "assigned portion" of a URN 
can be expected to be persistent.   If an f-component, q-component, 
and/or r-component is included with the URN, the entire URN can no 
longer expected to be persistent, but the "assigned portion" is still 
expected to be persistent.

Similarly, just because a URN appears with an f-component, q-component, 
or r-component doesn't mean that applications processing that URN are 
expected to use all of those components in every situation.   This may 
vary due to both the context in which a URN appears and also according 
to the user interface.   For instance:

  * A URN appears in the HREF parameter of an A element in an HTML
    document.   If the user "clicks" on that link, the expectation is
    that the document referred to by the URN should be loaded and
    presented to the user, who can then interact with that resource if
    it supports interaction.
      o If the r-component of that URN doesn't specify any particular
        operation, the client should probably try to present the
        document referred to by the URN to the user, and whether that
        happens by the client issuing a I2L request to the resolution
        service and selecting from among the links returned, or by the
        client issuing an I2R request to the resolution service, this is
        an implementation detail.  The client would also supply any
        q-component to the resource, and process the returned content
        according to any f-component supplied with the URN.
      o If the client were to learn that the resource requires some sort
        of authentication or purchase, the client might instead present
        a dialog which permits the user to authenticate and/or authorize
        such a purchase, before trying to present the actual resource.  
        This is reasonable behavior for the client in this case because
        the expectation is that the user can interact with the client
        and the resource.
      o However if the r-component of the URN explicitly specifies the
        I2C operation, the citation of the resource (perhaps further
        selected by additional parts of the r-component) should be
        presented to the user.
      o Even if the URN supplies an r-component that specifies default
        behavior for "clicking" on the link, the client might permit the
        user to "right click" on the link and explicitly request a
        citation, links, related resources, revision history, etc.   In
        that case the client would ignore any {f,q,r}-components
        supplied with the URN.
  * A URN appears in the SRC parameter of an IMG element in an HTML
    document.   In this case, the client will attempt to obtain the
    resource content (which it assumes to be an image) and automatically
    display it.   Any r-component that specifies other than I2R should
    probably be ignored, but an f-component or q-component would be used
    if supplied.   The client could still permit "right click" on the
    image and allow the user to obtain citations etc. from the assigned
    portion of the URN.




--------------060409050009000800090502
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 09/02/2015 03:25 AM, Svensson, Lars
      wrote:<br>
    </div>
    <blockquote
      cite="mid:24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE"
      type="cite">
      <pre wrap="">This is where we differ: In my opinion the resolver needs to know what "I2C" means, whom to ask for the URC and how to build the request. The reason is that if the client already mandates what protocol to use we're in for serious problems when in future there is no bibiliographic lookup service that supports SRU (or Z39.50) because everyone has moved on to BLOAT (Bibliographic Lookup Online Access Terminal) or whatever protocol is en vogue at that time. If URNs with r-components are intended to be persistent, they must only say <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>what<span class="moz-txt-tag">_</span></span> is to be done, but not <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>how<span class="moz-txt-tag">_</span></span>.</pre>
    </blockquote>
    <br>
    I think we should make clear that only the "assigned portion" of a
    URN can be expected to be persistent.   If an f-component,
    q-component, and/or r-component is included with the URN, the entire
    URN can no longer expected to be persistent, but the "assigned
    portion" is still expected to be persistent.<br>
    <br>
    Similarly, just because a URN appears with an f-component,
    q-component, or r-component doesn't mean that applications
    processing that URN are expected to use all of those components in
    every situation.   This may vary due to both the context in which a
    URN appears and also according to the user interface.   For
    instance:<br>
    <br>
    <ul>
      <li>A URN appears in the HREF parameter of an A element in an HTML
        document.   If the user "clicks" on that link, the expectation
        is that the document referred to by the URN should be loaded and
        presented to the user, who can then interact with that resource
        if it supports interaction.    </li>
      <ul>
        <li>If the r-component of that URN doesn't specify any
          particular operation, the client should probably try to
          present the document referred to by the URN to the user, and
          whether that happens by the client issuing a I2L request to
          the resolution service and selecting from among the links
          returned, or by the client issuing an I2R request to the
          resolution service, this is an implementation detail.  The
          client would also supply any q-component to the resource, and
          process the returned content according to any f-component
          supplied with the URN.<br>
        </li>
        <li>If the client were to learn that the resource requires some
          sort of authentication or purchase, the client might instead
          present a dialog which permits the user to authenticate and/or
          authorize such a purchase, before trying to present the actual
          resource.   This is reasonable behavior for the client in this
          case because the expectation is that the user can interact
          with the client and the resource.<br>
        </li>
        <li>However if the r-component of the URN explicitly specifies
          the I2C operation, the citation of the resource (perhaps
          further selected by additional parts of the r-component)
          should be presented to the user.   </li>
        <li>Even if the URN supplies an r-component that specifies
          default behavior for "clicking" on the link, the client might
          permit the user to "right click" on the link and explicitly
          request a citation, links, related resources, revision
          history, etc.   In that case the client would ignore any
          {f,q,r}-components supplied with the URN.<br>
        </li>
      </ul>
      <li>A URN appears in the SRC parameter of an IMG element in an
        HTML document.   In this case, the client will attempt to obtain
        the resource content (which it assumes to be an image) and
        automatically display it.   Any r-component that specifies other
        than I2R should probably be ignored, but an f-component or
        q-component would be used if supplied.   The client could still
        permit "right click" on the image and allow the user to obtain
        citations etc. from the assigned portion of the URN.</li>
    </ul>
    <p><br>
      <br>
    </p>
  </body>
</html>

--------------060409050009000800090502--


From nobody Thu Sep  3 16:32:34 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFE71A895C for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 16:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.301
X-Spam-Level: 
X-Spam-Status: No, score=-0.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_OFF=2.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 iUpY07bPPZBf for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 16:32:33 -0700 (PDT)
Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB3881A020A for <urn@ietf.org>; Thu,  3 Sep 2015 16:32:32 -0700 (PDT)
Received: by igbni9 with SMTP id ni9so952239igb.0 for <urn@ietf.org>; Thu, 03 Sep 2015 16:32:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ZCDcC2IUazG82Gq6XRzwA57LD3BGq8MiTn7hXjuaqto=; b=FE5zJPAkX9n4Qezr/+F/nBdhqkfK5p+sBBF32N9sdAvNaoECpkmiy3sr5R3G8EBXd+ EM2reDW5lnT9qIpa+MQ802VDIfQjpxn9wPMw0ZyqKo/xxgZaEGI8a0ohlqLIC3MA/oaL immss/I9SXjZCYW8xLXaUacEnKLCVeZXT9lHGt+1uF97u7qoGhDzdF9yeIV4vpQPWRYj O2IJhF0WiNk8NZRFzSbVUCjac5pxD8yfs2nWb4cnrmjK2lFSHjbgQyymTTLniS1l+xNj gXR+tVaoshJ7SzUHogxnyvGMwFCOvlw/CKQbB4l1P9xKvgENtsTqVxAApfijYZsAe4/I y2ew==
X-Gm-Message-State: ALoCoQlPd+8Wv4HV0y575U8usyqc0wrbTXxv5Mf/X+IQe0d/+JcpyvC5S9aVm8mfjNMrudzyCvuY
X-Received: by 10.50.40.105 with SMTP id w9mr1294095igk.55.1441323152241; Thu, 03 Sep 2015 16:32:32 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id bd7sm395090igb.19.2015.09.03.16.32.30 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 16:32:31 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, urn@ietf.org
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE> <55E7377D.50702@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8D88D.7050206@andyet.net>
Date: Thu, 3 Sep 2015 17:32:29 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E7377D.50702@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/wqVKULwb9JxtYTTkAHrqwXX-R8k>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Sep 2015 23:32:34 -0000

On 9/2/15 11:53 AM, Keith Moore wrote:
> On 09/02/2015 03:25 AM, Svensson, Lars wrote:
>> This is where we differ: In my opinion the resolver needs to know what "I2C" means, whom to ask for the URC and how to build the request. The reason is that if the client already mandates what protocol to use we're in for serious problems when in future there is no bibiliographic lookup service that supports SRU (or Z39.50) because everyone has moved on to BLOAT (Bibliographic Lookup Online Access Terminal) or whatever protocol is en vogue at that time. If URNs with r-components are intended to be persistent, they must only say_what_  is to be done, but not_how_.
>
> I think we should make clear that only the "assigned portion" of a URN
> can be expected to be persistent.   If an f-component, q-component,
> and/or r-component is included with the URN, the entire URN can no
> longer expected to be persistent, but the "assigned portion" is still
> expected to be persistent.

Agreed.

Peter



From nobody Thu Sep  3 16:53:41 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3A0B1B30AD for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 16:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 6iN1VPJpdT4w for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 16:53:37 -0700 (PDT)
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com [209.85.213.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC2DF1B2A02 for <urn@ietf.org>; Thu,  3 Sep 2015 16:53:36 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so1112810igb.0 for <urn@ietf.org>; Thu, 03 Sep 2015 16:53:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=3PJqMH0OpJZwwGyeSa6K21VBLXOkTlj6vcY7tdOCNGI=; b=Ix01FYzYjKRJ6iR2KcVznlsx0jeUBLbH/mOhx7YYXTtoyMpscFTuwYf1x9K44Yfrvu lNfR3sJdrsFST4EE2fbm1iRSxDgrRNPQYJOdKzZIjaameq7NU/dn3lsFL3jX0YkTRoGJ duw4BF5AcY38fTz3pDzwq2lvuVtd4PMAgObVQuwgaYhm8in+CFwm6n3Kji6SHGSBZQD0 ztffEwfQ2065gLHqCOomUEFkvLh5bJXpX0NEAa+7o6+rrYv96jokQ5v1SV6VO8tp5aZP 3vHOCXz+UT45PxilIL9xmQNMrp5rNwo4DLCdvhgidWTRLxaaGE6AKutkiPTbEAawNJ1i +xeg==
X-Gm-Message-State: ALoCoQnwxGabd5yQPGha9X5AYR0DVaSIqYHGCeY4MOc8smg1oa8a47anrsp0ijRjB+JTNNXi9bzf
X-Received: by 10.50.43.170 with SMTP id x10mr1535823igl.12.1441324416013; Thu, 03 Sep 2015 16:53:36 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id c97sm341766ioj.41.2015.09.03.16.53.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 16:53:35 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8DD7E.1020309@andyet.net>
Date: Thu, 3 Sep 2015 17:53:34 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <559463C3.3030905@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/5lYzQN52n0Aqc4KvxU65XS_8ed8>
Subject: [urn] Section 3.2: NSS (was: Re:  review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Sep 2015 23:53:40 -0000

Here is the second installment of my reply...

On 7/1/15 4:03 PM, Keith Moore wrote:

> *3.*  Section 3.2, 2nd paragraph:
>
> This document modifies the syntax of the NSS to allow the following
> characters: "/", "~", and "&".
>
>
> Are there reasons to permit "~" and "&", and have we sufficiently
> investigated the implications of doing so?

I think the idea was: is there a reason to *not* permit "~" and "&"? 
This is an artifact of trying to align with the URI spec as much as 
possible, in this case by reusing the 'pchar' rule.

>  I am wondering whether
> this will break parsers for no good reason.  I have seen URLs which
> "~" was encoded to "%7E" (even though this shouldn't be necessary)
> and "&" to "%26" (which also shouldn't be necessary except in a query
> that uses HTML FORM encoding for HTTP GET).

It's not our job to design around broken parsers. That way lies madness.

> *4. * This document needs to clarify (somewhere) that the change to
> the URN grammar DOES NOT change encoding rules for existing URN
> namespaces, if there are existing namespaces that are used outside of
> the URN context, and in which use any of "/", "~", or "&" are allowed
> to appear in those names in native form.

Although I have no objections to including such text, the universe of 
URN namespaces is small enough that we could determine if any such 
namespaces exist:

http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml

> *5.*  Also, something that I think could possibly use a bit more
> explicit attention in the registration section and perhaps elsewhere:
> In some sense there are two kinds of URN namespaces: those that exist
>  solely as URNs, and identifier spaces that exist independently of
> URNs.   The latter kind of identifier has a "native" form and a URN
> form, and its URN namespace registration should specify an algorithm
> for converting from native form to URN form.   Ideally this algorithm
>  produces a distinguished form of its input when converting it to URN
>  format - this makes it easier to build generic services that answer
>  queries for arbitrary URNs.   If the algorithm is just to use
> percent-encoding, that's fine, but IMO this should be explicitly
> specified in the namespace registration. I don't think we should
> unilaterally impose this algorithm for all identifier spaces.

But do you think we should recommend it? This feels like one of those 
situations where the creativity of the namespace registrant could lead 
to bad results.

> Client software that just handles URNs doesn't need to worry about
> this.   Such software should always see the URN form of such
> identifiers and should be able to handle all URNs in a uniform
> manner.   However, software that allows such identifiers to be input
> directly (e.g. without the urn:xxx: prefix) and converts those
> identifiers to URNs, needs to be aware of the conversion rules for
> each URN namespace that it accepts.

Aren't we verging close to violation of the principle of uniformity 
here? I'd at least prefer to say that you SHOULD use percent-encoding 
(unless you have good reason not to, and please document your reasons, 
such as having an existing encoding rule as you describe below).

> Anyway, I think it would help to have some background text early in
> the document that explains this, and one or two specific items in the
>  registration template

That does sound helpful.

> (I can try to come up with text if desired, but I didn't want to
> delay this review any longer.)
>
> (Also, much of this item is also reflected in the next item.  Sorry
> for not merging them; I wanted to get this out the door.)
>
> *6.*  Section 3.2, 3rd paragraph:
>
> I'm concerned that telling implementors to use %-encoding of
> disallowed characters that appear in NSS might conflict with an
> existing URN namespace's encoding rule.  Also, %-encoding is a mess,

True. But it's a mess we know about.

> because it's used by so many different layers of software without any
> clear guidance about which layers undo which portions of the
> encoding.  So I doubt that it's a good idea to specify a uniform rule
> for how every namespace should encode its native names to URN format;
> instead, I think that encoding considerations should be part of
> namespace-specific "canonicalization" rules.
>
> As for interoperability: if a URN appears with its urn:nid prefix,
> software should be able to assume that it's already in appropriate
> format, with all necessary encoding applied, and apply uniform
> parsing rules, uniform resolution code, etc. to that URN.   But if an
> identifier appears without a urn:nid prefix, software shouldn't be
> trying to generate a URN from it, or otherwise treat it as a URN,
> unless that software knows the namespace-specific rules for encoding
> those identifiers as URNs.   And somewhere, probably in this
> document, there should be a discussion about the difference between
> URN format and namespace-specific "native" formats of identifiers.

I agree that some text about that would be helpful.

> CURRENT:
>
> Depending on the rules governing a namespace, names that are valid
> in a namespace might contain characters that are not allowed by the
> "pchar" production referenced above (e.g., characters outside the
> ASCII range or characters that are reserved in URIs, such as "?",
> and "#").  While such a string might be a valid name, it is not a
> valid URN until it has been translated into a conformant NSS.
> Translation is done by percent-encoding each disallowed character
> using the method defined in Section 2.1 of the generic URI
> specification [RFC3986].  Note that the "%" character is allowed in
> the NSS only for the purpose of percent-encoding.
>
> RECOMMENDED:
>
> Depending on the rules governing a namespace, names that are valid
> in a namespace might contain characters that are not allowed by the
> "pchar" production referenced above (e.g., characters outside the
> ASCII range or characters that are reserved in URIs, such as "?",
> and "#").  While such a string might be a valid name, it is not a
> valid URN until it has been translated into a conformant
> NSS.*Translation****of an identifier from its "native" format to URN
> format is accomplished**by using the canonicalization and encoding
> methods  defined for that **URN namespace in that namespace's
> registration.  Software that is not aware of those URN
> canonicalization**and encoding rules for the namespace used MUST NOT
> construct URNs  from such identifiers.*

That seems fine, with the proviso that I think it might be reasonable to 
recommend percent-encoding.

> *7.* Last paragraph of section 3.2:
>
> CURRENT:
>
> If a namespace designates one or more characters conforming to the
> "pchar" rule as having special meaning for that namespace (e.g.,
> "@") and the namespace also uses that character in a literal sense,
> when used in a literal sense the character MUST be percent-encoded
> (e.g., "%40").  For related considerations with regard to NID
> registration, see Section 7.3.2.
>
>
> RECOMMENDED:
>
> If a namespace designates one or more characters conforming to the
> "pchar" rule as having special meaning for that namespace (e.g.,
> "@") and the namespace also uses that character in a literal
> sense,*that ***    *namespace registration MUST specify a means of
> representing *    *its native format*  *identifiers as URNs in a way
> that conforms *    *with the URN NSS grammar*.*See Section 7.3.2.*

+1

Peter


From nobody Thu Sep  3 18:38:42 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFAA31ACD79 for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.301
X-Spam-Level: 
X-Spam-Status: No, score=-0.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_OFF=2.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 9oG1DShrEG08 for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:38:37 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71F171ACDDE for <urn@ietf.org>; Thu,  3 Sep 2015 18:38:37 -0700 (PDT)
Received: by padhy16 with SMTP id hy16so5200062pad.1 for <urn@ietf.org>; Thu, 03 Sep 2015 18:38:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=dtlMuv06PHOUsoWxC9F6C6PhEIZVitEmFUtDq0BOuec=; b=WUMq9FeoN9q1asfpXFYxinu3NOrBZVYiRzqs4d3ghop1+xxbr2tW7wN+mwGxLHx32G 0LBVwdOUGp2PuuJgA/5VoDAe8cc6z06AHiU1134l7XrJhc3HD0YD/xWrIXfscqU4/iZi iHWgcNcD3H2YJ99QCrGG9bhhoMOx38WBwQSNHt8ab2F8Q10Q/f18nI9V2wtBytis58TD PsZwDX7TYA8znkDI7LqJ/HExED5jSDAB8ulhHir+4i6+21vOt/Uc5gebEVRdN0v/vcFB CltyyqmvGNw5SA/1Z7mcdcEGoWALlzcP8XfDkCgRN4D/ZSRXwxQSqx5tNnXguxa5FLjr nCSQ==
X-Gm-Message-State: ALoCoQk16wr9OZLh4Opk7C8LAXo/xLRTH4M1TQ5Ctz0DOWrmus5jzBsXULGJQhrHaeVBFc2y0Tgu
X-Received: by 10.66.184.197 with SMTP id ew5mr2318224pac.54.1441330716934; Thu, 03 Sep 2015 18:38:36 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:cc24:4db:ecc4:70ae]) by smtp.googlemail.com with ESMTPSA id eh4sm430968pbd.27.2015.09.03.18.38.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Sep 2015 18:38:35 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8F613.2080907@andyet.net>
Date: Thu, 3 Sep 2015 19:38:27 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <559463C3.3030905@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/mUbui6ClbdteHtUmfbkNBDw6rzY>
Subject: [urn] Section 3.3: Optional Components (was: Re: review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 01:38:40 -0000

Third installment...

On 7/1/15 4:03 PM, Keith Moore wrote:

> *8.* Section 3.3:
>
> I have several problems with this section overall:
>
> Defining new URN components without saying anything about semantics
> (a) invites inconsistent interpretation of those components from one
> URN namespace to the next (which thwarts the ability to write client
>  software that handles URNs in a uniform way), and (b) also threatens
> to harm the ability to specify queries and/or fragments with URNs
> that resolve to URLs.
>
> Even though the semantics of q-components and f-components might vary
>  from one URN to the next, it's important for this document to make
> clear that client software can handle these in a uniform manner.  For
> URNs that resolve to URLs, q-component /always/ maps to the URL query
> (if that URL scheme supports query), and f-component /always/ maps to
> the URL fragment.

Syntactically, yes.

> At least for those resources, the semantics of the
>  q-components are defined by those resources, not by the namespace.
> The semantics of f-components are defined by the media type of the
> resource, not by its URN namespace.   (The namespace can choose to
> not assign names to resources that don't fit its criteria for
> interpretation of queries or fragments, but it's important that
> 2141bis not promote the idea that the interpretation of these
> components is arbitrary, or namespace-specific.)

I think I agree. However, it's also important that 2141bis not promote 
the idea that all URNs can be resolved to URLs. Your proviso specifying 
that this behavior applies "for URNs that resolve to URLs" is spot on.

> It's also important to recognize that a resource can quite reasonably
>  have multiple URNs, in the same and/or different namespaces.  This
> must not create a conflict or ambiguity over the interpretation of
> f-components or q-components with respect to that resource, either
> when such components appear within URNs or when those components
> appear in relative references within those resources.

Good point (not that I think it will be a common occurrence for the same 
resource to be identified by URNs in different namespaces).

> If this document is going to focus "almost exclusively" on URN
> syntax, then we need to have an accompanying document that discusses
> semantics of the new components.  I think that's probably a Bad Idea.
> Every time a reader has to switch from one document to another,
> there's a good chance that he'll lose some context, or worse, not
> bother to read the next document.   I'm fine with -semantics-clarif
> being in a separate document if it just explains why certain
> decisions were made, but it's probably not a good idea to entirely
> separate syntax and semantics.   So I'm proceeding on the assumption
> that at least minimum interpretation/semantics of these new
> components needs to be specified in 2141bis.

I guess I'm not as uncomfortable as you are regarding the relative lack 
of detail about the semantics (especially of r-components), but then I 
am not optimistic about the ability of this WG or any other group to 
come to agreement about that for all URN namespaces.

> CURRENT:
>
> Because this specification focuses almost exclusively on URN syntax,
> it does not define the semantics of the q-component, r-component,
> and f-component for URNs in general.  Instead, additional
> specifications might establish these matters for URN-related services
> (such as URN resolution) or for individual URN namespaces (e.g., to
> handle extended information about the resource identified by a URN).
> Defining the details of such usage is the responsibility of
> specifications for URN resolution services, namespace registration
> requests or specifications for individual namespaces, and other
> appropriate documentation (such as policy documents governing the
> management of a given URN namespace).
>
> Unless specifically defined for a particular namespace after
> publication of this document, use of these components is disallowed,
> thereby maintaining strict backward compatibility with namespaces
> defined in accordance with [RFC2141] and registered in accordance
> with [RFC3406].
>
>
> SUGGESTED:
>
> *As compared to [RFC2141], this document extends the URN syntax to***
> *permit inclusion of three new types of components: q-component,***
> *r-component, and f-component. **Because this specification focuses
> ***    *almost exclusively on URN syntax, it does not define detailed
> ***    *semantics for these components for URNs in general. However,
> each of ***    *these components has a distinct role from the others,
> which is***    *independent of the URN and its namespace, and it is
> intended that ***    *clients be able to handle these components
> uniformly for all URNs. ***    *In general: ******o q-component is
> intended for parameters to be transmitted to ****the named resource
> and interpreted by that resource; ******o r-component is intended for
> parameters to be transmitted to ****resolution services and
> interpreted by those services; and ******o f-component is intended to
> be interpreted by the client as ****a specification for a location
> within or region of, the****named resource.*** *The above is true
> regardless of the URN's namespace.******Whenever a URN resolves to a
> URL which may be used to access the****resource, there is a more
> specific interpretation of q-component and ****f-component: the
> q-component is copied verbatim to the query portion****  of the URL
> (if that URL scheme supports query), and the f-component****  is
> copied verbatim to the fragment portion of the URL. This
> is****necessary, among other reasons, so that interpretation of
> q-component****and f-component when associated with URNs, will be
> consistent with****the interpretation of relative references
> containing query and/or ****fragment, respectively, within documents
> which are accessible via URNs.****Thus, for resources which may be
> accessed via a URL, the semantics of ****q-component are identical to
> those for queries to that resource, and ****the semantics of
> f-components are identical to those of fragments for****that
> resource. Semantics of q-component and f-component for
> resources****that inherently cannot be accessed via a URL are
> undefined by this ****document; however, they SHOULD be consistent
> with the above roles. ****It is expected that additional
> specifications will define the semantics****of
> r-components.******Note: In general, neither syntax nor semantics of
> q-component or f-component are**defined by, or dependent on, the
> namespace of the URN. **A particular**namespace might, however,
> define use of r-components that are specific **to its namespace and
> supported by the resolution services  which that**namespace operates
> and/or recommends.****Any of these components MAY be used with URNs
> from existing namespaces whether or not the namespace explicitly
> supports them. As described above, the interpretation of q-component
> and f-component is namespace- independent. Interpretation of an
> r-component may be namespace-dependent to some degree if it relies on
> behavior of a namespace-specific resolution service. If a URN
> contains r-components that are not defined by the namespace, the
> meaning of the URN and result of resolution are out of scope for this
> specification. *

Despite the caveats I expressed above, I think that text is mostly fine. 
I will look it over more carefully before we're done.

> Note about the last paragraph of the suggested text as compared to
> the original: I think it's pointless to forbid use of a *-component
> with existing URNs, especially when the client's interpretation of
> such a component should be consistent from one URN to the next
> anyway.   It's unreasonable to expect clients to implement
> namespace-specific behavior for interpretation of *-components. *

Even for r-components? Or do you say that because we're talking about 
clients here?

> **9.* Section 3.3.1
>
> Again, it is important that this document be clear about the
> appropriate roles for each of these components, and for this document
> to not encourage inconsistent use of these components from one client
>  application or namespace to another.   Also, it's important to be
> clear that q-components are not passed to URN resolvers, so that they
> are not taken into account in URN resolution.

Agreed.

> Also, the example chosen in the -12 text to illustrate use of
> q-components in this section, while valid, seems likely to cause
> confusion.  While it is certainly possible and reasonable to have a
> resource that returns metadata about other resources, and for a URN
> to be assigned to a metadata-returning resource, the example URN
> doesn't actually specify the URI of a resource for which metadata is
> to be returned.   The reader is likely to presume that the resource
> named is returning metadata about itself.  And while a resource could
> certainly do that (and it might be a useful convention), that's
> assuming a lot more than anything that's been specified to date.
> Normally one does not obtain metadata by querying a resource,

Would you consider HTML <head/> to be an exception? Or are you thinking 
about different kinds of metadata?

> one
> obtains metadata by contacting a resolution service - and the
> r-component, not the q-component, must be used to pass paramters to
> the resolution service.
>
> CURRENT:
>
> 3.3.1.  q-component
>
> Although the URN q-component has close to the same syntax as the URI
> query component, the URN q-component need not be semantically
> equivalent to the URI query component and therefore is called by a
> different name in this specification to emphasize that the
> relationship is about syntax only (see also
> [I-D.ietf-urnbis-semantics-clarif]).
>
> The q-component is indicated by the first question mark ("?")
> character and terminated by a double question mark ("??"), by a
> number sign ("#") character, or by the end of the URI.  The q-string
> MUST NOT begin with a question mark ("?") since a double question
> mark is reserved for use by an r-component (Section 3.3.2).  The
> characters slash ("/") and question mark ("?") may represent data
> within the q-string.  Note that characters outside the ASCII range
> [RFC20] MUST be percent-encoded using the method defined in Section
> 2.1 of the generic URI specification [RFC3986].
>
> As described under Section 4, the q-component SHALL NOT be taken
> into account when determining URN equivalence.
>
> The q-component is primarily intended to be used for passing
> information in requests to the resources identified by a URN or to
> applications that manage such resources.  Consider the hypothetical
> example of passing parameters to an application that returns
> metadata about a resource (say, Dublin Core [RFC5013] data about a
> published book).  This could perhaps be accomplished by specifying
> the desired metadata field (e.g., "description") in the q-component,
> resulting in URNs such as
> "urn:example:0-395-36341-1?operation=search&field=description".
> However, this primary purpose is not intended to forestall other
> potential uses for q-components.
>
>
> SUGGESTED:
>
> (note: the following text assumes the grammar alternative 2 and will
> need to be changed if a different fix for the grammar is chosen)

I think alternative 2 is sensible.

> 3.3.1.  q-component
>
> *The URN q-component has the same syntax as the URI query component.
> ****If a URN resolves to a URL with a scheme that supports a query
> ****component, the q-component from the URN is copied verbatim to
> the****query component of the URL.**If the URN does not resolve to a
> URL,****the interpretation of the q-component is undefined by this
> ****specification; however, it SHOULD be used to communicate
> parameters****that are interpreted by a resource. The q-component
> MUST NOT be  used**to communicate parameters to a resolution
> service.********The q-component follows the r-component if one
> exists. The start of the**q-component is indicated by**a**question
> mark ("?") character and ****terminated by a number sign ("#")
> character, or by the end of the URI. * The characters slash ("/") and
> question mark ("?") may represent data within the q-component. Note
> that characters outside the ASCII range [RFC20] MUST be
> percent-encoded using the method defined in Section 2.1 of the
> generic URI specification [RFC3986]. As described under Section 4,
> the q-component SHALL NOT be taken into account when determining URN
> equivalence.*Similarly, the q-component SHALL NOT be taken into
> account when resolving a URN and MUST**NOT be passed  to a resolution
> service when querying the service for metadata.*
>
> The q-component is*entirely*  intended to be used for passing
> information in requests to the resources identified by a URN or to
> applications that manage such resources.*Consider the hypothetical
> example of passing parameters to an application that returns
> weather****maps from different regions and/or for different time
> periods. This****could perhaps be accomplished by specifying lat/long
> coordinates and****dates/times in the URN's q-component.*

That seems mostly fine to me. Again, I'll look at it more carefully 
before we're done.

> * **10. * Section 3.3.2

If we follow alternative 2, this section would move up in the document 
(before the section on q-component).

> CURRENT:
>
> 3.3.2.  r-component
>
> The URN r-component has no syntactic equivalent in URIs.
>
> The r-component is indicated by a double question mark ("??") and
> terminated by a number sign ("#") character or by the end of the
> URI. The characters slash ("/") and question mark ("?") may represent
> data within the r-string.  Note that characters outside the ASCII
> range [RFC20] MUST be percent-encoded using the method defined in
> Section 2.1 of the generic URI specification [RFC3986].
>
> As described under Section 4, the r-component SHALL NOT be taken
> into account when determining URN equivalence.
>
> The r-component is primarily intended to be used for passing
> information in requests to URN resolution services (not, as with the
> q-component, to the resources identified by a URN or to applications
> that manage such resources).  Consider the hypothetical example of
> passing parameters to resolution service (say, an ISO alpha-2
> country code [ISO3166-1] in order to scope down the preferred country
> in which to search for a physical copy of a book).  This could
> perhaps be accomplished by specifying the country code in the
> r-component, resulting in URNs such as
> "urn:example:0-395-36341-1??cc=uk". However, this primary purpose is
> not intended to forestall other potential uses for r-components.
>
> This document defines only the syntax of the r-component and
> reserves it for future use.  The exact semantics of the r-component
> and its use in URN resolution protocols are a matter for potential
> standardization in separate specifications.
>
>
> SUGGESTED:
>
> (note: the following assumes the grammar alternative 2 and will need
> changes for different fixes to the grammar)
>
> 3.3.2.  r-component
>
> The URN r-component has no syntactic equivalent in URIs.
>
> ***The r-component precedes any q-component.

I suppose that would be "any q-component or f-component"?

> It is indicated by a
> double question mark ("??") and terminated by a number sign ("#")
> character, a question mark ("?"), or by the end of the URI. The slash
> ("/") may represent data within the r-component, but the question
> mark ("?") MUST NOT appear in an r-component. If there is a need to
> represent a question mark in data passed to a resolver, it MUST be
> percent-encoded in the URN.*****    Note that characters outside the
> ASCII range [RFC20] MUST be percent-encoded using the method defined
> in Section 2.1 of the generic URI specification [RFC3986].
>
> As described under Section 4, the r-component SHALL NOT be taken
> into account when determining URN equivalence.*The r-component SHALL
> be ****supplied along with the URN when presenting requests to URN
> resolution****services.*
>
> The r-component is*entirely*  intended to be used for passing
> information in requests to URN resolution services (not, as with the
> q-component, to the resources identified by a URN or to applications
> that manage such resources).  Consider the hypothetical example of
> passing parameters to resolution service (say, an ISO alpha-2
> country code [ISO3166-1] in order to scope down the preferred country
> in which to search for a physical copy of a book).  This could
> perhaps be accomplished by specifying the country code in the
> r-component, resulting in URNs such as
> "urn:example:0-395-36341-1??cc=uk".

Per Juha's feedback, that example needs to change.

> This document defines only the syntax of the r-component and
> reserves it for future use.  The exact semantics of the r-component
> and its use in URN resolution protocols are a matter for potential
> standardization in separate specifications.
>
>
> *11.*  Section 3.3.3
>
> CURRENT
>
> 3.3.3.  f-component
>
> Although the URN f-component has the same syntax as the URI fragment
> component, the URN f-component need not be semantically equivalent
> to the URI fragment component and therefore is called by a different
> name in this specification to emphasize that the relationship is
> about syntax only (see also [I-D.ietf-urnbis-semantics-clarif]).
>
> The f-component is indicated by the presence of a number sign ("#")
> character and terminated by the end of the URI.  Note that
> characters outside the ASCII range [RFC20] MUST be percent-encoded
> using the method defined in Section 2.1 of the generic URI
> specification [RFC3986].
>
> As described under Section 4, the f-component SHALL NOT be taken
> into account when determining URN equivalence.
>
> The f-component is primarily intended to distinguish the integral
> parts of resources named by URNs in particular namespaces.  Consider
> the hypothetical example of obtaining resources that are part of a
> larger entity (say, the chapters of a book).  Each part could be
> specified in the f-component, resulting in URNs such as
> "urn:example:978-952-10-7060-0#chapter1".  However, this primary
> purpose is not intended to forestall other potential uses for
> f-components.
>
>
> ALTERNATIVE
>
> 3.3.3.  f-component
>
> *The URN f-component has the same syntax as the URI fragment
> component. When a URN containing an f-component resolves to a
> URL,****the f-component from the URN is copied verbatim into the
> fragment****of that URL. Interpretation of the f-component for URNs
> that do****not resolve to URLs is not defined by this
> specification.*** The f-component is indicated by the presence of a
> number sign ("#") character and terminated by the end of the URI.
> Note that characters outside the ASCII range [RFC20] MUST be
> percent-encoded using the method defined in Section 2.1 of the
> generic URI specification [RFC3986].
>
> As described under Section 4, the f-component SHALL NOT be taken
> into account when determining URN equivalence.*Similarly, the
> f-component****MUST NOT be passed to resolution servers when querying
> them for resource**locations or metadata.*
>
> The f-component is primarily intended to distinguish the integral
> parts of resources named by URNs in particular namespaces.  Consider
> the hypothetical example of obtaining resources that are part of a
> larger entity (say, the chapters of a book).  Each part could be
> specified in the f-component, resulting in URNs such as
> "urn:example:978-952-10-7060-0#chapter1".  However, this primary
> purpose is not intended to forestall other potential uses for
> f-components*for URNs that do not resolve to
> network-accessible****resources. *

Here again that seems mostly fine to me.

Thanks for all the suggested text!

Peter


From nobody Thu Sep  3 18:40:34 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F751B434D for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 j-cwbVDr7-zP for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:40:33 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 618D91B4319 for <urn@ietf.org>; Thu,  3 Sep 2015 18:40:33 -0700 (PDT)
Received: by pacfv12 with SMTP id fv12so7730481pac.2 for <urn@ietf.org>; Thu, 03 Sep 2015 18:40:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=VoNHtt0pwE1ILmox/MIArkixpfUW8iiJZ5wpZX/VIUg=; b=hdkg9pjqtxdokmvwhAP0WlcRSvJJXM1oICf7I+Unqun8HpvJXy8mcfTElKWJegmARI kruVqEZqdKK9DdUXPi0nDRZADNvTfANJtuvy72KF0oqcX/SlPiXK4srAym3U7QHSMRYD 9y+RXVCJSgCEaDEBrC3p1Qvm1+pt1medjbZAfm4B2T/JooC3oBWp2nVlnFigqAnah/SP XIpYyIf7FohB+1vCG9LmgG6orK5NPpHL/FuoG+1uAJ1Q3gOVHxbTEi0NtVbBqL+DkL9s J0rV/Q4DsZduYlewz9fMj/+1etL/8+5lIeVdRoTMg+bnqcBtig7F/ktfInF42YrteAIF IZOA==
X-Gm-Message-State: ALoCoQmGzjU8h6i/BqE8i3RIp2WvuR48qpQe5+RZc0GAXogGgbBV3LFiWRMH1B9HY1PdidrGkko0
X-Received: by 10.68.244.234 with SMTP id xj10mr2283643pbc.13.1441330832978; Thu, 03 Sep 2015 18:40:32 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:cc24:4db:ecc4:70ae]) by smtp.googlemail.com with ESMTPSA id c6sm434341pat.13.2015.09.03.18.40.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Sep 2015 18:40:32 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8F68E.2000806@andyet.net>
Date: Thu, 3 Sep 2015 19:40:30 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <559463C3.3030905@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/d3p2RFp9Dei-KqaNAvd13nD54fc>
Subject: [urn] Section 5: URI Conformance (was: Re: review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 01:40:34 -0000

Fourth installment...

On 7/1/15 4:03 PM, Keith Moore wrote:

> *12.*  Section 5.3
>
> (NIT) I think it's a bit of a stretch to say what the result of use of a
> relative
> reference will be if there's no base URI.
>
> CURRENT:
>
>     If no such base URI exists, use of a relative reference with respect
>     to a URN is an error and will yield results that might be unexpected
>     or not useful.
>
> RECOMMENDED:
>
>     If no such base URI exists, use of a relative reference with respect
>     to a URN is an error.*Client behavior in this case is undefined. *

WFM.

Peter



From nobody Thu Sep  3 18:46:19 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6ED1B2A42 for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level: 
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 CzSmTUe2CWGV for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 18:46:17 -0700 (PDT)
Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C9691B36F4 for <urn@ietf.org>; Thu,  3 Sep 2015 18:46:16 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so2504026igb.0 for <urn@ietf.org>; Thu, 03 Sep 2015 18:46:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=e9MYYVT1mrOzhdSS86BmCUKcavWwRm6hkQL/HPnLNeM=; b=IhEKLqSZPnPFeS3dDk3T1vl7zTahwdkwelKGyVsCqssJPwhDLJkNcnfIhX5VWNdlmx asSH2oSCI2mBFXPxXGbJd4HEbCoQivcupGALwpGSZ/ZFR6T+NRcVIGVOWZN3FCbnybav 2pr5hzn4q8elQ2VQUV0u7Ch5lSw1tvKCfi7HhbT0JSuCXw3Kq3KPVVQ9kYlg/KTjS7RU /EObYepBmMhC31H+o73ssW6EVIFLzPZ1rStNgya8bcUAEdQ05ovAZm8TPzmD6fN005Rl IrNAGhGh5pkFKi6MIjJ/axH373KGfFEtinqFxUyQaK8zDLCm45XpnD3sQ7OI/SM0gxox muRg==
X-Gm-Message-State: ALoCoQmAGje3/Efo3NKYBsTw3rHD3028kfAMEYCEPm4ulXRTF51RRNb5C9HJT+A7kxNCFeOAZ0rW
X-Received: by 10.50.18.40 with SMTP id t8mr2073978igd.57.1441331175795; Thu, 03 Sep 2015 18:46:15 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:cc24:4db:ecc4:70ae]) by smtp.googlemail.com with ESMTPSA id v11sm518952iov.20.2015.09.03.18.46.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 18:46:15 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E8F7E2.5040507@andyet.net>
Date: Thu, 3 Sep 2015 19:46:10 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <559463C3.3030905@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/ogGEbIrTlhYgRRtvuIfqHbEfx0w>
Subject: [urn] Section 6: URN Namespaces Re:  review of rfc2141bis-12
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 01:46:19 -0000

Fifth installment...

On 7/1/15 4:03 PM, Keith Moore wrote:

> *13.*  Section 6, about halfway through
>
> Clarify that a resource MAY have more than one URN assigned to
> it, either in the same namespace or in different namespaces.
>
> CURRENT:
>
>     With regard to global uniqueness, using different NIDs for different
>     collections of identifiers ensures that no two URNs will be the same
>     for different resources, since each collection is required to
>     uniquely assign each identifier.  However, a single resource can have
>     more than one URN assigned to it for different purposes (for example,
>     if a book were published in a monograph series, it could have both an
>     ISBN [RFC3187] and an ISSN [RFC3044] assigned to it, resulting in two
>     URNs referring to the same book).  Subject to other constraints, such
>     as those imposed by the URI syntax [RFC3986], the rules of the URN
>     scheme are intended to allow preserving the normal and natural form
>     of identifiers specified elsewhere when they are treated as URN
>     namespaces.
>
>
> RECOMMENDED:
>
>     With regard to global uniqueness, using different NIDs for different
>     collections of identifiers ensures that no two URNs will be the same
>     for different resources, since each collection is required to
>     uniquely assign each identifier.*However, a single resource MAY have more than one URN assigned to it,
> either in the same namespace (if the namespace permits it) or**in different namespaces, and either for similar purposes or different **purposes.*  (for example,
>     if a book were published in a monograph series, it could have both an
>     ISBN [RFC3187] and an ISSN [RFC3044] assigned to it, resulting in two
>     URNs referring to the same book).  Subject to other constraints, such
>     as those imposed by the URI syntax [RFC3986], the rules of the URN scheme
>     are intended to allow preserving the normal and natural form of
>     identifiers specified  elsewhere when they are treated as URN
>     namespaces.

That's an improvement, thanks.

> *14.* section 6, last paragraph
>
> If we're deprecating X- namespaces, fine, but we should reserve
> namespaces beginning with X- to prevent conflicts with identifiers
> that might already exist in the wild.
>
> CURRENT:
>
>     Note: [RFC3406] defined a third type of "experimental namespaces",
>     denoted by prefixing the namespace identifier with the string "X-".
>     Consistent with general IETF conclusions about similar approaches
>     [RFC6648], this specification removes the experimental category and
>     syntax.  Because experimental namespaces were never registered,
>     removing the experimental category has no impact on the existing
>     registries or future registration procedures.  Because they are not
>     registered, strings that refer to existing experimental namespaces
>     are not valid URNs.  Truly experimental usages can, of course, employ
>     the 'example' namespace [RFC6963].
>
>
> RECOMMENDED:
>
>     Note: [RFC3406] defined a third type of "experimental namespaces",
>     denoted by prefixing the namespace identifier with the string "X-".
>     Consistent with general IETF conclusions about similar approaches
>     [RFC6648], this specification removes the experimental category and
>     syntax.  Because experimental namespaces were never registered,
>     removing the experimental category has no impact on the existing
>     registries.*However, to avoid the potential for conflict between****previously-allowed unregistered experimental namespaces and ****namespaces registered in the future, no registrations will be****accepted for new namespaces beginning with "X-". *Because they are not
>     registered, strings that refer to experimental namespaces
>     are not valid URNs.  Truly experimental usages*MAY*, of course, employ
>     the 'example' namespace [RFC6963].

Yes, that's better.

> *15.* Section 6.1
>
> CURRENT:
>
>     5.  It MUST NOT start with the string "xn--" or any other string
>         consisting of two letters followed by two hyphens.  Those strings
>         are reserved for potential representation of DNS A-labels and
>         similar strings in the future [RFC5890].
>
> RECOMMENDED:
>
>     5.  It MUST NOT start with the string "xn--" or any other string
>         consisting of two letters followed by two hyphens.  Those strings
>         are reserved for potential representation of DNS A-labels and
>         similar strings in the future [RFC5890].
>
> *6. It MUST NOT start with the string "X-" so that it will not be
> confused with an experimental namespace previously permitted by
> [RFC3406], nor conflict**with such a namespace.*

+1.

Peter



From nobody Thu Sep  3 19:45:55 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7EB1B37CA for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 19:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 zza7dyS1wgW8 for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 19:45:51 -0700 (PDT)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com [209.85.223.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 186AF1B468D for <urn@ietf.org>; Thu,  3 Sep 2015 19:45:51 -0700 (PDT)
Received: by ioiz6 with SMTP id z6so9394792ioi.2 for <urn@ietf.org>; Thu, 03 Sep 2015 19:45:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=AnyafbmFH7ZURom0nl6RrdoAUn/5AW1YIaZnbqXAQWY=; b=Y72wTLYcz1+R9zqqlMTOd1v3ZzwHfVboyGj2t8+wpeteiq1fXBhhyFV2lbkKtRaxYb tW6X4vPotol1rkiN/0rGIkSjZteUjdTP4z1X34vSIFbuvIqpZECz4QvI18iRrDlcuyBy gmMEyzJelMZD5BbCS+WmuzFuid04bgUKAF85XhYhNan9gyZuVXVDgBCLYiuzT+TwXaFP aR0lk4eZdt8wHwqNLWIctTTRz6k06WMsAuDzJqrXyEaPlHikF6gv18AeR/+LiJ5SUje0 Qlzhz+RxNuFfAq5MmmR1yu2kZc0nQ75GIDt1VOetdK+n42XFBglxCQ/DJ7JxlY0Up97x BQiA==
X-Gm-Message-State: ALoCoQnbR45QaVp7vGScCDCZUJva93toW93BpCY6XgHZmfbuAcyP1HGndOBE99Tbq5MAYnIg/dpz
X-Received: by 10.107.170.164 with SMTP id g36mr787319ioj.177.1441334750181; Thu, 03 Sep 2015 19:45:50 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id z5sm591857igl.21.2015.09.03.19.45.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 19:45:49 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55E905DC.1080209@andyet.net>
Date: Thu, 3 Sep 2015 20:45:48 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55E8DD7E.1020309@andyet.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/EfeaLcqwC0ZVcEU_lx6W62fQUsE>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 02:45:54 -0000

On 9/3/15 5:53 PM, Peter Saint-Andre - &yet wrote:
> Here is the second installment of my reply...
>
> On 7/1/15 4:03 PM, Keith Moore wrote:
>
>> *3.*  Section 3.2, 2nd paragraph:
>>
>> This document modifies the syntax of the NSS to allow the following
>> characters: "/", "~", and "&".
>>
>>
>> Are there reasons to permit "~" and "&", and have we sufficiently
>> investigated the implications of doing so?
>
> I think the idea was: is there a reason to *not* permit "~" and "&"?
> This is an artifact of trying to align with the URI spec as much as
> possible, in this case by reusing the 'pchar' rule.
>
>>  I am wondering whether
>> this will break parsers for no good reason.  I have seen URLs which
>> "~" was encoded to "%7E" (even though this shouldn't be necessary)
>> and "&" to "%26" (which also shouldn't be necessary except in a query
>> that uses HTML FORM encoding for HTTP GET).
>
> It's not our job to design around broken parsers. That way lies madness.
>
>> *4. * This document needs to clarify (somewhere) that the change to
>> the URN grammar DOES NOT change encoding rules for existing URN
>> namespaces, if there are existing namespaces that are used outside of
>> the URN context, and in which use any of "/", "~", or "&" are allowed
>> to appear in those names in native form.
>
> Although I have no objections to including such text,

Here is proposed text (adding the second paragraph below):

    This document modifies the syntax of the NSS to allow the following
    characters: "/", "~", and "&".  In particular, allowing the "/"
    character effectively makes it possible to encapsulate hierarchical
    identifiers from other naming systems.  For instance, consider the
    hypothetical example of a hierarchical naming system in which the
    identifiers take the form of a series of numbers separated by the "/"
    character, such as "1/406/47452/2".  If the naming authority for such
    identifiers were to use URNs, it would be natural to place the
    existing identifiers in the NSS, resulting in URNs such as
    "urn:example:1/406/47452/2".

    However, the foregoing changes to the syntax for the NSS do not
    change the encoding rules for URN namespaces that were defined in
    accordance with [RFC2141].  If any existing URN namespace that is
    used outside of the URN context (i.e., as a standalone identifier
    space) also allows the use of "/", "~", or "&" in the native form
    within that identifier space, then the encoding rules for that
    namespace are not changed by this specification.

> the universe of
> URN namespaces is small enough that we could determine if any such
> namespaces exist:
>
> http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml
>
>> *5.*  Also, something that I think could possibly use a bit more
>> explicit attention in the registration section and perhaps elsewhere:

I propose adding a new sentence to the very first paragraph of the 
introduction:

    A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
    [RFC3986] that is assigned under the "urn" scheme and a particular
    namespace, with the intent that the URN will be either a persistent,
    location-independent resource identifier or in some cases an abstract
    designator that is persistent but that does not identify a resource.
    A URN namespace is a collection of such identifiers, each of which is
    (1) unique, (2) assigned in a consistent and managed way, and (3)
    assigned according to a common definition.  (Some URN namespaces
    create names that exist only as URNs, whereas others create URNs out
    of names that already exist in other identifier systems, such as
    ISBNs [RFC3187] and ISSNs [RFC3044].)

>> In some sense there are two kinds of URN namespaces: those that exist
>>  solely as URNs, and identifier spaces that exist independently of
>> URNs.   The latter kind of identifier has a "native" form and a URN
>> form, and its URN namespace registration should specify an algorithm
>> for converting from native form to URN form.   Ideally this algorithm
>>  produces a distinguished form of its input when converting it to URN
>>  format - this makes it easier to build generic services that answer
>>  queries for arbitrary URNs.   If the algorithm is just to use
>> percent-encoding, that's fine, but IMO this should be explicitly
>> specified in the namespace registration. I don't think we should
>> unilaterally impose this algorithm for all identifier spaces.
>
> But do you think we should recommend it? This feels like one of those
> situations where the creativity of the namespace registrant could lead
> to bad results.
>
>> Client software that just handles URNs doesn't need to worry about
>> this.   Such software should always see the URN form of such
>> identifiers and should be able to handle all URNs in a uniform
>> manner.   However, software that allows such identifiers to be input
>> directly (e.g. without the urn:xxx: prefix) and converts those
>> identifiers to URNs, needs to be aware of the conversion rules for
>> each URN namespace that it accepts.
>
> Aren't we verging close to violation of the principle of uniformity
> here? I'd at least prefer to say that you SHOULD use percent-encoding
> (unless you have good reason not to, and please document your reasons,
> such as having an existing encoding rule as you describe below).
>
>> Anyway, I think it would help to have some background text early in
>> the document that explains this, and one or two specific items in the
>>  registration template
>
> That does sound helpful.
>
>> (I can try to come up with text if desired, but I didn't want to
>> delay this review any longer.)
>>
>> (Also, much of this item is also reflected in the next item.  Sorry
>> for not merging them; I wanted to get this out the door.)
>>
>> *6.*  Section 3.2, 3rd paragraph:
>>
>> I'm concerned that telling implementors to use %-encoding of
>> disallowed characters that appear in NSS might conflict with an
>> existing URN namespace's encoding rule.  Also, %-encoding is a mess,
>
> True. But it's a mess we know about.
>
>> because it's used by so many different layers of software without any
>> clear guidance about which layers undo which portions of the
>> encoding.  So I doubt that it's a good idea to specify a uniform rule
>> for how every namespace should encode its native names to URN format;
>> instead, I think that encoding considerations should be part of
>> namespace-specific "canonicalization" rules.
>>
>> As for interoperability: if a URN appears with its urn:nid prefix,
>> software should be able to assume that it's already in appropriate
>> format, with all necessary encoding applied, and apply uniform
>> parsing rules, uniform resolution code, etc. to that URN.   But if an
>> identifier appears without a urn:nid prefix, software shouldn't be
>> trying to generate a URN from it, or otherwise treat it as a URN,
>> unless that software knows the namespace-specific rules for encoding
>> those identifiers as URNs.   And somewhere, probably in this
>> document, there should be a discussion about the difference between
>> URN format and namespace-specific "native" formats of identifiers.
>
> I agree that some text about that would be helpful.
>
>> CURRENT:
>>
>> Depending on the rules governing a namespace, names that are valid
>> in a namespace might contain characters that are not allowed by the
>> "pchar" production referenced above (e.g., characters outside the
>> ASCII range or characters that are reserved in URIs, such as "?",
>> and "#").  While such a string might be a valid name, it is not a
>> valid URN until it has been translated into a conformant NSS.
>> Translation is done by percent-encoding each disallowed character
>> using the method defined in Section 2.1 of the generic URI
>> specification [RFC3986].  Note that the "%" character is allowed in
>> the NSS only for the purpose of percent-encoding.
>>
>> RECOMMENDED:
>>
>> Depending on the rules governing a namespace, names that are valid
>> in a namespace might contain characters that are not allowed by the
>> "pchar" production referenced above (e.g., characters outside the
>> ASCII range or characters that are reserved in URIs, such as "?",
>> and "#").  While such a string might be a valid name, it is not a
>> valid URN until it has been translated into a conformant
>> NSS.*Translation****of an identifier from its "native" format to URN
>> format is accomplished**by using the canonicalization and encoding
>> methods  defined for that **URN namespace in that namespace's
>> registration.  Software that is not aware of those URN
>> canonicalization**and encoding rules for the namespace used MUST NOT
>> construct URNs  from such identifiers.*
>
> That seems fine, with the proviso that I think it might be reasonable to
> recommend percent-encoding.

I propose the following adjusted text:

    Depending on the rules governing a namespace, names that are valid in
    a namespace might contain characters that are not allowed by the
    "pchar" production referenced above (e.g., characters outside the
    ASCII range or characters that are reserved in URIs, such as "?", and
    "#").  While such a string might be a valid name, it is not a valid
    URN until it has been translated into a conformant NSS.  In the case
    of URNs that are formed from names that exist separately in a
    standalone identifier space, translation of an identifier from its
    "native" format to URN format is accomplished by using the
    canonicalization and encoding methods defined for that URN namespace.
    Such methods SHOULD use percent-encoding unless the standalone
    identifier space already defines different encoding rules for such
    characters within the native format.  Software that is not aware of
    those namespace-specific canonicalization and encoding rules MUST NOT
    construct URNs from the names in the standalone identifier space.

>> *7.* Last paragraph of section 3.2:
>>
>> CURRENT:
>>
>> If a namespace designates one or more characters conforming to the
>> "pchar" rule as having special meaning for that namespace (e.g.,
>> "@") and the namespace also uses that character in a literal sense,
>> when used in a literal sense the character MUST be percent-encoded
>> (e.g., "%40").  For related considerations with regard to NID
>> registration, see Section 7.3.2.
>>
>>
>> RECOMMENDED:
>>
>> If a namespace designates one or more characters conforming to the
>> "pchar" rule as having special meaning for that namespace (e.g.,
>> "@") and the namespace also uses that character in a literal
>> sense,*that ***    *namespace registration MUST specify a means of
>> representing *    *its native format*  *identifiers as URNs in a way
>> that conforms *    *with the URN NSS grammar*.*See Section 7.3.2.*

I propose the following adjusted text:

    If a namespace designates one or more characters conforming to the
    "pchar" rule as having special meaning for that namespace (e.g., "@")
    and the namespace also uses that character in a literal sense, when
    used in a literal sense the namespace registration MUST specify a
    method of representing its native-format identifiers as URNs in a way
    that conforms with the generic URN NSS grammar.  This method SHOULD
    use percent-encoding unless the standalone identifier space already
    defines different encoding rules for such characters.  For related
    considerations with regard to NID registration, see Section 7.3.2.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Sep  3 23:07:48 2015
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8377D1A0404 for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 23:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.998
X-Spam-Level: 
X-Spam-Status: No, score=0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, MANGLED_OFF=2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 WyLFX-MS0HaS for <urn@ietfa.amsl.com>; Thu,  3 Sep 2015 23:07:44 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0706.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::706]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D33F1B3E4D for <urn@ietf.org>; Thu,  3 Sep 2015 23:07:42 -0700 (PDT)
Received: from AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) by AMSPR07MB453.eurprd07.prod.outlook.com (10.242.106.143) with Microsoft SMTP Server (TLS) id 15.1.256.15; Fri, 4 Sep 2015 06:07:23 +0000
Received: from AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) by AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) with mapi id 15.01.0256.013; Fri, 4 Sep 2015 06:07:23 +0000
From: "Hakala, Juha E" <juha.hakala@helsinki.fi>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Usage of f-, q- and r-components
Thread-Index: AdDIQbL0NAceB7DfRNuZTediDm8aUwAqLg8ABxmHt4AAFerigAA+JayAAAwni8A=
Date: Fri, 4 Sep 2015 06:07:23 +0000
Message-ID: <AMSPR07MB4548320A8BE86683B2491ECFA570@AMSPR07MB454.eurprd07.prod.outlook.com>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE> <55E7377D.50702@network-heretics.com> <55E8D88D.7050206@andyet.net>
In-Reply-To: <55E8D88D.7050206@andyet.net>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=juha.hakala@helsinki.fi; 
x-originating-ip: [128.214.71.222]
x-microsoft-exchange-diagnostics: 1; AMSPR07MB453; 5:m7aLRclWIyc9Ua+V7aU99s8Wquj8bBrS06TsLPSLkDrhzEW6zyaTIErdRBKabuDpgI1kjkmDleoLum3bcC9mJeKNep4t2Caa9ppFdoBZsS3pwhWAXaooaMJAH4pORwhHS2OE0qZTISSSHpLr7twjGA==; 24:i6B8akSd0Dsk8NbISlqqXbLEbuD+46f7Tv9Qu1T286wkCBngQbuUfx9YB9yY0xTVoCfsQINGnuOzKK336b+H76AHUC6ICwRC6eWFMnmjW/Q=; 20:WAR3w8zgPdSlnEtlIhrjxkK1nV6x5yHE+ko/xQp+iOIm3A/8GuQ6jTIXWAnXsMoLf6TtyOAvWtGG2J3aJvySSw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB453;
x-microsoft-antispam-prvs: <AMSPR07MB4530C429FE06ECAC7D49127FA570@AMSPR07MB453.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(5005006)(3002001); SRVR:AMSPR07MB453; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB453; 
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377454003)(189002)(13464003)(199003)(479174004)(46102003)(101416001)(2900100001)(5007970100001)(5004730100002)(2950100001)(74316001)(92566002)(93886004)(62966003)(5003600100002)(87936001)(122556002)(64706001)(66066001)(19580405001)(76576001)(74482002)(86362001)(77156002)(19580395003)(33656002)(97736004)(102836002)(5001920100001)(4001540100001)(77096005)(68736005)(15975445007)(5001960100002)(2501003)(5001830100001)(107886002)(5001860100001)(40100003)(50986999)(5001770100001)(10400500002)(189998001)(106356001)(5002640100001)(54356999)(105586002)(81156007)(76176999); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB453; H:AMSPR07MB454.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: helsinki.fi does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: helsinki.fi
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2015 06:07:23.2452 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 98ae7559-10dc-4288-8e2e-4593e62fe3ee
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB453
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/IQYGYAuxDZzvxmKGsJ4fCmCPVAM>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 06:07:47 -0000

Hello,

people who manage URN namespaces will only be responsible of namespace spec=
ific strings. When somebody / something adds a component to a URN, there sh=
ould not be an expectation that the component will persist in the same way =
as the URN proper.=20

There is one exception: f-components will be fairly persistent iff they are=
 used in namespaces where the URN applies to a single manifestation of the =
identified resource only. An example is ISBN namespace, an ISBN assigned fo=
r a book in PDF format is not supposed to re-assigned to any other manifest=
ation of the book.  Alas, mistakes do happen, and therefore even in urn:isb=
n namespace f-components are not to be fully trusted, although they are sti=
ll more reliable than fragments added to URLs. Note that if the same ISBN i=
s given to two manifestations of a book, the URN:ISBN remains actionable, a=
lthough there is a possibility that the user will get an unexpected version=
 of the book.   =20

IMO r- and q-components will normally be created on the fly and piggybacked=
 with the rest of the URN whenever there is a need to request something els=
e than the default resolution service (whatever that is).=20

Whatever the appropriate request for a certain service is will change over =
time, so it would be shortsighted to "hardcode" r- and especially q-compone=
nts. For instance, in current application environment library systems might=
 use Z39.50 and MARC 21 metadata format to fulfill I2C request; a decade fr=
om now the protocol may be different (BLOAT sounds like a nice name, althou=
gh then our systems would be bloated) and the default metadata format is li=
kely to be something else as well. Such technological changes will have maj=
or impact on q-components, so they are definitely non-persistent. It is pos=
sible to make r-component more immune to technical obsolescence, but even t=
hat will be challenging. I2C can and will be reserved for requesting metada=
ta about resource, but there will still be the problem of specifying approp=
riate metadata format; the one supported now by all integrated library syst=
ems may be supported by zero ILMs 50 years from now. Not defining the forma=
t at all makes the I2C request persistent, but as a result resolution proce=
ss becomes somewhat unpredictable since metadata format will be whatever th=
e target system regards as default.=20

To sum up, components are not part of the namespace specific string, they w=
ill not be managed in the same way as NSS (since basically anyone can add a=
 component to an existing URN any time), and apart from at least some f-com=
ponents they will not be persistent in the URN sense of the word. And when =
a component is added, the URN still identifies the same resource as persist=
ently as before, but the additional functionality requested by the componen=
t is subject to technological obsolescence.  =20

Juha   =20

> -----Original Message-----
> From: urn [mailto:urn-bounces@ietf.org] On Behalf Of Peter Saint-Andre -
> &yet
> Sent: 4. syyskuuta 2015 2:32
> To: Keith Moore <moore@network-heretics.com>; urn@ietf.org
> Subject: Re: [urn] Usage of f-, q- and r-components
>=20
> On 9/2/15 11:53 AM, Keith Moore wrote:
> > On 09/02/2015 03:25 AM, Svensson, Lars wrote:
> >> This is where we differ: In my opinion the resolver needs to know what
> "I2C" means, whom to ask for the URC and how to build the request. The
> reason is that if the client already mandates what protocol to use we're =
in for
> serious problems when in future there is no bibiliographic lookup service=
 that
> supports SRU (or Z39.50) because everyone has moved on to BLOAT
> (Bibliographic Lookup Online Access Terminal) or whatever protocol is en
> vogue at that time. If URNs with r-components are intended to be persiste=
nt,
> they must only say_what_  is to be done, but not_how_.
> >
> > I think we should make clear that only the "assigned portion" of a URN
> > can be expected to be persistent.   If an f-component, q-component,
> > and/or r-component is included with the URN, the entire URN can no
> > longer expected to be persistent, but the "assigned portion" is still
> > expected to be persistent.
>=20
> Agreed.
>=20
> Peter
>=20
>=20
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn


From nobody Fri Sep  4 00:27:47 2015
Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024BE1A92F1 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 00:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.16
X-Spam-Level: 
X-Spam-Status: No, score=-0.16 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, MANGLED_OFF=2.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 JeJo95-mIAYq for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 00:27:44 -0700 (PDT)
Received: from nordpol.dnb.de (nordpol.dnb.de [193.175.100.40]) by ietfa.amsl.com (Postfix) with ESMTP id DB2A81A8771 for <urn@ietf.org>; Fri,  4 Sep 2015 00:27:43 -0700 (PDT)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by nordpol.dnb.de (Postfix) with ESMTP id 3B1348AFD6; Fri,  4 Sep 2015 09:27:42 +0200 (CEST)
X-AuditID: 0a453fe7-f79136d0000011d7-ab-55e947ed6f7b
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 3F.07.04567.DE749E55; Fri,  4 Sep 2015 09:27:42 +0200 (CEST)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Fri, 4 Sep 2015 09:27:41 +0200
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Usage of f-, q- and r-components
Thread-Index: AdDIQbL0NAceB7DfRNuZTediDm8aUwAl/SwABxxsXLAAEwY+gAA+JayAABScUHA=
Date: Fri, 4 Sep 2015 07:27:40 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D0D4C66@dnbf-ex1.AD.DDB.DE>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE> <55E7377D.50702@network-heretics.com> <55E8D88D.7050206@andyet.net>
In-Reply-To: <55E8D88D.7050206@andyet.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.12.173]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA12Ta0hTYRjHeXeO29naW6+b07eZXU75xchLKViEBlkqWpmmiSV5bKdtOS/s bKJ9aVKhDSuTCSVJCRZ2oUzDkoRoSaWGSh/UQvvQzVS8FIlGEp2zs9mxb8/5Pc//z/95Hw5F aMYUespcZGOtRYyFlqtI1Z74uS3TieOZkZ+HlbG1c33y2J6PXURs3ZlZ2S4iqW9kUJHU1PRL llT7OiuNyFHtNLAWcylrjYjLU5m+jrbLSlzqstab3xQOMKx0AiWFUTSeazkrE+tAPPDhgdwJ VJQGdQHc5G4jxY92gOcafiucQEHJURieMTkBRQWgU3jEnS5ItWgbbux2kiKOxosOm4AD0H5c WdcOBEyiTbjnQ4RQQpSC3zcXidbVMtzveOwnjCt56y+LzaRQAxSCW1r6CaEmUBBu/TrvJ4ZE uKlT5Bjp8PinP16+HrtcvXJxPhLP9F33ajfjW42Tnhoif9x99TNZA3T1Ett6iaReIqmXSG4A 8g5YyRUao8IZQ7jBkB9uYFuBeJGxJ+Di2wQ3QBSg1fDa/LdMjR9TypUXusEBSkbr4Okt45ma lfnFhnITw5mOWe0WlqMDoIK/owYu4Xy7pYBeC6fGxzI1QUuUs3Ml5uPmYjt3zG61uAGmCF5K eqQGpvwUay0WDd0gmCLpIHj5acUhDTIyNraAZUtYq6+bTVE0huf28kJ/K2tky06YLTZfm9dZ dvMdJO14Am0QA+mljf8zySilG6RSaj6YS/CHXAlTyJmNXm8tXLeVp2of9fiGwCMTvG+gDy73 7AEZ+iBYK5ghYcJkL1rKqg+E0zX8G6+SNARL/XqYEs8LVkv4ctcJkMyfSAsp4fXU/H/1L6MG 7hPgCi/0RFwDWSGizsv+90rlbxsAlXGehW2MTbrwjjjPwl7qXThagIE+uNxO7wDdDceTfy3G fJxVVhFT9288P5loCe28cCk+peVRzPmjA/fKpisST9eW4ZdbO1TtF1ytWUNT1RmFB6vSB6Jf 3T6cU6pa+F5pHHp2Vf3uVe6J/sHRhOwerfbhz7xGLqQ39MXG147JhTbdm86JKPnMZLLBGXxX O1zdsL3ghzM57cpIB51Lk5yJiQojrBzzF3XWDBB6BAAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/jUvI-Bagy3r53BNKtXPFM9J953I>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 07:27:46 -0000

On Friday, September 04, 2015 1:32 AM, Peter Saint-Andre - &yet wrote:
> On 9/2/15 11:53 AM, Keith Moore wrote:
> > On 09/02/2015 03:25 AM, Svensson, Lars wrote:
> >> This is where we differ: In my opinion the resolver needs to know what
> "I2C" means, whom to ask for the URC and how to build the request. The
> reason is that if the client already mandates what protocol to use we're =
in for
> serious problems when in future there is no bibiliographic lookup service=
 that
> supports SRU (or Z39.50) because everyone has moved on to BLOAT
> (Bibliographic Lookup Online Access Terminal) or whatever protocol is en
> vogue at that time. If URNs with r-components are intended to be
> persistent, they must only say_what_  is to be done, but not_how_.
> >
> > I think we should make clear that only the "assigned portion" of a URN
> > can be expected to be persistent.   If an f-component, q-component,
> > and/or r-component is included with the URN, the entire URN can no
> > longer expected to be persistent, but the "assigned portion" is still
> > expected to be persistent.
>=20
> Agreed.

I agree, too, but still want to emphasise that when we design the interface=
 for communication with the resolver ("r-component") we should avoid specif=
ying protocols or specific query parameters to be passed on to an underlyin=
g service. The resolver should know how to resolve the URN possibly using i=
nformation from the r-component, to specify how that is done is not somethi=
ng the client should do.

Best,

Lars=20


From nobody Fri Sep  4 00:51:10 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98D71A8AC4 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 00:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_OFF=2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 trBBjICueqBE for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 00:51:08 -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 08CA71A1B8A for <urn@ietf.org>; Fri,  4 Sep 2015 00:51:08 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZXlm5-000DPz-RN; Fri, 04 Sep 2015 03:51:05 -0400
Date: Fri, 04 Sep 2015 03:51:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>, urn@ietf.org
Message-ID: <3C61ACA3278CFAB29281B727@JcK-HP8200.jck.com>
In-Reply-To: <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE>
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: <http://mailarchive.ietf.org/arch/msg/urn/IwkG71FtnZkiT_9m-HSXWcYbPPc>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 07:51:09 -0000

--On Wednesday, September 02, 2015 07:25 +0000 "Svensson, Lars"
<L.Svensson@dnb.de> wrote:

>...
> This is where we differ: In my opinion the resolver needs to
> know what "I2C" means, whom to ask for the URC and how to
> build the request.
>...

Lars,

Perhaps there is a source of misunderstanding here.  Despite the
early model of URLs, URCs, and URNs, as far as I know, URCs have
never been seen in production use.  They were definitely not
included, even by vague handwaving, in RFC 3986.    

The URC situation is one of several reasons why I have been
resisting strong, normative, references to RFC 1737.  It states,
in a couple of places, that URCs are used for meta-information
but neither it nor, as far as I know, any other document actual
defines URC format and use.  In addition, the first paragraph of
the introduction of RFC 1937 contains the statement:

	"URNs are used for identification, URCs for including
	meta-information, and URLs for locating or finding
	resources."  

In practice, while the statement about URNs is true, a very
large fraction of the debates of the last several years has
ultimately been about the relationship and mapping between URNs
and actual objects and what one can do with that relationship
and mapping, activities that might be describes as "locating or
finding resources".  I may be wrong, but I think that bit of
confusion has been a source of comfort for those making the
claim that URNs are useless and unneeded, even if it is not an
actual source of that position.

Do you have examples of the actual existence of URCs and, if so,
where are they documented?

    john





From nobody Fri Sep  4 04:12:45 2015
Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDF71B3630 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 04:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.16
X-Spam-Level: 
X-Spam-Status: No, score=-0.16 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, MANGLED_OFF=2.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 5jG01Ab5SRvQ for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 04:12:41 -0700 (PDT)
Received: from nordpol.dnb.de (nordpol.dnb.de [193.175.100.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6547E1B2EBE for <urn@ietf.org>; Fri,  4 Sep 2015 04:12:41 -0700 (PDT)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by nordpol.dnb.de (Postfix) with ESMTP id 4B5048AE96; Fri,  4 Sep 2015 13:12:40 +0200 (CEST)
X-AuditID: 0a453fe7-f79136d0000011d7-22-55e97ca8daf9
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id E5.F7.04567.8AC79E55; Fri,  4 Sep 2015 13:12:40 +0200 (CEST)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Fri, 4 Sep 2015 13:12:39 +0200
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: John C Klensin <john-ietf@jck.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Usage of f-, q- and r-components
Thread-Index: AdDIQbL0NAceB7DfRNuZTediDm8aUwAl/SwABxxsXLAAYpUAAAALFuww
Date: Fri, 4 Sep 2015 11:12:39 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D0D4E21@dnbf-ex1.AD.DDB.DE>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE> <3C61ACA3278CFAB29281B727@JcK-HP8200.jck.com>
In-Reply-To: <3C61ACA3278CFAB29281B727@JcK-HP8200.jck.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.12.173]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA12TaUwTURSFfW0p09Knz2Hps4pLNZqoIAR+KDFADBoU4xKpGiDBwY5ttSyZ aSuLRlzApKKyJzQat6JiMCoxilGjNrjiFtDEJSjGBcFdg2Ak6rxOiwP/Tr57z8m58zKUnH4Z qKMsOTaWy2GseqVaoZ6f0BtxfFO3IerydTi7pG1AObtm+1dZoizZ7f4lS25v+CBfJktTzzWy VouD5WbFr1Gb751qCcirQ/nPP51TFoPnGidQURjFYs/OciDqMPzwxSkl0TRqAbjjVbITqAV9 DuALTa/kThBIKdF0/MVMVkLQfFxZ1uBdD0Yx+NBtp8IJKIHH4oFim7iyADdWuAOJVqApeFdP u5KsQJSCSzpTxPA+gI81/FCQHRWKw9e2VQUQDVA4Pn36gZxoOdLipnd9AWJLhN2XRI5RKO5+ /cfHJ+Lq6laluB+Fv9w/4PPOwEcPffBqiEbj23VvFOUg1CWJdUksLonFJbEcBIoTYCSfbYqO ZIyRRmNWpJFtAuJLdDWDPW1JHoAooNfAfX3vDXQA4+ALsj1gKSXTh8IMa7eBHpmVaywwM7w5 k7NbWV4fAg8XChgO4iy7dYN+PPzU3WWgtYOUt/N5lrWWXDufaeesHoApuWCtWU6sRqagkOVy xUAPGEsp9FpYcXFrKo1MjI3dwLJ5LOefrqYoPYZUkWAczbEmNn+dxWrzjwVfK2mDpBNvoUli IZ10MLyTjFJ5wGJKIxTbTPIhn8dk8xaTLzsY2tcLVOOn3txwmN4j5Ib54dDMO2CFTgtNJAyR DbM9Z7CrLgx+Lhe+8SjJgETqJsKUBMEwRsKHpvaAhcITBcMIkqsR/qf/HWn4ndwf5IPeiuMg SyqG+tjwrMXC24ZAVbz3YBtjkx4cF+892Ed9B8cSGOaHQ+N0xWB3aVnzo+THjpYn09KrJvxd unLmyc5btQYu88qq7MzWFz+D50XXeirfph2hF91NDd9fWXT1Y/T5p3DWDZdqStXZq7+CBkpn OOq/ZUymS7SdnC5tSWVGFlvfW1v+u+Vmf8dU47qeOYkbRzxbu7fi4JYg+Rn3QGujbFxqWtGY J/3LkmJW79AreDMTPV3O8cw/1ODJ1HIEAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/R1tQGNu9lchFD9VgYaM87Z2AH64>
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 11:12:43 -0000

John,

On Friday, September 04, 2015 9:51 AM, John C Klensin wrote:

> --On Wednesday, September 02, 2015 07:25 +0000 "Svensson, Lars"
> <L.Svensson@dnb.de> wrote:
>=20
> >...
> > This is where we differ: In my opinion the resolver needs to
> > know what "I2C" means, whom to ask for the URC and how to
> > build the request.
> >...
>=20
> Lars,
>=20
> Perhaps there is a source of misunderstanding here.  Despite the
> early model of URLs, URCs, and URNs, as far as I know, URCs have
> never been seen in production use.  They were definitely not
> included, even by vague handwaving, in RFC 3986.
>=20
> The URC situation is one of several reasons why I have been
> resisting strong, normative, references to RFC 1737.  It states,
> in a couple of places, that URCs are used for meta-information
> but neither it nor, as far as I know, any other document actual
> defines URC format and use.  In addition, the first paragraph of
> the introduction of RFC 1937 contains the statement:
>=20
> 	"URNs are used for identification, URCs for including
> 	meta-information, and URLs for locating or finding
> 	resources."
>=20
> In practice, while the statement about URNs is true, a very
> large fraction of the debates of the last several years has
> ultimately been about the relationship and mapping between URNs
> and actual objects and what one can do with that relationship
> and mapping, activities that might be describes as "locating or
> finding resources".  I may be wrong, but I think that bit of
> confusion has been a source of comfort for those making the
> claim that URNs are useless and unneeded, even if it is not an
> actual source of that position.
>=20
> Do you have examples of the actual existence of URCs and, if so,
> where are they documented?

No, I have no such examples. I used the term "URC" only because of that is =
the reading of "C" in "U2C". What I meant was "whom [i. e. which service] t=
o ask for the metadata".

Sorry for any confusion my message might have caused.

Best,

Lars=20


From nobody Fri Sep  4 06:31:26 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562911B330A for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 06:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_OFF=2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 s5gCN0ec1_kC for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 06:31:19 -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 955EF1ACCE5 for <urn@ietf.org>; Fri,  4 Sep 2015 06:31:19 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZXr5K-000DuN-66; Fri, 04 Sep 2015 09:31:18 -0400
Date: Fri, 04 Sep 2015 09:31:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>
Message-ID: <EECF770A4EECA97BB201923B@JcK-HP8200.jck.com>
In-Reply-To: <24637769D123E644A105A0AF0E1F92EF010D0D4E21@dnbf-ex1.AD.DDB.DE>
References: <DB4PR07MB46089182301642447B9BCE7FA8E0@DB4PR07MB460.eurprd07.prod.outlook.com> <55B6FF2A.3060001@network-heretics.com> <24637769D123E644A105A0AF0E1F92EF010D0BFAA2@dnbf-ex1.AD.DDB.DE> <3C61ACA3278CFAB29281B727@JcK-HP8200.jck.com> <24637769D123E644A105A0AF0E1F92EF010D0D4E21@dnbf-ex1.AD.DDB.DE>
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: <http://mailarchive.ietf.org/arch/msg/urn/OEXEk6fOF3mXc7BrUDutyxTkkCU>
Cc: urn@ietf.org
Subject: Re: [urn] Usage of f-, q- and r-components
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 13:31:25 -0000

--On Friday, September 04, 2015 11:12 +0000 "Svensson, Lars"
<L.Svensson@dnb.de> wrote:

>> Do you have examples of the actual existence of URCs and, if
>> so, where are they documented?
> 
> No, I have no such examples. I used the term "URC" only
> because of that is the reading of "C" in "U2C". What I meant
> was "whom [i. e. which service] to ask for the metadata".
> 
> Sorry for any confusion my message might have caused.

Lars,

Not a problem.   The alphabet soup of many abbreviations and
acronyms sometimes gets intense in this area and, as I
mentioned, there have been suggestions that imply treating RFC
1737 as the authoritative statement about the scope of URNs and
what they are suppose to be about, so I just wanted to be sure I
understood what you meant and were referring to.

Thanks for the clarification.

best,
   john



From nobody Fri Sep  4 07:55:01 2015
Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB121B3BC8 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 07:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FbULwGEpB8iG for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 07:54:57 -0700 (PDT)
Received: from nordpol.dnb.de (nordpol.dnb.de [193.175.100.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5AAD41B3BE7 for <urn@ietf.org>; Fri,  4 Sep 2015 07:54:56 -0700 (PDT)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by nordpol.dnb.de (Postfix) with ESMTP id 6B3018B27C; Fri,  4 Sep 2015 16:54:55 +0200 (CEST)
X-AuditID: 0a453fe7-f79136d0000011d7-e8-55e9b0bf8821
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 48.C8.04567.FB0B9E55; Fri,  4 Sep 2015 16:54:55 +0200 (CEST)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Fri, 4 Sep 2015 16:54:54 +0200
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Section 3 (was: Re:  review of rfc2141bis-12)
Thread-Index: AQHQ5S5Zw/xy+SJLb0+dXTtANET/RJ4sdv4w
Date: Fri, 4 Sep 2015 14:54:54 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net>
In-Reply-To: <55E66B01.2070903@andyet.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.12.173]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA12Ta0hTYRjHec+Z2+vytePRzdfZdfQhimaGkZSYhoFh0NWulB7b0c3mHDub OPuQVnQFUcvMIVghGV103SS6UCwlU1CJbjSLyqhWeKEytcg6l82OfXv2e57///0/52GQpL+r dNBsdbB2K2PRK9UK9crlwwvuefyZC0+e0iZWDXcpEzvetZKJ1fuHiBQyvav3mSq9oWGMSK9q 37SW3KZOMrIWcxFrj0vOVptujPtDbC9UxbcGDxGloFZ5FIRCTCXg0bt3FVKtxT2vm3muhjTV CrDn8A8g/WgB+O3LX/yUCiqpeXjQdBRAGEWV4F7vekEaSaXggQc/RZsoKhV3l91QSSOLcE2t Q8AKag5+fvapSqgRlYF9dc9JoaapDfjWkRZCqEN570v33eIMoKZjj6dbnCGpaHz1w0iIlJLC DXckjikN9veNB/gsfOJEp1KaX4gHu+oD2vn43JkvpPRuBH5U+15RATRuma1bJnHLJG6Z5DRQ XADhXEFevIExGozGHIORvQqkk3y8Ccofp3kBBYE+DNWNfMqkQ5gizlXgBWsgodeg+ov+TDo8 p9DoMjGcKcvutLCcPgo1NvMYTeAcp2W3fgbq93/MpKMnKOfkbOZd5kInl+W0W7wAQ5KXxnoE qZFxlbD2QsnQC2KhQh+NKm+XbaSpPMbB7mZZG2sPdrdAqMfofRMvjLCzeWxxrtniCLZ5XYnQ oeQdMdBsKZBO3vg/EwFDvWA1DOODjQguiLMxBZw5L+AdicoEGhakou90tP0z76sNwsmeHSAL nh71XSZohbXQyuqiUY8YT5g2Oa0TuXVaNFDBf++psoZgr5uFMpbzghgZn/zCZ7CKP1ckcglH COP/ZP/y0qhGeGxKAIpxpyFWiKsJsP+9VvN3jkKhyeLyDsYhX35psrh8gAaWTxCgNggn2+lK QdM6pi5usS2nf+b5DVcKmjrbr7WtOF4eEluegAzf4MG+lLS98W/6xsbX/Pm9s7GlZ9rIJTh3 cMnOY762lJv1eLPPH0PseNBovmggRquGLddN+853zE068DC8bNme3MYnvtSnT15V3K7cU3o9 K3ZBas3W5ogER7VLsyK78qsmP9+XNqRXcCYmfh5p55i/Q1kcAIcEAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/lbKjEcoIEpJNMms8W7r569a4AOw>
Subject: Re: [urn] Section 3 (was: Re:  review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 14:54:59 -0000

On Wednesday, September 02, 2015 5:21 AM, Peter Saint-Andre - &yet wrote:
=20
> I have come to think that placing the r-component first has several
> advantages - it keeps the new URN-specific component syntactically
> separate from the existing URI components, everything after the
> r-component can be passed directly to a standard URL or query-string
> parser (without splitting things up or pulling out this strange new
> r-component thing from the middle), and as you note it enables the first
> character of a q-component to be "?".

Yes, but only if there is an r-component in the urn. If you only have

urn:example:foo??bar=3Dbaz

you cannot determine if the last nine characters should be interpreted as a=
n r-component "bar=3Dbaz" or a q-component "?bar=3Dbaz". It seems that we s=
till cannot allow the first character of the q-component to be '?' unless w=
e choose another character to delimit the r-component.

Or am I mistaken?

Best,

Lars=20


From nobody Fri Sep  4 09:15:27 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B1C1A9075 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 09:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 DuaAI8XQDcNf for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 09:15:24 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCDD11B3DB5 for <urn@ietf.org>; Fri,  4 Sep 2015 09:15:24 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 3977920909 for <urn@ietf.org>; Fri,  4 Sep 2015 12:15:24 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 04 Sep 2015 12:15:24 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=+uHPigyCicFulSE WSs1M4n3VuRE=; b=FzKZPxxkZniZqXgap5+9H9iOmYbAU2QJumMwvhqVVWe66tH 5MKkPQUjXaBPXsKXXYs8uj4KitQAv8ujxRkOmnGyPFIzQJslMnHJ9Mbxk9vNkCdI XT1Ry9v+MpW133q+26ygjGYTe1XUW7wTrOpvXzodzvNZg5ziu4y/w4q+NkC0=
X-Sasl-enc: hMobkRIkikKqbjpXlQq+uxC75SV7+8Rt6bTgXtlsg3gx 1441383324
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id C15DDC0028A; Fri,  4 Sep 2015 12:15:23 -0400 (EDT)
To: "Svensson, Lars" <L.Svensson@dnb.de>, Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55E9C38E.7040307@network-heretics.com>
Date: Fri, 4 Sep 2015 12:15:10 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/nG2h5blKiR7QfV8ru7TvnbNB0DQ>
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 16:15:26 -0000

On 09/04/2015 10:54 AM, Svensson, Lars wrote:
>> I have come to think that placing the r-component first has several
>> >advantages - it keeps the new URN-specific component syntactically
>> >separate from the existing URI components, everything after the
>> >r-component can be passed directly to a standard URL or query-string
>> >parser (without splitting things up or pulling out this strange new
>> >r-component thing from the middle), and as you note it enables the first
>> >character of a q-component to be "?".
> Yes, but only if there is an r-component in the urn. If you only have
>
> urn:example:foo??bar=baz
>
> you cannot determine if the last nine characters should be interpreted as an r-component "bar=baz" or a q-component "?bar=baz". It seems that we still cannot allow the first character of the q-component to be '?' unless we choose another character to delimit the r-component.
>
> Or am I mistaken?
I believe you are correct.


From nobody Fri Sep  4 10:41:26 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 267FB1ACDBC for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 10:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 mpNzEQEdGBf1 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 10:41:21 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB341B3AD8 for <urn@ietf.org>; Fri,  4 Sep 2015 10:41:20 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2F9E320AC1 for <urn@ietf.org>; Fri,  4 Sep 2015 13:41:20 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 04 Sep 2015 13:41:20 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=KQOcHyusqgQA9Hl tNCRp2iK3BUQ=; b=O8iKhBUQ4ZZfHYRSEYfLs/x3DcdBsCwu2XgFk5mffejae/A wwExUApa1rSLtATVKq1D6GzwSeDkQCv0F5nmqMgDqX+fOSjeLGfxUDmtxoUCJwRx HlfLX0ccoFY0CE8hY+BOujwWZGFqPpsL0kj3PhYEZzuh2iImxXkx4I36k2ug=
X-Sasl-enc: 0sRq7JA++b+0n4a+GkkCAdQ12JEhZR8r19vbnRgTSjft 1441388479
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id A9B31C0028D; Fri,  4 Sep 2015 13:41:19 -0400 (EDT)
To: Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55E9D7B3.6030206@network-heretics.com>
Date: Fri, 4 Sep 2015 13:41:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E905DC.1080209@andyet.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/5a7vV_4o-Wzaxu3oDo7L4-bWGQg>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 17:41:23 -0000

On 09/03/2015 10:45 PM, Peter Saint-Andre - &yet wrote:
> Here is proposed text (adding the second paragraph below):
>
>    This document modifies the syntax of the NSS to allow the following
>    characters: "/", "~", and "&".  In particular, allowing the "/"
>    character effectively makes it possible to encapsulate hierarchical
>    identifiers from other naming systems.  For instance, consider the
>    hypothetical example of a hierarchical naming system in which the
>    identifiers take the form of a series of numbers separated by the "/"
>    character, such as "1/406/47452/2".  If the naming authority for such
>    identifiers were to use URNs, it would be natural to place the
>    existing identifiers in the NSS, resulting in URNs such as
>    "urn:example:1/406/47452/2".
>
>    However, the foregoing changes to the syntax for the NSS do not
>    change the encoding rules for URN namespaces that were defined in
>    accordance with [RFC2141].  If any existing URN namespace that is
>    used outside of the URN context (i.e., as a standalone identifier
>    space) also allows the use of "/", "~", or "&" in the native form
>    within that identifier space, then the encoding rules for that
>    namespace are not changed by this specification.

Mostly looks good, though I think I would change the first sentence to 
say "... do not change the encoding rules for existing URN namespaces" 
because a reader doesn't have a good way to know whether a namespace 
registration was defined according to 2141 or not.

> I propose adding a new sentence to the very first paragraph of the 
> introduction:
>
>    A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
>    [RFC3986] that is assigned under the "urn" scheme and a particular
>    namespace, with the intent that the URN will be either a persistent,
>    location-independent resource identifier or in some cases an abstract
>    designator that is persistent but that does not identify a resource.
>    A URN namespace is a collection of such identifiers, each of which is
>    (1) unique, (2) assigned in a consistent and managed way, and (3)
>    assigned according to a common definition.  (Some URN namespaces
>    create names that exist only as URNs, whereas others create URNs out
>    of names that already exist in other identifier systems, such as
>    ISBNs [RFC3187] and ISSNs [RFC3044].)

Looks good.   (I assume those are informative references?   I have heard 
that they're likely to be updated soon and would hate for those updates 
to delay adoption of 2141bis.)

>
>>> In some sense there are two kinds of URN namespaces: those that exist
>>>  solely as URNs, and identifier spaces that exist independently of
>>> URNs.   The latter kind of identifier has a "native" form and a URN
>>> form, and its URN namespace registration should specify an algorithm
>>> for converting from native form to URN form.   Ideally this algorithm
>>>  produces a distinguished form of its input when converting it to URN
>>>  format - this makes it easier to build generic services that answer
>>>  queries for arbitrary URNs.   If the algorithm is just to use
>>> percent-encoding, that's fine, but IMO this should be explicitly
>>> specified in the namespace registration. I don't think we should
>>> unilaterally impose this algorithm for all identifier spaces.
>>
>> But do you think we should recommend it? This feels like one of those
>> situations where the creativity of the namespace registrant could lead
>> to bad results.

I don't think namespace registrants should be constrained to use percent 
encoding if there's a more readable and/or transcribable way to convert 
their names from native format to URN NSS format (say, by substituting 
one separator character for another).   I also think that (for similar 
reasons) imposing percent encoding as a constraint could discourage some 
namespaces from registering as URNs.   Perhaps that isn't a tragedy, 
since we probably can't expect that all persistent namespaces should be 
URNs anyway, but it seems unfortunate.

I also think it's very important that client software not assume that 
the way to translate native format names to URNs is to percent-encode 
them.   So encouarging the percent-encoding convention for this, or 
making it a SHOULD, actually seems harmful to me.
>
> I propose the following adjusted text:
>
>    Depending on the rules governing a namespace, names that are valid in
>    a namespace might contain characters that are not allowed by the
>    "pchar" production referenced above (e.g., characters outside the
>    ASCII range or characters that are reserved in URIs, such as "?", and
>    "#").  While such a string might be a valid name, it is not a valid
>    URN until it has been translated into a conformant NSS.  In the case
>    of URNs that are formed from names that exist separately in a
>    standalone identifier space, translation of an identifier from its
>    "native" format to URN format is accomplished by using the
>    canonicalization and encoding methods defined for that URN namespace.
>    Such methods SHOULD use percent-encoding unless the standalone
>    identifier space already defines different encoding rules for such
>    characters within the native format.  Software that is not aware of
>    those namespace-specific canonicalization and encoding rules MUST NOT
>    construct URNs from the names in the standalone identifier space.

I would remove the penultimate sentence, but otherwise fine.

>
>>> *7.* Last paragraph of section 3.2:
>>>
>>> CURRENT:
>>>
>>> If a namespace designates one or more characters conforming to the
>>> "pchar" rule as having special meaning for that namespace (e.g.,
>>> "@") and the namespace also uses that character in a literal sense,
>>> when used in a literal sense the character MUST be percent-encoded
>>> (e.g., "%40").  For related considerations with regard to NID
>>> registration, see Section 7.3.2.
>>>
>>>
>>> RECOMMENDED:
>>>
>>> If a namespace designates one or more characters conforming to the
>>> "pchar" rule as having special meaning for that namespace (e.g.,
>>> "@") and the namespace also uses that character in a literal
>>> sense,*that ***    *namespace registration MUST specify a means of
>>> representing *    *its native format*  *identifiers as URNs in a way
>>> that conforms *    *with the URN NSS grammar*.*See Section 7.3.2.*
>
> I propose the following adjusted text:
>
>    If a namespace designates one or more characters conforming to the
>    "pchar" rule as having special meaning for that namespace (e.g., "@")
>    and the namespace also uses that character in a literal sense, when
>    used in a literal sense the namespace registration MUST specify a
>    method of representing its native-format identifiers as URNs in a way
>    that conforms with the generic URN NSS grammar.  This method SHOULD
>    use percent-encoding unless the standalone identifier space already
>    defines different encoding rules for such characters.  For related
>    considerations with regard to NID registration, see Section 7.3.2.

As above, I would remove the penultimate sentence.

Keith


From nobody Fri Sep  4 11:00:00 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771FC1A1B81 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 10:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 mBu3baM8ZH2Y for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 10:59:56 -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 435541AC3B8 for <urn@ietf.org>; Fri,  4 Sep 2015 10:59:55 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZXvHA-000EJ8-7t; Fri, 04 Sep 2015 13:59:48 -0400
Date: Fri, 04 Sep 2015 13:59:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>
Message-ID: <A822453F1489C3FE635934DF@JcK-HP8200.jck.com>
In-Reply-To: <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE>
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: <http://mailarchive.ietf.org/arch/msg/urn/V9k6uTyzzVzbp3YwFoxNLm9KQVQ>
Cc: urn@ietf.org, Keith Moore <moore@network-heretics.com>, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3 (was: Re:  review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 17:59:58 -0000

--On Friday, September 04, 2015 14:54 +0000 "Svensson, Lars"
<L.Svensson@dnb.de> wrote:

> Yes, but only if there is an r-component in the urn. If you
> only have
> 
> urn:example:foo??bar=baz
> 
> you cannot determine if the last nine characters should be
> interpreted as an r-component "bar=baz" or a q-component
> "?bar=baz". It seems that we still cannot allow the first
> character of the q-component to be '?' unless we choose
> another character to delimit the r-component.
> 
> Or am I mistaken?

I believe you are correct... and this was one of the
considerations that led to the initial proposal/ decision to put
q-component first, after which one could make 3986-compatible
syntax restrictions and interpretation on what came within what
3986 would continue to consider a query but URNs would consider
a q-component followed by an r-component.

The explanation that follows is an abbreviated version of the
one I've been resisting trying to reconstruct, partially because
I haven't looked at, or had occasion to apply except via tools
that hide it, the theory involved carefully in some years and
can't be sure I've got the explanation below completely right.
Even then, I'm assuming that everyone in the WG understands LR
and LALR parsing at a level beyond what appears in tutorials for
various large bovine parser generators.  FWIW, I'm a lot less
comfortable trying to simulate a computer scientist at this
point in my career than pretending to be a network engineer, but
maybe the following will help albeit with apologies to those who
don't know the literature.

Consider the hypothetical, but often cited, generic URI parser
that breaks things into components with your string above and
with 

urn:example:foo?bar=baz
urn:example:foo??bar=baz?aaa?bbb=cdd

Doing this from memory, so excuse small errors, the generic URI
parse trees then look like

	Scheme: urn
	Hier-part: example:foo
	Query: ?bar=baz

	Scheme: urn
	Hier-part: example:foo
	Query: bar=baz

and

	Scheme: urn
	Hier-part: example:foo
	Query: ?bar=baz?aaa??bbb=cdd
	
Now, in all three cases, the Query is perfectly valid under
3986.  It is under the second too, but any ideas of being able
to pass r-component off to a separate processor without passing
through the query processor first essentially disappear.  Even
in the third case a URN-specific query processor cannot tell
unambiguously whether the r-component is "bbb=cdd" or the
entirety of "bar=baz?aaa??bbb=cdd".

Now, if r-component follows the q-component, then, while the
3986 syntax remains 

	scheme ":" hier-part [ "?" query ]

it is easy to imagine a URN-specific parser applied to the tree
the generic URI parser produces.   That parser, or at least part
of it, is needed anyway to separate NID from NSS.

So, for the "r-component after" model, the generic URN parser,
applied to the trees above, produces

	Scheme: urn
	NID: example
	NSS: foo
	q-component: ?bar=baz
	r-component: (empty)
       (because, at least as I first spelled it out, the
introducer for an r-component is two consecutive "??" _inside_
the query.  If one wanted

	q-component: (empty)
	r-component: bar=baz 

then one would need to write 

	urn:example:foo???bar=baz

which is an eyesore, but at least unambiguous.  The third case
is clear:

	Scheme: urn
	Hier-part: example:foo
	q-component: ?bar=baz?aaa
	r-component: bbb=cdd

One can decide that there is really no such thing as a generic
URI parser (at beyond separation of scheme from tail) and recast
things in LR terms.  But, that way, the "r-component second"
model requires only an LALR(1) engine because one needs to look
ahead only to see if another "?" (or a "#" is coming.  But
dealing with figuring out whether an r-component is actually
present in the "r-component before" case requires either
prohibiting any use of un-encoded "?" within the q-component or
an LR(k) engine for essentially arbitrary _k_ to determine
whether any question marks appear in the query and, if so,
whether it is doubled.

There are a number of parsing scenarios that don't raise any of
the above issues and that make the choice between "r-component
before" and "r-component after" either arbitrary or a matter of
taste.  But I have lost track of how many times the WG has been
told that there are generic URI parsers out there and that we
must design URNs so that they work.  I can find nothing in 3986
that prohibits such a parser from breaking the URI into
substrings (or tree nodes) and then passing those subtrees off
to action routine that do not have the ability to reconstruct
and then re-parse the whole URI string.

best,
   john


    john


From nobody Fri Sep  4 11:08:25 2015
Return-Path: <john@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D511B4504 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vGQPPOhqvyrd for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:08: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 BFE161A90BC for <urn@ietf.org>; Fri,  4 Sep 2015 11:08:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1ZXvP8-000EKN-6K; Fri, 04 Sep 2015 14:08:02 -0400
Date: Fri, 04 Sep 2015 14:07:57 -0400
From: John C Klensin <john@jck.com>
To: Keith Moore <moore@network-heretics.com>
Message-ID: <7F7E6E1E49855C2258EF6848@JcK-HP8200.jck.com>
In-Reply-To: <55E9D7B3.6030206@network-heretics.com>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net> <55E9D7B3.6030206@network-heretics.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@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/DhCXHYYdGMmwuj3QKUYS90nKY9k>
Cc: urn@ietf.org, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 18:08:23 -0000

--On Friday, September 04, 2015 13:41 -0400 Keith Moore
<moore@network-heretics.com> wrote:

> (Some URN namespaces
>>    create names that exist only as URNs, whereas others
>>    create URNs out of names that already exist in other
>>    identifier systems, such as ISBNs [RFC3187] and ISSNs
>>    [RFC3044].)
> 
> Looks good.   (I assume those are informative references?   I
> have heard that they're likely to be updated soon and would
> hate for those updates to delay adoption of 2141bis.)

They certainly look like informative references to me.  More to
the point, draft-ietf-urnbis-ns-reg-transition, also in the WG's
queue, discusses the fate of those documents and their
relationship to the URNBIS effort.   If you think it would be
helpful, we couple presumably incorporate a reference to it in
2141bis.  While it seems obvious that we need to get 2141bis
locked down before giving significant attention to the other two
pending specs (draft-ietf-urnbis-semantics-clarif being the
other one), I cannot imagine a scenario in which we did not try
to progress all three together.

    john




From nobody Fri Sep  4 11:19:12 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA351B2EC8 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 hhbwFdn1PQlF for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:19:09 -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 A6C861B2DB7 for <urn@ietf.org>; Fri,  4 Sep 2015 11:19:09 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZXvZr-000ELd-Nh; Fri, 04 Sep 2015 14:19:07 -0400
Date: Fri, 04 Sep 2015 14:19:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Keith Moore <moore@network-heretics.com>, urn@ietf.org
Message-ID: <8348EDB5A60ADA9A547FC8F7@JcK-HP8200.jck.com>
In-Reply-To: <55E905DC.1080209@andyet.net>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net>
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: <http://mailarchive.ietf.org/arch/msg/urn/dll9E4Cw-jatTbzxlR6BSUnCfsU>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 18:19:11 -0000

--On Thursday, September 03, 2015 20:45 -0600 Peter Saint-Andre
- &yet <peter@andyet.net> wrote:

>     Depending on the rules governing a namespace, names that
> are valid in
>     a namespace might contain characters that are not allowed
> by the
>     "pchar" production referenced above (e.g., characters
> outside the
>     ASCII range or characters that are reserved in URIs, such
> as "?", and
>     "#").

Peter,

I understand and appreciate the desire to be helpful, but please
be careful here because "reserved in URIs" is a tricky concept,
with some characters that are candidates for reservation within
schemes and some that are always reserved except when they
appear in specific context, such as left-to-right after an
appearance of the same character.   I'd hate to see us add to
the confusion.

Similarly,

> translation of an identifier from its
>     "native" format to URN format is accomplished by using the
>     canonicalization and encoding methods defined for that URN
> namespace.     Such methods SHOULD use percent-encoding unless
> the standalone     identifier space already defines different
> encoding rules for such     characters within the native
> format.  Software that is not aware of     those
> namespace-specific canonicalization and encoding rules MUST NOT
>     construct URNs from the names in the standalone identifier
> space.

I got a bad headache reading that out of context the first
couple of times.  If you are talking about the methods, they
don't "user percent-encoding", they interpret strings containing
percent signs as percent-encoding as, in turn, specified in RFC
3986 rather than interpreting the percent signs in some other
way (or not at all).

> If a namespace designates one or more characters conforming to
> the     "pchar" rule as having special meaning for that
> namespace (e.g., "@")     and the namespace also uses that
> character in a literal sense, when     used in a literal sense
> the namespace registration MUST specify a     method of
> representing its native-format identifiers as URNs in a way
> that conforms with the generic URN NSS grammar.

Is a sentence I could have written, one of the ones people claim
is incomprehensible on first (or even third or fourth) reading.
If you need it, please break it up into pieces.

I will probably have more to say about this (and maybe some more
specific suggestions) when I can see things in more context in
-13.

     john



    john




From nobody Fri Sep  4 11:26:02 2015
Return-Path: <john@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69471A702B for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 hGYGfwcp5A5E for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 11:26:00 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 DF3991A904A for <urn@ietf.org>; Fri,  4 Sep 2015 11:25:59 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1ZXvgT-000EMM-T3; Fri, 04 Sep 2015 14:25:57 -0400
Date: Fri, 04 Sep 2015 14:25:52 -0400
From: John C Klensin <john@jck.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, Keith Moore <moore@network-heretics.com>, urn@ietf.org
Message-ID: <2F3EF2E485D0E54A666EF271@JcK-HP8200.jck.com>
In-Reply-To: <55E66B01.2070903@andyet.net>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net>
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@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/zU0g4Tmg-8SEKcOXs4HuVIsKSXQ>
Subject: Re: [urn] Section 3 (was: Re:  review of rfc2141bis-12)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 18:26:00 -0000

--On Tuesday, September 01, 2015 21:20 -0600 Peter Saint-Andre -
&yet <peter@andyet.net> wrote:

>> b) The grammar refers to "q-string" etc. but the text refers
>> to "q-component" etc.  I could find no reason for the
>> discrepancy.
> 
> Editorial oversight, I think.

A bit more than that.   At one time, a distinction was made with
grammar that looked more like

     namestring  = assigned-name [ q-string ] ...
     q-string = "?" q-component
     ...

I don't remember whether I was worried about some difficulty
with clarity or if it was tied up with the treatment of "/" and
the former p-component idea.   In any event, when that was
simplified, I obviously didn't correctly realign it with the
text.   Mea Culpa... sorry.

Definitely safe to fix.

    john



From nobody Fri Sep  4 16:42:57 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADB01B3AA3 for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 16:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Lwk7hqSvwK-D for <urn@ietfa.amsl.com>; Fri,  4 Sep 2015 16:42:55 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E193C1B3A9E for <urn@ietf.org>; Fri,  4 Sep 2015 16:42:54 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 40AF0203DD for <urn@ietf.org>; Fri,  4 Sep 2015 19:42:54 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 04 Sep 2015 19:42:54 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=vSKT9mMH6xqQ+lG RseC/hFVTosU=; b=pIisHcjVd3mQ/+qLHXpxesFAEB3tV+F11UckAfnumTK6XcT ybqW0B5AO+WgHRYxX7GVkcqXjLbzHA1ixPbrW8Re4XV5iGEEa+RLMSFLHBxk0W1T 9sc/3mu6Y7viUCZigTB7l2cw8QpEmDH8GoRpjjemebsZ8H6DxX1HKuFU8AWM=
X-Sasl-enc: 4l83iCB+9J0RXSklZA1BZzH8GLFYWuVjRIhdiy4+qAMl 1441410174
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id ACC6E68017B; Fri,  4 Sep 2015 19:42:53 -0400 (EDT)
To: John C Klensin <john-ietf@jck.com>, "Svensson, Lars" <L.Svensson@dnb.de>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE> <A822453F1489C3FE635934DF@JcK-HP8200.jck.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55EA2C71.4000905@network-heretics.com>
Date: Fri, 4 Sep 2015 19:42:41 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <A822453F1489C3FE635934DF@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/KGSv41i8Ncx8bPfbdLA92r6Yxwg>
Cc: urn@ietf.org, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Sep 2015 23:42:56 -0000

On 09/04/2015 01:59 PM, John C Klensin wrote:
>
> --On Friday, September 04, 2015 14:54 +0000 "Svensson, Lars"
> <L.Svensson@dnb.de> wrote:
>
>> Yes, but only if there is an r-component in the urn. If you
>> only have
>>
>> urn:example:foo??bar=baz
>>
>> you cannot determine if the last nine characters should be
>> interpreted as an r-component "bar=baz" or a q-component
>> "?bar=baz". It seems that we still cannot allow the first
>> character of the q-component to be '?' unless we choose
>> another character to delimit the r-component.
>>
>> Or am I mistaken?
> I believe you are correct...

mostly so.   The "alternative 2" grammar I suggested is ambiguous 
because the parser doesn't know whether to reduce

'?' '?' pchar  -> '?' q-component

or

'?' '?' pchar -> r-component

and no amount of lookahead will resolve this conflict unless there is an 
additional '?' in the URN.

What this would mean in practice is that absent some explicit rule to 
resolve the ambiguity, different correct implementations might parse the 
same URNs in different ways, which would be bad.

> The explanation that follows is an abbreviated version of the
> one I've been resisting trying to reconstruct, partially because
> I haven't looked at, or had occasion to apply except via tools
> that hide it, the theory involved carefully in some years and
> can't be sure I've got the explanation below completely right.

Your explanation is basically correct as far as I can tell, though I 
didn't go through it with a fine-toothed comb.   However, IMO it's 
really not necessary for a URN parsing grammar to be LALR(1) or to limit 
lookahead to one symbol.   I expect that hardly anyone is going to use a 
parser generator to construct a URN parser, as this is easily 
accomplished with (say) regular expression libraries that are available 
in most modern programming languages.    Such libraries will do as much 
lookahead as needed.

Or if we resolved the ambiguity somehow (e.g. by saying that '?' may 
never appear as the first character of a query without percent-encoding 
it) an LALR(1) parser could parse it because these generally have some 
way to explicitly resolve reduce/reduce conflicts.

So the real problem with alternative 2 isn't the amount of lookahead 
required, it's the ambiguity in the grammar.   But at this point I'm not 
sure that alternative 2 (even with the ambiguity fixed) offers any 
advantage over alternative 1.

As for 3986 compatibility, I think we need to constrain URNs so that 
they are accepted as valid URNs by the 3986 grammar, but I don't think 
we need to worry too much about being compatible with how a 3986 parser 
breaks such a URN down into individual components.   Any software that 
actually tries to resolve URNs is going to need to know how to parse 
them according to 2141bis.

Keith


From nobody Sat Sep  5 03:13:50 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5F01B2B3C for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 03:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 t72xVuKROJaX for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 03:13:46 -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 5EF7F1B2AAF for <urn@ietf.org>; Sat,  5 Sep 2015 03:13:46 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZYATB-000GKI-Jp; Sat, 05 Sep 2015 06:13:13 -0400
Date: Sat, 05 Sep 2015 06:13:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, "Svensson, Lars" <L.Svensson@dnb.de>
Message-ID: <C13BC05B36E0B90DF0632002@JcK-HP8200.jck.com>
In-Reply-To: <55EA2C71.4000905@network-heretics.com>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE> <A822453F1489C3FE635934DF@JcK-HP8200.jck.com> <55EA2C71.4000905@network-heretics.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: <http://mailarchive.ietf.org/arch/msg/urn/NKK82MrOHkH_oWM8ktBDWLjDtG4>
Cc: urn@ietf.org, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Sep 2015 10:13:49 -0000

Keith,

I think your comments identify the very essence of the
disagreement we are having and the tradeoff choices the WG needs
to make.  That, AFIAC, is great progress.

Inline below.

--On Friday, September 04, 2015 19:42 -0400 Keith Moore
<moore@network-heretics.com> wrote:

> Your explanation is basically correct as far as I can tell,
> though I didn't go through it with a fine-toothed comb.
> However, IMO it's really not necessary for a URN parsing
> grammar to be LALR(1) or to limit lookahead to one symbol.   I
> expect that hardly anyone is going to use a parser generator
> to construct a URN parser, as this is easily accomplished with
> (say) regular expression libraries that are available in most
> modern programming languages.    Such libraries will do as
> much lookahead as needed.

I learned a lesson about IT Standards and implementations many
years ago, when the Internet was in its infancy.  A standard was
under development that was, necessarily, hundreds of pages long
and involved a three-level grammar and other sources of
complexity.  For various reasons, some similar to the reasons
XML2RFC has become popular in the IETF, the spec was written is
SGML.   There were GML and SGML libraries around, but, because
of SGML's flexibility, they were complex to use and took effort
to understand.  The folks on the standards development committee
were, however, almost all compiler experts.  The prediction was
that the committee either would rely on the editor for
compilation and work with the output text or would learn and use
those libraries.  I certainly made that prediction and was part
of the second group.  But it didn't work out that way: we ended
up with nearly as many implementations as there were members of
the committee.  The vast majority of them were not SGML
implementations, they were specific to the DTD and actions
required for the particular grammar and conventions needed for
the standard.  The reason?  Typically "we had the right tools
for building something like that in our compiler kits, they were
familiar and easy to apply, and we didn't have to learn a new
and complex package/ library".  Given the complexity of
multi-pass compiler-building toolsets, especially at the time,
that decision is both bizarre and completely rational.

The lesson: You may look at a spec and say "this will mostly be
implemented in regular expressions".  I might even agree.  But,
unless the standard is written with a requirement to implement
in a particular way, it is important to consider _all_ possible
rational implementation models and to understand the loss
functions associated with assuming one of them.

> Or if we resolved the ambiguity somehow (e.g. by saying that
> '?' may never appear as the first character of a query without
> percent-encoding it) an LALR(1) parser could parse it because
> these generally have some way to explicitly resolve
> reduce/reduce conflicts.

Oddly, this is another example of the above.  I recommend
DeRemer's dissertation and the DeRemer-Penello paper as
recreational reading.  If there are conflicts to be resolved,
either the grammar is LR(k) rather than LALR(k) (especially with
k= 0 or 1) or there are deficiencies or ambiguities in the
grammar that need to be resolved in other ways.  That doesn't
imply that no implementation has features to prioritize
constructions; several do.   However, the implementations aren't
the standard (or, in this case, the abstract model).

>...
> As for 3986 compatibility, I think we need to constrain URNs
> so that they are accepted as valid URNs by the 3986 grammar,
> but I don't think we need to worry too much about being
> compatible with how a 3986 parser breaks such a URN down into
> individual components.   Any software that actually tries to
> resolve URNs is going to need to know how to parse them
> according to 2141bis.

Well, I've believed all along that, in practice, all the
hypothetical generic URI parser is going to do is the most
superficial of pattern-conformance checks (if that) and then
pass the entire URI (or everything other than the scheme name)
string  to a scheme-specific parser.  That belief, along with
listening to many discussions about what real implementations do
in the wild, is why I keep putting "hypothetical" in front of
"generic URI parser".  That is completely consistent with the
above.   However, assume instead that the generic parser
actually breaks things up into the pieces specified in Section 3
of RFC 3096 and that it then either passes individual pieces off
to different action routines or calls on a scheme-specific
mechanism with separate pre-processed (e.g., to get rid of
"%"-encoding) elements [1].  We've been told that there are
implementations that do that.  Any implementation that handles
fragments in the scheme-independent way to which we've been told
URNs must conform has at least some properties of that approach.
In that model, there is still a 2141bis-specific processor, but
it never sees the original URI string, much less has a chance to
parse/interpret the component separation differently than 3986
does.

That, btw, is why I've tended to want to write the 2141bis
grammar along the lines of 

   URN = NID ":" NSS [ "?" query ] [ "#" f-component]
   query = [ q-component "??" r-component ]
     (or some r-component-before variation)

so that the 3986 syntax is clearly intact.  But the way in which
the ABNF is written is a lot less important than what we want
the syntax to be and whether this is compatible with
3986-conformant implementations.[2] 

best,
   john


[1] Many readings of 3986 and the proposed text for 2141bis
assume that the decision to interpret "%" as an encoding
indicator for a specific encoding can be per-scheme or even
per-NID.  As I understand it, WHATWG and at least some of the
IRI folks believe that interpretation is inherent to URIs and is
inescapable.  I can only note that the former group believes
that the definition of "generic URI parser" is "what browsers
do" and that, if we violate that definition, whatever we are
doing won't work in practice regardless of how we read 3986.

[2] I do not advocate going back to it, but this whole mess is
the reason why my initial instinct was "URNs are not URIs" -- a
decision that would, in essence, have acknowledged that there
was no such things as a generic URI parser beyond separation of
scheme from an opaque string and that 3986 was a guide to URI
scheme design, not a parsing or interpretation specification.
In that model, one really could say "URNs get parsed with a
2141bis-specific parser without interference from anything
URI-generic".  But, as long as we require that URNs be strictly
conformant to URI syntax as defined in 3986 and not get
crosswise with any possible 3986-conformant generic parsing
model, we are stuck with this situation.


From nobody Sat Sep  5 04:19:17 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1DA1B3F47 for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 04:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Q4qQcs3Xbajq for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 04:19:15 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 787281B3A30 for <urn@ietf.org>; Sat,  5 Sep 2015 04:19:15 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B299D20495 for <urn@ietf.org>; Sat,  5 Sep 2015 07:19:14 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 05 Sep 2015 07:19:14 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=BcFDZM3Oqo4ot7H MyoJKYc34Xxo=; b=VGAt+hR3swTTY3A91TGSLHcpAetBLpIj38MfcKVsaOmJe/f puf3K9tmEg7RnbEYS+QrNiqZwGYYEbQ6D406vl2/n7HhUZQEbIoIphFzLHds3558 axSoNuNq/Lef+t1Pjlva3nyE02iFWrZjWIujyhGm5nUr9Fzli9l/6hPgtXLE=
X-Sasl-enc: ILpjenEcV0m2TWfe3WaJSjzYUyxchiMnuAAI/AUUjnnd 1441451954
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E11D68012D; Sat,  5 Sep 2015 07:19:14 -0400 (EDT)
To: John C Klensin <john-ietf@jck.com>, "Svensson, Lars" <L.Svensson@dnb.de>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE> <A822453F1489C3FE635934DF@JcK-HP8200.jck.com> <55EA2C71.4000905@network-heretics.com> <C13BC05B36E0B90DF0632002@JcK-HP8200.jck.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <55EACFB0.9060200@network-heretics.com>
Date: Sat, 5 Sep 2015 07:19:12 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <C13BC05B36E0B90DF0632002@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/4NTCMCSPKw5hg0CyEIJKf_Zt3mM>
Cc: urn@ietf.org, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Sep 2015 11:19:16 -0000

On 09/05/2015 06:13 AM, John C Klensin wrote:
> Keith,
>
> I think your comments identify the very essence of the
> disagreement we are having and the tradeoff choices the WG needs
> to make.  That, AFIAC, is great progress.

I wasn't aware that we were still having a substantive disagreement 
about URN syntax choices, since I explicitly stated that I no longer see 
an advantage in alternative 2.   So I think that either we need to go 
with alternative 1 (despite its warts) or find another character to 
introduce r-components.   And I realize that there may be no characters 
available for that purpose that are compatible with 3986.



From nobody Sat Sep  5 05:09:59 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E4C1B5437 for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 05:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5r5bXTER6S43 for <urn@ietfa.amsl.com>; Sat,  5 Sep 2015 05:09:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 178021B5441 for <urn@ietf.org>; Sat,  5 Sep 2015 05:09:56 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZYCI2-000GSq-Nw; Sat, 05 Sep 2015 08:09:50 -0400
Date: Sat, 05 Sep 2015 08:09:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, "Svensson, Lars" <L.Svensson@dnb.de>
Message-ID: <5A358520D967FF6EE745C879@JcK-HP8200.jck.com>
In-Reply-To: <55EACFB0.9060200@network-heretics.com>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE> <A822453F1489C3FE635934DF@JcK-HP8200.jck.com> <55EA2C71.4000905@network-heretics.com> <C13BC05B36E0B90DF0632002@JcK-HP8200.jck.com> <55EACFB0.9060200@network-heretics.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: <http://mailarchive.ietf.org/arch/msg/urn/aF_eOOrErN7uChVg2ny1aVB0jA4>
Cc: urn@ietf.org, Peter Saint-Andre - &yet <peter@andyet.net>
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Sep 2015 12:09:57 -0000

--On Saturday, September 05, 2015 07:19 -0400 Keith Moore
<moore@network-heretics.com> wrote:

> On 09/05/2015 06:13 AM, John C Klensin wrote:
>> Keith,
>> 
>> I think your comments identify the very essence of the
>> disagreement we are having and the tradeoff choices the WG
>> needs to make.  That, AFIAC, is great progress.
> 
> I wasn't aware that we were still having a substantive
> disagreement about URN syntax choices, since I explicitly
> stated that I no longer see an advantage in alternative 2.
> So I think that either we need to go with alternative 1
> (despite its warts) or find another character to introduce
> r-components.   And I realize that there may be no characters
> available for that purpose that are compatible with 3986.

Philosophical disagreement, not a substantive one -- I've been
having trouble understanding you and considered that a problem
-- more or one if you were having equal trouble understanding
me.   

Back to Peter... and, fwiw, another of my objections to 3986 is
that it seems to have used up every plausible candidate
single-character delimiter.

best,
   john




From nobody Thu Sep 10 07:04:24 2015
Return-Path: <bs7652@att.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955BC1B5CBD for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 07:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.367
X-Spam-Level: 
X-Spam-Status: No, score=-0.367 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 XHKI3_mxmaBp for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 07:04:13 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 6E7F01B4F76 for <urn@ietf.org>; Thu, 10 Sep 2015 07:04:13 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id t8ADxca5043538 for <urn@ietf.org>; Thu, 10 Sep 2015 10:04:12 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0048589.ppops.net-00191d01. with ESMTP id 1wquydcp1j-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <urn@ietf.org>; Thu, 10 Sep 2015 10:04:12 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t8AE4Bet021975 for <urn@ietf.org>; Thu, 10 Sep 2015 10:04:11 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t8AE44BS021892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <urn@ietf.org>; Thu, 10 Sep 2015 10:04:04 -0400
Received: from GAALPA1MSGHUBAH.ITServices.sbc.com (GAALPA1MSGHUBAH.itservices.sbc.com [130.8.218.157]) by alpi132.aldc.att.com (RSA Interceptor) for <urn@ietf.org>; Thu, 10 Sep 2015 14:03:55 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.18]) by GAALPA1MSGHUBAH.ITServices.sbc.com ([130.8.218.157]) with mapi id 14.03.0248.002; Thu, 10 Sep 2015 10:03:55 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "urn@ietf.org" <urn@ietf.org>
Thread-Topic: questions on new namespace registrations
Thread-Index: AdDrzRTAt7MLZfkaToGy3ER7+gdzNw==
Date: Thu, 10 Sep 2015 14:03:54 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6113A9EBA38@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.81.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-09-10_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310000 definitions=main-1509100214
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/XbxpJ4MSXaHrkCBEnQ0cdldBrhI>
Subject: [urn] questions on new namespace registrations
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Sep 2015 14:04:15 -0000

Dear urnbis,
I've just joined this list after discovering that the urnbis WG is busy wor=
king on updates to the URN registration template and procedures. I read tha=
t one goal of urnbis is to avoid the occurrence of "squatting" on namespace=
s, by making the process easier.

I have a "friend" who was intending to start the registration process to as=
k for a new formal, registered namespace; but who has been "squatting" on 2=
 namespace NIDs (to publish widely used xsd and xml documents). I think my =
friend needs advice.

The 2 squatted namespace NIDs are derived from the current and former domai=
n names. Hypothetically, I'll call these "dslforum-org" and "broadband-foru=
m-org".

Would it make sense to register both of these once the new registration pro=
cess is in place?

My friend has expressed some sensitivity that these look nothing like curre=
ntly registered formal URNs (none of which have hyphens, and which are all =
shorter).=20
Would it make sense to register a new formal NID (for example, "bbf") that =
looks more like the other formally registered URNs? Or, if the squatted one=
s were to be registered, would those be just fine, and my friend should fee=
l no shame in the lengthy and hyphenated nature of those NIDs?

Thanks,
Barbara


From nobody Thu Sep 10 18:15:32 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5B41B3710 for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 18:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 UkJt9-9wwDDV for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 18:15:27 -0700 (PDT)
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D65A11B3616 for <urn@ietf.org>; Thu, 10 Sep 2015 18:15:15 -0700 (PDT)
Received: by iofb144 with SMTP id b144so82167207iof.1 for <urn@ietf.org>; Thu, 10 Sep 2015 18:15:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=HTvQwMjxGHVvBIRiZ9CbgOqvfdz+KA29Z4wuf4jxjx4=; b=lyGzjce4Y0deE6Rpc55uzzHTvJk9qcEJUJjRXmMYvtXM2uVYdAtDL0hQcjCy86891x u0Bha8da5f7Yot0fQnnACxa0kkNKisIe4z/q/WhEYSdPTGwtP4eD3x+a0rSBbfo9/MEU STFmptD7dH7NSznI6eZzzuJhMMbgN2xtPi8u/e/ZFSAWrVuF9YdoBatx1SwNoAY9QXaw Sz6yfhznnVxvfEsXeonsUKbMK8AgiyUnt5st/PcPnhrNsvK/u+lLEflRSf5RNX/HRkjE S8fp8qLwMKrWr+QGvwIgFaNDHi3jfB1iPoiRDhlUYnk8m0o2u3hlgaasVVBM4BrHnPct 5NMg==
X-Gm-Message-State: ALoCoQnlhKz7VbGcJFVZ7ozEbkKNhHTbWxJe71RtL4C0bXqZTYRbV70JDElK7FIE2C7a5M7n8XYd
X-Received: by 10.107.6.73 with SMTP id 70mr51400897iog.158.1441934114901; Thu, 10 Sep 2015 18:15:14 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:795f:a37b:a0c6:f9c8]) by smtp.googlemail.com with ESMTPSA id z5sm5462879igl.21.2015.09.10.18.15.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Sep 2015 18:15:14 -0700 (PDT)
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net> <55E9D7B3.6030206@network-heretics.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F22B21.4050301@andyet.net>
Date: Thu, 10 Sep 2015 19:15:13 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E9D7B3.6030206@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/wQem7JD_Xhqdxsy332iFagShT2M>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 01:15:29 -0000

On 9/4/15 11:41 AM, Keith Moore wrote:
> On 09/03/2015 10:45 PM, Peter Saint-Andre - &yet wrote:
>> Here is proposed text (adding the second paragraph below):
>>
>>    This document modifies the syntax of the NSS to allow the following
>>    characters: "/", "~", and "&".  In particular, allowing the "/"
>>    character effectively makes it possible to encapsulate hierarchical
>>    identifiers from other naming systems.  For instance, consider the
>>    hypothetical example of a hierarchical naming system in which the
>>    identifiers take the form of a series of numbers separated by the "/"
>>    character, such as "1/406/47452/2".  If the naming authority for such
>>    identifiers were to use URNs, it would be natural to place the
>>    existing identifiers in the NSS, resulting in URNs such as
>>    "urn:example:1/406/47452/2".
>>
>>    However, the foregoing changes to the syntax for the NSS do not
>>    change the encoding rules for URN namespaces that were defined in
>>    accordance with [RFC2141].  If any existing URN namespace that is
>>    used outside of the URN context (i.e., as a standalone identifier
>>    space) also allows the use of "/", "~", or "&" in the native form
>>    within that identifier space, then the encoding rules for that
>>    namespace are not changed by this specification.
>
> Mostly looks good, though I think I would change the first sentence to
> say "... do not change the encoding rules for existing URN namespaces"
> because a reader doesn't have a good way to know whether a namespace
> registration was defined according to 2141 or not.

I don't see much effective difference between "existing URN namespaces 
at the time of writing" and "namespaces registered before 2141bis is 
published as an RFC". However, I suppose that even a namespace 
registered after 2141bis is published an RFC could be defined in 
accordance with RFC 2141 syntax (e.g., perhaps it was defined years ago 
and only now registered). I think the pointer to 2141 syntax is more 
precise.

>> I propose adding a new sentence to the very first paragraph of the
>> introduction:
>>
>>    A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
>>    [RFC3986] that is assigned under the "urn" scheme and a particular
>>    namespace, with the intent that the URN will be either a persistent,
>>    location-independent resource identifier or in some cases an abstract
>>    designator that is persistent but that does not identify a resource.
>>    A URN namespace is a collection of such identifiers, each of which is
>>    (1) unique, (2) assigned in a consistent and managed way, and (3)
>>    assigned according to a common definition.  (Some URN namespaces
>>    create names that exist only as URNs, whereas others create URNs out
>>    of names that already exist in other identifier systems, such as
>>    ISBNs [RFC3187] and ISSNs [RFC3044].)
>
> Looks good.   (I assume those are informative references?   I have heard
> that they're likely to be updated soon and would hate for those updates
> to delay adoption of 2141bis.)

They sure look informative to me.

>>>> In some sense there are two kinds of URN namespaces: those that exist
>>>>  solely as URNs, and identifier spaces that exist independently of
>>>> URNs.   The latter kind of identifier has a "native" form and a URN
>>>> form, and its URN namespace registration should specify an algorithm
>>>> for converting from native form to URN form.   Ideally this algorithm
>>>>  produces a distinguished form of its input when converting it to URN
>>>>  format - this makes it easier to build generic services that answer
>>>>  queries for arbitrary URNs.   If the algorithm is just to use
>>>> percent-encoding, that's fine, but IMO this should be explicitly
>>>> specified in the namespace registration. I don't think we should
>>>> unilaterally impose this algorithm for all identifier spaces.
>>>
>>> But do you think we should recommend it? This feels like one of those
>>> situations where the creativity of the namespace registrant could lead
>>> to bad results.
>
> I don't think namespace registrants should be constrained to use percent
> encoding if there's a more readable and/or transcribable way to convert
> their names from native format to URN NSS format (say, by substituting
> one separator character for another).

That's what SHOULD means here, I think.

>  I also think that (for similar
> reasons) imposing percent encoding as a constraint could discourage some
> namespaces from registering as URNs.   Perhaps that isn't a tragedy,
> since we probably can't expect that all persistent namespaces should be
> URNs anyway, but it seems unfortunate.
>
> I also think it's very important that client software not assume that
> the way to translate native format names to URNs is to percent-encode
> them.   So encouarging the percent-encoding convention for this, or
> making it a SHOULD, actually seems harmful to me.

Well this isn't a hill for me to die on so dropping the recommendation 
is fine with me.

>> I propose the following adjusted text:
>>
>>    Depending on the rules governing a namespace, names that are valid in
>>    a namespace might contain characters that are not allowed by the
>>    "pchar" production referenced above (e.g., characters outside the
>>    ASCII range or characters that are reserved in URIs, such as "?", and
>>    "#").  While such a string might be a valid name, it is not a valid
>>    URN until it has been translated into a conformant NSS.  In the case
>>    of URNs that are formed from names that exist separately in a
>>    standalone identifier space, translation of an identifier from its
>>    "native" format to URN format is accomplished by using the
>>    canonicalization and encoding methods defined for that URN namespace.
>>    Such methods SHOULD use percent-encoding unless the standalone
>>    identifier space already defines different encoding rules for such
>>    characters within the native format.  Software that is not aware of
>>    those namespace-specific canonicalization and encoding rules MUST NOT
>>    construct URNs from the names in the standalone identifier space.
>
> I would remove the penultimate sentence, but otherwise fine.

Sure.

>>>> *7.* Last paragraph of section 3.2:
>>>>
>>>> CURRENT:
>>>>
>>>> If a namespace designates one or more characters conforming to the
>>>> "pchar" rule as having special meaning for that namespace (e.g.,
>>>> "@") and the namespace also uses that character in a literal sense,
>>>> when used in a literal sense the character MUST be percent-encoded
>>>> (e.g., "%40").  For related considerations with regard to NID
>>>> registration, see Section 7.3.2.
>>>>
>>>>
>>>> RECOMMENDED:
>>>>
>>>> If a namespace designates one or more characters conforming to the
>>>> "pchar" rule as having special meaning for that namespace (e.g.,
>>>> "@") and the namespace also uses that character in a literal
>>>> sense,*that ***    *namespace registration MUST specify a means of
>>>> representing *    *its native format*  *identifiers as URNs in a way
>>>> that conforms *    *with the URN NSS grammar*.*See Section 7.3.2.*
>>
>> I propose the following adjusted text:
>>
>>    If a namespace designates one or more characters conforming to the
>>    "pchar" rule as having special meaning for that namespace (e.g., "@")
>>    and the namespace also uses that character in a literal sense, when
>>    used in a literal sense the namespace registration MUST specify a
>>    method of representing its native-format identifiers as URNs in a way
>>    that conforms with the generic URN NSS grammar.  This method SHOULD
>>    use percent-encoding unless the standalone identifier space already
>>    defines different encoding rules for such characters.  For related
>>    considerations with regard to NID registration, see Section 7.3.2.
>
> As above, I would remove the penultimate sentence.

Fine with me.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Sep 10 18:33:05 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 700D01B4FD9 for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 18:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 fRdKFLw4M5mj for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 18:33:01 -0700 (PDT)
Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84B511B44E0 for <urn@ietf.org>; Thu, 10 Sep 2015 18:33:01 -0700 (PDT)
Received: by ioii196 with SMTP id i196so82101203ioi.3 for <urn@ietf.org>; Thu, 10 Sep 2015 18:33:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=mAIH8wwpHPHIRb/usFq0fEbd3S8xyO6q31WSA/W0UYY=; b=aAsGCnWuur+kJoTDuOIFk7dvT97s9uXHV3G+V34+5TtL/gSOeVyX1yVri04YIWGxJN rhBeom5U1VvXIbEGZ0QGEpkvn5A0OoISHjZ2RZdq6ctxkkIx1BvMDCPY7qXSILOvyVt6 BTWmphVDHQBOLl/1HiycwyGcOnm4m6ay2LSVU0mWysYMiXnGIlHSt6NqNH8HIZTwoyBI MrhWaXYXHbCnDryRNVceLAzViFpCyVbYj+rsH8XLApbHbZ7a5JKXF/xlzXxKuYS2I9eZ qJiWCs2tiaeFNAaMNbc8ooeZIE0gX9ihAcwBlEZ/IxrvTc9CONLZ2GqM4LRALnvsKh81 EN3w==
X-Gm-Message-State: ALoCoQmTgXu2xZUcQNjOdj0Zl+iUgLO0DDRySAAj+CvL0R3wQ7rWJ40WzTzRFr9xZVoYWLFW4N7P
X-Received: by 10.107.7.41 with SMTP id 41mr69702426ioh.48.1441935180881; Thu, 10 Sep 2015 18:33:00 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id 20sm8400323iof.18.2015.09.10.18.33.00 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Sep 2015 18:33:00 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Keith Moore <moore@network-heretics.com>, urn@ietf.org
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net> <8348EDB5A60ADA9A547FC8F7@JcK-HP8200.jck.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F22F4C.1040003@andyet.net>
Date: Thu, 10 Sep 2015 19:33:00 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <8348EDB5A60ADA9A547FC8F7@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/XYggwrsaesZVqeqdnuwNd7h6nRs>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 01:33:03 -0000

On 9/4/15 12:19 PM, John C Klensin wrote:
>
>
> --On Thursday, September 03, 2015 20:45 -0600 Peter Saint-Andre
> - &yet <peter@andyet.net> wrote:
>
>>      Depending on the rules governing a namespace, names that
>> are valid in
>>      a namespace might contain characters that are not allowed
>> by the
>>      "pchar" production referenced above (e.g., characters
>> outside the
>>      ASCII range or characters that are reserved in URIs, such
>> as "?", and
>>      "#").
>
> Peter,
>
> I understand and appreciate the desire to be helpful, but please
> be careful here because "reserved in URIs" is a tricky concept,
> with some characters that are candidates for reservation within
> schemes and some that are always reserved except when they
> appear in specific context, such as left-to-right after an
> appearance of the same character.   I'd hate to see us add to
> the confusion.

I see your point. How about:

OLD

    or characters that are reserved in URIs, such as "?", and "#").

NEW

    or other disallowed characters such as "?" and "#").

We could even say:

    or the characters "/", "?", "#", "[", and "]").

> Similarly,
>
>> translation of an identifier from its
>>      "native" format to URN format is accomplished by using the
>>      canonicalization and encoding methods defined for that URN
>> namespace.     Such methods SHOULD use percent-encoding unless
>> the standalone     identifier space already defines different
>> encoding rules for such     characters within the native
>> format.  Software that is not aware of     those
>> namespace-specific canonicalization and encoding rules MUST NOT
>>      construct URNs from the names in the standalone identifier
>> space.
>
> I got a bad headache reading that out of context the first
> couple of times.  If you are talking about the methods, they
> don't "user percent-encoding", they interpret strings containing
> percent signs as percent-encoding as, in turn, specified in RFC
> 3986 rather than interpreting the percent signs in some other
> way (or not at all).

Keith suggested we drop that sentence entirely, which I'd find acceptable.

>> If a namespace designates one or more characters conforming to
>> the     "pchar" rule as having special meaning for that
>> namespace (e.g., "@")     and the namespace also uses that
>> character in a literal sense, when     used in a literal sense
>> the namespace registration MUST specify a     method of
>> representing its native-format identifiers as URNs in a way
>> that conforms with the generic URN NSS grammar.
>
> Is a sentence I could have written, one of the ones people claim
> is incomprehensible on first (or even third or fourth) reading.
> If you need it, please break it up into pieces.

I am not sure that we need it. In particular, I am not confident that I 
understand what RFC 2141 intended by the terms "special meaning" and 
"literal sense" (see Section 2.3.1 there):

    Namespaces MAY designate one or more characters from the URN
    character set 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 "%"-encoded if the character is not a reserved
    character.  Therefore, the process of registering a namespace
    identifier shall include publication of a definition of which
    characters have a special meaning to that namespace.

> I will probably have more to say about this (and maybe some more
> specific suggestions) when I can see things in more context in
> -13.

OK. I will keep plugging away so that we can publish -13. As a colleague 
of mine says, "ship and iterate".

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Sep 10 19:00:32 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8FB81B3E20 for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 19:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ypvdmGOu3Vxn for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 19:00:29 -0700 (PDT)
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469F61B3DA4 for <urn@ietf.org>; Thu, 10 Sep 2015 19:00:29 -0700 (PDT)
Received: by iofh134 with SMTP id h134so82896710iof.0 for <urn@ietf.org>; Thu, 10 Sep 2015 19:00:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=xCKhWiXxOu9UddXHw4p/uqO4Zj3GnxhcH0xJZp3mhwg=; b=Bc8JniyldAHR0aKOJLSwBDXmvcswaQDT31S+o1IXt+Q87/dTLelZpaEAQ7nWZx5Wrc DbQLjp7gJPO1Y0d7r+rhNMDMseaOl2BQSTbltiirdG/l/XDg9Zn0V+k3xxXHY2rYY2nv 8+W0xLPsC9qZ3/llYBiyTrfKFQrQBJcJomNkexfI3c3Mvo9UAC57vcmQrxV9ABDMHWQo UL43DAbZIrG66ewoDfcIvoxpgd/vt41WazBTOiakCrLpYufOIEDwgedOa9AXfswsHjUE DHA+sH7REGalE2uHVGipTyfg4T8o/uE5Hd1HH0g4yAyqJFzf9L2FyAz3hsyVhZl43LyN N66A==
X-Gm-Message-State: ALoCoQkLNBSZb6uThaRsflPoVIGF9AFxFDeVHAkIc8fMn5UdUN7HbgWqy0zT1AldCUy6QWLxom3B
X-Received: by 10.107.128.41 with SMTP id b41mr33780764iod.74.1441936828581; Thu, 10 Sep 2015 19:00:28 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id v3sm5559061igb.3.2015.09.10.19.00.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Sep 2015 19:00:27 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Keith Moore <moore@network-heretics.com>, "Svensson, Lars" <L.Svensson@dnb.de>
References: <559463C3.3030905@network-heretics.com> <55E66B01.2070903@andyet.net> <24637769D123E644A105A0AF0E1F92EF010D0D53CF@dnbf-ex1.AD.DDB.DE> <A822453F1489C3FE635934DF@JcK-HP8200.jck.com> <55EA2C71.4000905@network-heretics.com> <C13BC05B36E0B90DF0632002@JcK-HP8200.jck.com> <55EACFB0.9060200@network-heretics.com> <5A358520D967FF6EE745C879@JcK-HP8200.jck.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F235BA.9090901@andyet.net>
Date: Thu, 10 Sep 2015 20:00:26 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5A358520D967FF6EE745C879@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/GVLvXGMwoap0EJbfv8SUFexNOtw>
Cc: urn@ietf.org
Subject: Re: [urn] Section 3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 02:00:31 -0000

On 9/5/15 6:09 AM, John C Klensin wrote:
>
>
> --On Saturday, September 05, 2015 07:19 -0400 Keith Moore
> <moore@network-heretics.com> wrote:
>
>> On 09/05/2015 06:13 AM, John C Klensin wrote:
>>> Keith,
>>>
>>> I think your comments identify the very essence of the
>>> disagreement we are having and the tradeoff choices the WG
>>> needs to make.  That, AFIAC, is great progress.
>>
>> I wasn't aware that we were still having a substantive
>> disagreement about URN syntax choices, since I explicitly
>> stated that I no longer see an advantage in alternative 2.
>> So I think that either we need to go with alternative 1
>> (despite its warts) or find another character to introduce
>> r-components.   And I realize that there may be no characters
>> available for that purpose that are compatible with 3986.
>
> Philosophical disagreement, not a substantive one -- I've been
> having trouble understanding you and considered that a problem
> -- more or one if you were having equal trouble understanding
> me.
>
> Back to Peter...

Thanks!

If we've decided to go with Keith's alternative 1, then your suggestion 
of ABNF along the following lines does seem reasonable:

    URN = NID ":" NSS [ "?" query ] [ "#" f-component]
    query = [ q-component "??" r-component ]

I'll see about adjusting the text along those lines...

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Sep 10 22:31:29 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A9BE1B341F for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 22:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9ToQx9PQV8Us for <urn@ietfa.amsl.com>; Thu, 10 Sep 2015 22:31:26 -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 0194E1B3429 for <urn@ietf.org>; Thu, 10 Sep 2015 22:31:26 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZaGvi-000DYJ-2S; Fri, 11 Sep 2015 01:31:22 -0400
Date: Fri, 11 Sep 2015 01:31:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <22C448033E60F83E3EBC307A@JcK-HP8200.jck.com>
In-Reply-To: <55F22F4C.1040003@andyet.net>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net> <8348EDB5A60ADA9A547FC8F7@JcK-HP8200.jck.com> <55F22F4C.1040003@andyet.net>
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: <http://mailarchive.ietf.org/arch/msg/urn/YzAsycFm18LAsdymubVtZllHdOU>
Cc: urn@ietf.org, Keith Moore <moore@network-heretics.com>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 05:31:28 -0000

--On Thursday, September 10, 2015 19:33 -0600 Peter Saint-Andre
- &yet <peter@andyet.net> wrote:

>...
>> Peter,
>> 
>> I understand and appreciate the desire to be helpful, but
>> please be careful here because "reserved in URIs" is a tricky
>> concept, with some characters that are candidates for
>> reservation within schemes and some that are always reserved
>> except when they appear in specific context, such as
>> left-to-right after an appearance of the same character.
>> I'd hate to see us add to the confusion.
> 
> I see your point. How about:
> 
> OLD
> 
>     or characters that are reserved in URIs, such as "?", and
> "#").
> 
> NEW
> 
>     or other disallowed characters such as "?" and "#").

I don't think that helps.  It might make things worse because it
doesn't provide a citation for "diaallowed characters".

> We could even say:
> 
>     or the characters "/", "?", "#", "[", and "]").

Perhaps:

	or the characters "/", "?", "#", "[", and "]",
	consistent with the restrictions in RFC 3986).

Not wonderful, but it lets us off the hook, avoids claims about
"reserved" or "disallowed", and points the finger squarely where
it belongs.

>> Similarly,
>> 
>>> translation of an identifier from its
>>>      "native" format to URN format is accomplished by using
>>>      the canonicalization and encoding methods defined for
>>>      that URN namespace.     Such methods SHOULD use
>>> percent-encoding unless the standalone     identifier space
>>> already defines different encoding rules for such
>>> characters within the native format.  Software that is not
>>> aware of     those
>>> namespace-specific canonicalization and encoding rules MUST
>>> NOT construct URNs from the names in the standalone
>>>      identifier space.
>> 
>> I got a bad headache reading that out of context the first
>> couple of times.  If you are talking about the methods, they
>> don't "user percent-encoding", they interpret strings
>> containing percent signs as percent-encoding as, in turn,
>> specified in RFC 3986 rather than interpreting the percent
>> signs in some other way (or not at all).
> 
> Keith suggested we drop that sentence entirely, which I'd find
> acceptable.

I do too.

>>> If a namespace designates one or more characters conforming
>>> to the     "pchar" rule as having special meaning for that
>>> namespace (e.g., "@")     and the namespace also uses that
>>> character in a literal sense, when     used in a literal
>>> sense the namespace registration MUST specify a     method of
>>> representing its native-format identifiers as URNs in a way
>>> that conforms with the generic URN NSS grammar.
>> 
>> Is a sentence I could have written, one of the ones people
>> claim is incomprehensible on first (or even third or fourth)
>> reading. If you need it, please break it up into pieces.
> 
> I am not sure that we need it. In particular, I am not
> confident that I understand what RFC 2141 intended by the
> terms "special meaning" and "literal sense" (see Section 2.3.1
> there):
> 
>     Namespaces MAY designate one or more characters from the
> URN
>     character set 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 "%"-encoded if the character is not
> a reserved
>     character.  Therefore, the process of registering a
> namespace
>     identifier shall include publication of a definition of
> which
>     characters have a special meaning to that namespace.

At least in some readings, earlier versions of URI/URL syntax
specs allowed more per-scheme syntax variations and restrictions
than many readers of RFC 3986 believe it allows.  If we can just
drop the comment and avoid being enmeshed in that discussion,
that would probably be the best solution.  While I dislike doing
this to readers in principle --especially given how hard 3986 is
to follow in places-- I think our decision to stick with 3986
syntax and some of the associated controversy suggests that we
should remove as much text as possible from 2141bis that merely
restates 3986 provisions or syntax unless we actually
need/intend to update it.

 
>> I will probably have more to say about this (and maybe some
>> more specific suggestions) when I can see things in more
>> context in -13.
> 
> OK. I will keep plugging away so that we can publish -13. As a
> colleague of mine says, "ship and iterate".

:-)
thanks,
   john



From nobody Fri Sep 11 05:53:42 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C3F1B4576 for <urn@ietfa.amsl.com>; Fri, 11 Sep 2015 05:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 9kuNiHubHLfk for <urn@ietfa.amsl.com>; Fri, 11 Sep 2015 05:53:36 -0700 (PDT)
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3FC81B45CD for <urn@ietf.org>; Fri, 11 Sep 2015 05:53:31 -0700 (PDT)
Received: by igcrk20 with SMTP id rk20so40638710igc.1 for <urn@ietf.org>; Fri, 11 Sep 2015 05:53:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ClC8732d3vTHwm/TXclqeypYQLu8qWkZ5qnd0HovI/U=; b=c49BMdqRZL12rY17Qor5gOwFtMUI6GLOFSziL5eecFpYmNL1SNaH8iBrTWMFCtdeb1 x1xAvt8CzSeLdQKHpnHaSeTRC7G+q1Mg2tnOx7iVZSNjuZfvnfmpuVYbuxQL2d9Q/3Ry euov1Kn0D7v4VhKr76qCNfV8/D0rx2dLsrhcg5KANVbW71SV33g4ibA/yG08U/2/ZCIg j6hDCPbTRbftFGgXFFTSykdUpLw8wu3p+puTznmP07C/0fUOL1cbtF0skYnKFi06xXv9 i0sb7sHC21In/1hbW9bvvWOqBE/+lLwQXzf3CZyer8YH29mInA4V/Q9sd99TUOus5BMV ntWw==
X-Gm-Message-State: ALoCoQlZw6PluW36jA1l4gSXlT/X6gAN+pXp8EYmPER9BVmJ86XtPKiF781iSoBW6pFiXAnuDNXk
X-Received: by 10.50.62.77 with SMTP id w13mr15839483igr.3.1441976010793; Fri, 11 Sep 2015 05:53:30 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id a4sm182831igh.16.2015.09.11.05.53.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Sep 2015 05:53:30 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>
References: <559463C3.3030905@network-heretics.com> <55E8DD7E.1020309@andyet.net> <55E905DC.1080209@andyet.net> <8348EDB5A60ADA9A547FC8F7@JcK-HP8200.jck.com> <55F22F4C.1040003@andyet.net> <22C448033E60F83E3EBC307A@JcK-HP8200.jck.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F2CECA.3060109@andyet.net>
Date: Fri, 11 Sep 2015 06:53:30 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <22C448033E60F83E3EBC307A@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/_1i4DyywLvSN_4AR1LyVbUieuu0>
Cc: urn@ietf.org, Keith Moore <moore@network-heretics.com>
Subject: Re: [urn] Section 3.2: NSS
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 12:53:38 -0000

On 9/10/15 11:31 PM, John C Klensin wrote:
>
>
> --On Thursday, September 10, 2015 19:33 -0600 Peter Saint-Andre
> - &yet <peter@andyet.net> wrote:
>
>> ...
>>> Peter,
>>>
>>> I understand and appreciate the desire to be helpful, but
>>> please be careful here because "reserved in URIs" is a tricky
>>> concept, with some characters that are candidates for
>>> reservation within schemes and some that are always reserved
>>> except when they appear in specific context, such as
>>> left-to-right after an appearance of the same character.
>>> I'd hate to see us add to the confusion.
>>
>> I see your point. How about:
>>
>> OLD
>>
>>      or characters that are reserved in URIs, such as "?", and
>> "#").
>>
>> NEW
>>
>>      or other disallowed characters such as "?" and "#").
>
> I don't think that helps.  It might make things worse because it
> doesn't provide a citation for "diaallowed characters".
>
>> We could even say:
>>
>>      or the characters "/", "?", "#", "[", and "]").
>
> Perhaps:
>
> 	or the characters "/", "?", "#", "[", and "]",
> 	consistent with the restrictions in RFC 3986).

WFM.

> Not wonderful, but it lets us off the hook, avoids claims about
> "reserved" or "disallowed", and points the finger squarely where
> it belongs.
>
>>> Similarly,
>>>
>>>> translation of an identifier from its
>>>>       "native" format to URN format is accomplished by using
>>>>       the canonicalization and encoding methods defined for
>>>>       that URN namespace.     Such methods SHOULD use
>>>> percent-encoding unless the standalone     identifier space
>>>> already defines different encoding rules for such
>>>> characters within the native format.  Software that is not
>>>> aware of     those
>>>> namespace-specific canonicalization and encoding rules MUST
>>>> NOT construct URNs from the names in the standalone
>>>>       identifier space.
>>>
>>> I got a bad headache reading that out of context the first
>>> couple of times.  If you are talking about the methods, they
>>> don't "user percent-encoding", they interpret strings
>>> containing percent signs as percent-encoding as, in turn,
>>> specified in RFC 3986 rather than interpreting the percent
>>> signs in some other way (or not at all).
>>
>> Keith suggested we drop that sentence entirely, which I'd find
>> acceptable.
>
> I do too.
>
>>>> If a namespace designates one or more characters conforming
>>>> to the     "pchar" rule as having special meaning for that
>>>> namespace (e.g., "@")     and the namespace also uses that
>>>> character in a literal sense, when     used in a literal
>>>> sense the namespace registration MUST specify a     method of
>>>> representing its native-format identifiers as URNs in a way
>>>> that conforms with the generic URN NSS grammar.
>>>
>>> Is a sentence I could have written, one of the ones people
>>> claim is incomprehensible on first (or even third or fourth)
>>> reading. If you need it, please break it up into pieces.
>>
>> I am not sure that we need it. In particular, I am not
>> confident that I understand what RFC 2141 intended by the
>> terms "special meaning" and "literal sense" (see Section 2.3.1
>> there):
>>
>>      Namespaces MAY designate one or more characters from the
>> URN
>>      character set 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 "%"-encoded if the character is not
>> a reserved
>>      character.  Therefore, the process of registering a
>> namespace
>>      identifier shall include publication of a definition of
>> which
>>      characters have a special meaning to that namespace.
>
> At least in some readings, earlier versions of URI/URL syntax
> specs allowed more per-scheme syntax variations and restrictions
> than many readers of RFC 3986 believe it allows.  If we can just
> drop the comment and avoid being enmeshed in that discussion,
> that would probably be the best solution.  While I dislike doing
> this to readers in principle --especially given how hard 3986 is
> to follow in places-- I think our decision to stick with 3986
> syntax and some of the associated controversy suggests that we
> should remove as much text as possible from 2141bis that merely
> restates 3986 provisions or syntax unless we actually
> need/intend to update it.

That seems eminently reasonable.

Peter



From nobody Fri Sep 11 07:52:25 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A2C1B4D58 for <urn@ietfa.amsl.com>; Fri, 11 Sep 2015 07:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 IshlRqhQLiab for <urn@ietfa.amsl.com>; Fri, 11 Sep 2015 07:52:21 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A99771B4D52 for <urn@ietf.org>; Fri, 11 Sep 2015 07:52:21 -0700 (PDT)
Received: by ioii196 with SMTP id i196so100529563ioi.3 for <urn@ietf.org>; Fri, 11 Sep 2015 07:52:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=QkS8xHdyDuX09snBKDJRkXar7+vSIGWOjMEOSNz26d0=; b=o1MbT6vxpGgNyK7uL4nBypP9EtABKAuJuNLKRHA6s7oH9EZOfG7Arx3oU/nDz2oqGN XYar4KfPOAx5ue0N32dpgRvPAUkkC7RMZ8q1rmieDZv5oBtC/K1+Boho9+GIJ6aecmRe DGsXOeI7qup9AW+QAZN1yjW0SPd7h0/rDXO5u2Ceiq7Isw8MggQHcwpndoisf+NeLHwt wHIaWD1ZJea0d+eqzRAF8IdnVJunBHaTP+A7hFIvC6riox/QghpE7VZ0hHmddY7Ea2xJ Dbq+Z+Fx8oLCE6X+JtfMhvyTMtytajHprUSgjtyXTjZWUm1yEJREH+miJfVpREGzZuiB ox3g==
MIME-Version: 1.0
X-Received: by 10.107.11.154 with SMTP id 26mr3002524iol.105.1441983140973; Fri, 11 Sep 2015 07:52:20 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.17.24 with HTTP; Fri, 11 Sep 2015 07:52:20 -0700 (PDT)
In-Reply-To: <20150911142142.19321.82949.idtracker@ietfa.amsl.com>
References: <20150911142142.19321.82949.idtracker@ietfa.amsl.com>
Date: Fri, 11 Sep 2015 10:52:20 -0400
X-Google-Sender-Auth: qesitlQOui5FtKXGusrPX5oBivg
Message-ID: <CAC4RtVDG=qEUca73UceXgyhcpOa7ATVNWmg2t+Lfua_Ep_=t5w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "urn@ietf.org" <urn@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/smgyYYhpKl0X-8RHKsCVJ_fIHtc>
Subject: [urn] Fwd: Last Call: <draft-blanchet-ccsds-urn-00.txt> (A Uniform Resource Name (URN) Namespace for the Consultative Committee for Space Data Systems (CCSDS)) to Informational RFC
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Sep 2015 14:52:23 -0000

URNbis denizens: Please note this last call, and please review and
comment on this request, as appropriate.  Especially consider any
issues related to the changes coming in 2141bis, as you review.
Please do make your comments on the main IETF discussion list, rather
than here, though discussion of 2141bis itself should stay here.

Thanks,
Barry


---------- Forwarded message ----------
From: The IESG <iesg-secretary@ietf.org>
Date: Fri, Sep 11, 2015 at 10:21 AM
Subject: Last Call: <draft-blanchet-ccsds-urn-00.txt> (A Uniform
Resource Name (URN) Namespace for the Consultative Committee for Space
Data Systems (CCSDS)) to Informational RFC
To: IETF-Announce <ietf-announce@ietf.org>



The IESG has received a request from an individual submitter to consider
the following document:
- 'A Uniform Resource Name (URN) Namespace for the Consultative Committee
   for Space Data Systems (CCSDS)'
  <draft-blanchet-ccsds-urn-00.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-10-09. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes a Uniform Resource Name (URN) namespace
   intended for persistently and uniquely naming resources published by
   the Consultative Committee for Space Data Systems (CCSDS).




The file can be obtained via
https://datatracker.ietf.org/doc/draft-blanchet-ccsds-urn/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-blanchet-ccsds-urn/ballot/


No IPR declarations have been submitted directly on this I-D.


From nobody Sun Sep 13 10:51:08 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BDD1B56CD for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 10:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 lyU63oDBDAJO for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 10:51:05 -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 665811B56C8 for <urn@ietf.org>; Sun, 13 Sep 2015 10:51:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZbBQd-000NyX-QA for urn@ietf.org; Sun, 13 Sep 2015 13:51:03 -0400
Date: Sun, 13 Sep 2015 13:50:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: urn@ietf.org
Message-ID: <65C29163B6F527DF836969A9@JcK-HP8200.jck.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: <http://mailarchive.ietf.org/arch/msg/urn/oR6NYgd0QK0qWD_44kbIYH5_2Yc>
Subject: [urn] Approval process for new URNs based on non-IETF standards
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 13 Sep 2015 17:51:07 -0000

Hi.
A recent request to register a URN associated with an external
standard involving a scientific community whose work lies well
outside the normal scope and expertise of the IETF brought up an
issue that I think we briefly discussed on-list but that never
made it into 2141bis.  The current particular issue involves
draft-blanchet-ccsds-urn-00.txt (A Uniform Resource Name (URN)
Namespace for the Consultative Committee for Space Data Systems
(CCSDS)) about which Barry wrote the WG earlier today.  


In the most general scenario of interest, a URN registration
request arrives from some specialized scientific or professional
community.  The IETF, and experts it designates, are generally
not in a good position to evaluate the request on the basis of
its subject matter.  We might offer advice about formats or
URN-specific issues but, ultimately, the right place to make the
decisions about the substantive matters and any tradeoffs is in
the relevant community, not the IETF.   Unfortunately, lack of
knowledge has never prevented the IETF community from having
opinions and expressing them loudly.  That can lead to
frustration and impatience on the part of the submitting
organization, reactions that, in turn, tend to discourage
registrations.

We encountered a similar issue in thinking about media types and
developed the idea of delegating most of the responsibility in
such situations to "recognized standards-related organization"
(see Section 3.1 of RFC 6838 for the current version, but
variations on the idea go back many years).  Adapting that model
to URNs seems wise to me.

If there is agreement about that as a principle, I suggest we
make approximately the following changes to Section 7 or
draft-ietf-urnbis-rfc2141bis-urn-12 (or equivalent, if Peter
gets -13 finished before agreement is reached on this):

  -----------

(1) At the end of Section 7.1, add:

	"While the registration templates are the same, slightly
	different procedures are used depending on the source of
	the registration."

(2) Change the title of Section 7.2 to "Registration Policy and
Process: Community Registrations".

(3) Add a new Section 7.3, titled "Registration Policy and
Process: Fast Track for Recognized Standards Development
Organizations and Scientific Societies" that reads:

	The IETF recognizes that situations will arise in which
	URN namespaces will be created to either embed existing
	and established standards or to reflect scientific
	knowledge, terminology, or information organization that
	lie well outside the IETF's scope or the likely subject
	matter knowledge of its Designated Experts.  In
	situations in which the registration request originates
	from, or is authorized by, a recognized
	standards-related organization or scientific society, a
	somewhat different procedure is available at the option
	of that body:
	
	1.  The namespace registration template is filled out
	and submitted as in steps 1 and 2 above.
	
	2. A specification is required that reflects of points
	to the needed external standards or specifications.
	Publication in the RFC Series or through an IETF process
	(e.g., posting as an Internet Draft) is not expected and
	would be appropriate only under very unusual
	circumstances.
	
	3.  The reviews on the discussion list and by the
	designated experts are, however, strictly advisory, with
	the decisions about what advice to accept and the length
	of time to allocate to the process strictly under the
	control of the external body.
	
	4.  When that body concludes that the application is
	sufficiently mature, they will request that IANA will
	complete the registration for the NID and IANA will do
	so.
	
	A similar model is available for recognized
	standards-related organizations registering Media Types.
	The document describing that mechanism [RFC6838]
	provides somewhat more information about the general
	concept.

(4) Renumber Section 7.3 and its subsections as appropriate.

(5) Add the following sentence to Section A.4:

If the registrant is a recognized standards development
organization or scientific society requesting the fact track
registration procedure (See Section 7.3), that information
should be clearly indicated in this section of the template.

  -----------

If this model is adopted, draft-ietf-urnbis-ns-reg-transition
will probably need some tuning but we can deal with that when
appropriate.

    john


From nobody Sun Sep 13 14:56:39 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8EF1B4A0B for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 14:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 y1jDnzQmhZwI for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 14:56:36 -0700 (PDT)
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39F461B4A08 for <urn@ietf.org>; Sun, 13 Sep 2015 14:56:36 -0700 (PDT)
Received: by igcpb10 with SMTP id pb10so77839347igc.1 for <urn@ietf.org>; Sun, 13 Sep 2015 14:56:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=D71VM5roElaDa5iySWBQusBGKrLRs4w01MUH5UzHUNE=; b=fwFJaUMoTh9m5164K2zqgR1Gh1wPsEEm/yUWHWSN8c0G3cNzkLshM0JOGdI57CamgV Scsc9ACzqK1acszCJmhcxjWmyfgMZ73B5JvFUZ9BbiEYbUIrCYQEaPVP9TaFUL68r/oF 3qnSBSGldPJLuBeHARMrKlbFfD2lKGO3mqwvKRRiw9NmwcuFHm8L2jaPulXvHqfx9qoR miSvqOGi0/I4kSb0R4etrQaS88F+q5kTIRzuaE5hEQc/Ou6SvtCgSR52Ga6rA6bFfLoP TF6jj/kncpJO3Xm5AwNE11vQ/zDvtisryLwfofiNpd/HAKuOcRzq3WTF4lCv3rBxAn8w aTtA==
X-Gm-Message-State: ALoCoQkYX8aFFfSXVxplu3uDOx4I6luLCLUYx6apwzmv5G1Bliw9a72L3EH7jNgYHSq6h4HLpj+8
X-Received: by 10.50.143.1 with SMTP id sa1mr13759184igb.32.1442181395312; Sun, 13 Sep 2015 14:56:35 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:84b7:bca2:8957:b371]) by smtp.googlemail.com with ESMTPSA id d3sm4347089igx.5.2015.09.13.14.56.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 Sep 2015 14:56:34 -0700 (PDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F5F110.8020007@andyet.net>
Date: Sun, 13 Sep 2015 15:56:32 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/ZC16B1XLqX3sugjM6itYlmxgCdI>
Subject: [urn] terminology
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 13 Sep 2015 21:56:37 -0000

To clarify the use of several terms, as well as to introduce early in 
the document the concept of resolving URNs into URLs, I propose that we 
add the following two paragraphs to Section 2:

    This document uses the terms "resolution" and "resolver" in roughly
    the sense from [RFC2276], i.e., "resolution" is the act of
    translating names into locators and a "resolver" is a service that
    translates names into locators.  In order to make that meaning clear,
    this document uses the term Uniform Resource Locator (URL), rather
    than the generic term Uniform Resource Identifier (URI), to refer to
    locators; see also Section 1.1.3 of [RFC3986].

    If a URN can theoretically or practically be resolved to one or more
    URLs, this document calls it a resource identifier in roughly the
    sense from [RFC3986].  If a URN cannot be so resolved, this document
    calls it an abstract designator.

RFC 2276 talks about URCs when describing the the concept of a resolver, 
which is why I've used the word "roughly" above. If we want to be more 
precise about where the roughness lies, we could add a few words about 
why URCs are not included in this model.

Peter


From nobody Sun Sep 13 15:15:41 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314891A1BB8 for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 15:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 l6HfBoOJx-Nh for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 15:15:38 -0700 (PDT)
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 285941A8869 for <urn@ietf.org>; Sun, 13 Sep 2015 15:15:38 -0700 (PDT)
Received: by ioii196 with SMTP id i196so147789061ioi.3 for <urn@ietf.org>; Sun, 13 Sep 2015 15:15:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=WO08hw24tY2SHVZcSOLXIXZoiI5oTadPklG+vG53hMI=; b=KZRpEwPbQIpxp7h7YG6b6L+Qsbg8xFG/T7NObfI9FGZrtdBKPEpcXFnmrSnxlzH9sl XkuRGfdZBKgWH/uL4Y1d7sMtT5BbLRZGevPsRFHq+eTcN/yacsY9UPuh6GX+g29vij8/ ouo62Jnl0zboVkog7SyJ3UmJtA+/pRRYS8FZ+hOQqTARSDDJiURlUypoXgN/Ud/g8O6Q QzJVyUVRPUlkgWhtgh6zlelsN/3GKrHAbUgZREYi6daGH0jFQC7Ki4ZngfMOZl0J49F8 JNubjI343qK+E6Kn1YP0yuGdZXRnMwOEkJKna9kz/Kac7b2PgcvYJW/XRRU4YjdFVTAJ pENw==
X-Gm-Message-State: ALoCoQna27UTbbFXLPEqdVjroiyfWD3YWSI/DKA0yLexcagsdLBhPL9YJ0pyu18FGXpC5gZG6uNb
X-Received: by 10.107.164.201 with SMTP id d70mr20735411ioj.127.1442182537429;  Sun, 13 Sep 2015 15:15:37 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:84b7:bca2:8957:b371]) by smtp.googlemail.com with ESMTPSA id hh9sm4359875igb.18.2015.09.13.15.15.36 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 Sep 2015 15:15:36 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, urn@ietf.org
References: <65C29163B6F527DF836969A9@JcK-HP8200.jck.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F5F587.2060207@andyet.net>
Date: Sun, 13 Sep 2015 16:15:35 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <65C29163B6F527DF836969A9@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/mYtA8iqjYaF3dogAJ9dv_E6ads0>
Subject: Re: [urn] Approval process for new URNs based on non-IETF standards
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 13 Sep 2015 22:15:40 -0000

On 9/13/15 11:50 AM, John C Klensin wrote:
> Hi.
> A recent request to register a URN associated with an external
> standard involving a scientific community whose work lies well
> outside the normal scope and expertise of the IETF brought up an
> issue that I think we briefly discussed on-list but that never
> made it into 2141bis.  The current particular issue involves
> draft-blanchet-ccsds-urn-00.txt (A Uniform Resource Name (URN)
> Namespace for the Consultative Committee for Space Data Systems
> (CCSDS)) about which Barry wrote the WG earlier today.
>
>
> In the most general scenario of interest, a URN registration
> request arrives from some specialized scientific or professional
> community.  The IETF, and experts it designates, are generally
> not in a good position to evaluate the request on the basis of
> its subject matter.  We might offer advice about formats or
> URN-specific issues but, ultimately, the right place to make the
> decisions about the substantive matters and any tradeoffs is in
> the relevant community, not the IETF.   Unfortunately, lack of
> knowledge has never prevented the IETF community from having
> opinions and expressing them loudly.  That can lead to
> frustration and impatience on the part of the submitting
> organization, reactions that, in turn, tend to discourage
> registrations.
>
> We encountered a similar issue in thinking about media types and
> developed the idea of delegating most of the responsibility in
> such situations to "recognized standards-related organization"
> (see Section 3.1 of RFC 6838 for the current version, but
> variations on the idea go back many years).  Adapting that model
> to URNs seems wise to me.
>
> If there is agreement about that as a principle, I suggest we
> make approximately the following changes to Section 7 or
> draft-ietf-urnbis-rfc2141bis-urn-12

Something along the lines of what you propose seems reasonable to me.

> (or equivalent, if Peter
> gets -13 finished before agreement is reached on this):

My goal is to get -13 published by the end of this week (i.e., September 
18th).

>    -----------
>
> (1) At the end of Section 7.1, add:
>
> 	"While the registration templates are the same, slightly
> 	different procedures are used depending on the source of
> 	the registration."
>
> (2) Change the title of Section 7.2 to "Registration Policy and
> Process: Community Registrations".
>
> (3) Add a new Section 7.3, titled "Registration Policy and
> Process: Fast Track for Recognized Standards Development
> Organizations and Scientific Societies" that reads:

I have two concerns about "scientific societies":

1. The IETF has experience in judging when another organization is an 
SDO, but not in judging when it is a scientific society.

2. It seems to me that the realm of organizations that might deserve to 
be on the fast track is not limited to scientific ones. What about 
organizations whose purpose is cultural (e.g., the British Museum), 
scholarly (e.g., the London Philological Society), educational (e.g., 
TERENA - see RFC 6338), governmental (e.g., the United Nations), 
military (e.g., NATO), charitable (e.g., Creative Commons), professional 
(various industry consortia), and so on?

> 	The IETF recognizes that situations will arise in which
> 	URN namespaces will be created to either embed existing
> 	and established standards or to reflect scientific
> 	knowledge, terminology, or information organization that
> 	lie well outside the IETF's scope or the likely subject
> 	matter knowledge of its Designated Experts.  In
> 	situations in which the registration request originates
> 	from, or is authorized by, a recognized
> 	standards-related organization or scientific society, a
> 	somewhat different procedure is available at the option
> 	of that body:
> 	
> 	1.  The namespace registration template is filled out
> 	and submitted as in steps 1 and 2 above.
> 	
> 	2. A specification is required that reflects of points
> 	to the needed external standards or specifications.
> 	Publication in the RFC Series or through an IETF process
> 	(e.g., posting as an Internet Draft) is not expected and
> 	would be appropriate only under very unusual
> 	circumstances.
> 	
> 	3.  The reviews on the discussion list and by the
> 	designated experts are, however, strictly advisory, with
> 	the decisions about what advice to accept and the length
> 	of time to allocate to the process strictly under the
> 	control of the external body.
> 	
> 	4.  When that body concludes that the application is
> 	sufficiently mature, they will request that IANA will
> 	complete the registration for the NID and IANA will do
> 	so.
> 	
> 	A similar model is available for recognized
> 	standards-related organizations registering Media Types.
> 	The document describing that mechanism [RFC6838]
> 	provides somewhat more information about the general
> 	concept.
>
> (4) Renumber Section 7.3 and its subsections as appropriate.
>
> (5) Add the following sentence to Section A.4:
>
> If the registrant is a recognized standards development
> organization or scientific society requesting the fact track
> registration procedure (See Section 7.3), that information
> should be clearly indicated in this section of the template.
>
>    -----------

Aside from the questions I raise above, this model seems reasonable to me.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Sun Sep 13 21:54:29 2015
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BBA1B5C29 for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 21:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 n3OmEJlYxTFn for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 21:54:25 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0750.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::750]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E55F1B5B6E for <urn@ietf.org>; Sun, 13 Sep 2015 21:54:24 -0700 (PDT)
Received: from AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) by AMSPR07MB456.eurprd07.prod.outlook.com (10.242.106.149) with Microsoft SMTP Server (TLS) id 15.1.268.17; Mon, 14 Sep 2015 04:54:06 +0000
Received: from AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) by AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) with mapi id 15.01.0268.017; Mon, 14 Sep 2015 04:54:06 +0000
From: "Hakala, Juha E" <juha.hakala@helsinki.fi>
To: Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] terminology
Thread-Index: AQHQ7m8Z9diqrBhCm0uwMT9LPGjABJ47b8yQ
Date: Mon, 14 Sep 2015 04:54:06 +0000
Message-ID: <AMSPR07MB454BD1586B695D98C9595A6FA5D0@AMSPR07MB454.eurprd07.prod.outlook.com>
References: <55F5F110.8020007@andyet.net>
In-Reply-To: <55F5F110.8020007@andyet.net>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=juha.hakala@helsinki.fi; 
x-originating-ip: [128.214.71.222]
x-microsoft-exchange-diagnostics: 1; AMSPR07MB456; 5:zjWoxz6C7XyNpKRUo8x9nX/hTNvBIbM/19dOWeHThHAXTb1CRViLO6p+kZYoTNSbowuPb3AB7pnddLJ8+IYuCf4C3cMnp0hU/LbPEXAcVzOtH8BXD6kpbpq9rVYWpWVWVzEbQ2eCvyt5vC7vp1vK2w==; 24:fF70vmRE5bUClSuzWVkBSxkN0Q6KPNxDoHp9lEKMSexUCzYRpak28B5KTpMtDceT5q9AM2br9toTsg0MWwP4CbV0cqetUIuZaWBbr53BUzU=; 20:H0Y54lWkEV327uIU/AlSuW4WKTJMXfgA71pbofjNW7IjT2/+0gecdgxWHa2MDLkEfOBnjBOgGrdU8CGveAw+dA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB456;
x-microsoft-antispam-prvs: <AMSPR07MB456AA5A8AB34F83604740D6FA5D0@AMSPR07MB456.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(8121501046)(3002001); SRVR:AMSPR07MB456; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB456; 
x-forefront-prvs: 0699FCD394
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(13464003)(74482002)(66066001)(74316001)(19580405001)(46102003)(19580395003)(10400500002)(5001770100001)(5001830100001)(40100003)(62966003)(92566002)(77156002)(64706001)(5003600100002)(86362001)(122556002)(102836002)(68736005)(77096005)(15975445007)(81156007)(105586002)(2950100001)(101416001)(97736004)(4001540100001)(2900100001)(189998001)(87936001)(107886002)(33656002)(5001960100002)(5002640100001)(76576001)(5001920100001)(106356001)(106116001)(50986999)(76176999)(5004730100002)(2501003)(54356999)(5007970100001)(11100500001)(5001860100001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB456; H:AMSPR07MB454.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: helsinki.fi does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: helsinki.fi
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Sep 2015 04:54:06.2601 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 98ae7559-10dc-4288-8e2e-4593e62fe3ee
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB456
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/OD4MqctEgHwtlXA7w_-XIbbdU-k>
Subject: Re: [urn] terminology
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 14 Sep 2015 04:54:28 -0000

Hello Peter,=20

your definition of resolution is too narrow, since in addition to translati=
ng a name into locators resolvers are - or will be - able to do many other =
things as well. People who claim that resolution is an extra step which sho=
uld be avoided will get more ammunition into their hands if we are too mode=
st about what resolvers may do, so it is in our interest to leave room for =
future developments in our specification of resolution.=20

You might say something like this to provide a more polished definition and=
 still avoid mentioning URCs:=20

"... "resolution" is the act of supplying services related to the identifie=
d resource, such as translating the persistent name into 1-n current locato=
rs of the resource, or delivering resource metadata in an appropriate forma=
t. Resolution services are currently defined in [RFC2483]. In order to unde=
rline the difference between the names and locations, this document uses th=
e term Uniform Resource Locator (URL) rather than the generic term Uniform =
Resource Identifier (URI) to refer to locators; see also Section 1.1.3 of [=
RFC3986].=20

If there are or will be resolution services available for a URN, this docum=
ent calls it a resource identifier in roughly the sense from [RFC3986].  If=
 there is no intention to provide any resolution services, this document ca=
lls URN an abstract designator."

Best regards,

Juha =20

> -----Original Message-----
> From: urn [mailto:urn-bounces@ietf.org] On Behalf Of Peter Saint-Andre -
> &yet
> Sent: 14. syyskuuta 2015 0:57
> To: urn@ietf.org
> Subject: [urn] terminology
>=20
> To clarify the use of several terms, as well as to introduce early in the
> document the concept of resolving URNs into URLs, I propose that we add t=
he
> following two paragraphs to Section 2:
>=20
>     This document uses the terms "resolution" and "resolver" in roughly
>     the sense from [RFC2276], i.e., "resolution" is the act of
>     translating names into locators and a "resolver" is a service that
>     translates names into locators.  In order to make that meaning clear,
>     this document uses the term Uniform Resource Locator (URL), rather
>     than the generic term Uniform Resource Identifier (URI), to refer to
>     locators; see also Section 1.1.3 of [RFC3986].
>=20
>     If a URN can theoretically or practically be resolved to one or more
>     URLs, this document calls it a resource identifier in roughly the
>     sense from [RFC3986].  If a URN cannot be so resolved, this document
>     calls it an abstract designator.
>=20
> RFC 2276 talks about URCs when describing the the concept of a resolver,
> which is why I've used the word "roughly" above. If we want to be more
> precise about where the roughness lies, we could add a few words about wh=
y
> URCs are not included in this model.
>=20
> Peter
>=20
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn


From nobody Sun Sep 13 22:24:27 2015
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD981B5D75 for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 22:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level: 
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 doFyqsGu9Exj for <urn@ietfa.amsl.com>; Sun, 13 Sep 2015 22:24:23 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0126.outbound.protection.outlook.com [104.47.126.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91F571B5C65 for <urn@ietf.org>; Sun, 13 Sep 2015 22:24:22 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [133.2.210.64] (133.2.210.64) by KAWPR01MB0131.jpnprd01.prod.outlook.com (10.161.27.12) with Microsoft SMTP Server (TLS) id 15.1.268.17; Mon, 14 Sep 2015 05:24:18 +0000
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>, Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
References: <55F5F110.8020007@andyet.net> <AMSPR07MB454BD1586B695D98C9595A6FA5D0@AMSPR07MB454.eurprd07.prod.outlook.com>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <55F659FC.3010009@it.aoyama.ac.jp>
Date: Mon, 14 Sep 2015 14:24:12 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <AMSPR07MB454BD1586B695D98C9595A6FA5D0@AMSPR07MB454.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: TY1PR06CA0042.apcprd06.prod.outlook.com (25.164.91.52) To KAWPR01MB0131.jpnprd01.prod.outlook.com (25.161.27.12)
X-Microsoft-Exchange-Diagnostics: 1; KAWPR01MB0131; 2:lsYe1iBYsGUxrwPa2G03vUMklcuYm5g6uLaRHciiqGPL5BqNlA1KEeibeuB8Fj245q/IHoGaeNpU2sjmWzabRpDhxNDhjpjR/KPgW4lRK92JmGMrVuo05aiZFpzihCDgx1Caj68/vAUM3vvCRNJwGkoSOWZJeXBp7qUPDeJRexo=; 3:F6vTZTib/PEXsDTxRLuKA7Y0qrserBeMOvrXLqm180WxoYBJnLmC4OG5rXL/YpF8iOUi/G5fSqMT/BSbMK+/1DaEjiVmeYveHlYDbJjrb/Kb+hkG7NtMu/o4k/KIyxTUgX6hgYlRdBswL6y5fYucBQ==; 25:pkVkvL3pcw/ge7AehSd1Yf2xLvwjO5XTnMtEXY4wHNHvhKwgsbd3sgL7MdPtCoQJFwi4mVd9tPeSGR65POIDC8yeSgjlYlHeBTrt2A6O28fpU7jeFCYWq38NEjbyfJ8cXUFlEwKZCahZgqLuIcjO3Gh857SI52P3cVkPGOgdjVGW65t/lwY2k/qTn4AAX8BVviV4bLUW8Dd9RtIHzP/XX1ehU+fvFAfIGCoYHcTL9nl1bFXF/WG/dRe5T/0GYp6eKPHBy0q3msiTYQoZ2lM7bA==; 4:x8Eh3TcCU5nY1G/UXzWyKB9713pNXD9F48Tw6S/pLKTTyVYD1vj4xbNGnNIFxPP3NUVXGmUEqABKGiPps5AyVADx6bEJA+3uMxjASEcWgiEoMc3XtHvxGaFw1eDtnYob4HiRTpGJqNCz0Z1ur7dZQpWdyEVjx/lp0EcuscVvVkW2OLdtn90CHtsdli81AaP/NhkR5mg2Cg3/1XKb60TRq8G4rrFGN84Q+Q0NUZwIH8z32cMyOdXE++YVf+pSTDLw8ypCaFZkMSjiZW+P0nllwV9IIUuW6577xugfPm/IhsfOzFffSCyiY9NdV6VeO3hs
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:KAWPR01MB0131;
X-Microsoft-Antispam-PRVS: <KAWPR01MB0131278A345BE956E64662A8CA5D0@KAWPR01MB0131.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(5005006)(8121501046)(3002001); SRVR:KAWPR01MB0131; BCL:0; PCL:0; RULEID:; SRVR:KAWPR01MB0131; 
X-Forefront-PRVS: 0699FCD394
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(24454002)(189002)(479174004)(199003)(40100003)(5007970100001)(5001860100001)(5004730100002)(92566002)(50466002)(80316001)(50986999)(122386002)(59896002)(101416001)(33656002)(87266999)(65816999)(54356999)(76176999)(4001350100001)(81156007)(5001830100001)(5001770100001)(97736004)(4001540100001)(87976001)(86362001)(83506001)(74482002)(23676002)(46102003)(2501003)(5001960100002)(68736005)(107886002)(189998001)(106356001)(42186005)(105586002)(2950100001)(77096005)(64126003)(77156002)(62966003)(65806001)(65956001)(64706001)(66066001)(47776003)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:KAWPR01MB0131; H:[133.2.210.64]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtLQVdQUjAxTUIwMTMxOzIzOlJlS1lxbnlMZVlheG9DaDV1b2d6dG5UMGUv?= =?utf-8?B?WUowa0s2anVDK016amFZMDV1YU5TRVRCQ0REcGtJeWw4RE9BaXhYejhKU21L?= =?utf-8?B?RHlrdzl0K3E1MzhSQStrQk9rYzd3U3dKUTNZWG1vMVdMOEVIS3dwcXlGYXB6?= =?utf-8?B?Q1E5VDdybXAvS0VXdXV5SVhRQ25pTnR6bkdqVk8rVzZUUnNOeVUwNXJpcWR0?= =?utf-8?B?WUZoODJORFlZd2s4RmdZNmFLSlpxMktXaFJlU0JVYmFFYW1vcEFMc1F6aVp3?= =?utf-8?B?dXlpb1VnQTVCN0MvRklUTGZRa2N6STY1R3BwMEVRTWpxSUNTSDU4dkV6dDdh?= =?utf-8?B?c015RmtzSURmU1JhdGplSTZtWW56d3lzR0hQajYvYm1XRjkvd1BNNU5MWEFM?= =?utf-8?B?cjk0SGw5MVJMUWpyWmZYa2dBajFkTm9UNGZOUmUxTVhKNHpjakVNWU1rZXRT?= =?utf-8?B?UEUwdlNVc2M4UlhWakhBZmpLdDN1ZHBGdVZ3Mzg4dmZUMDFBSGVORk8xdmhI?= =?utf-8?B?anB2ZG5HNlRYZVlCOGlITVlqYzluSnhrUlJDd3NDS2l5SExTdTVWTkQzZjNs?= =?utf-8?B?YlpZMHJIRWhOVDFMMkdlTjFEZ1F4UTZQcjJXaTd5ZDZGd0t6d0kvM2x1NzlX?= =?utf-8?B?KzhVZG0yd0UxaGVsemdnLzdET3cydEVTaGRSc012bGxITzVNaWxSY282bm9v?= =?utf-8?B?QlM4QUYwVEZQQ3ZTNEQxTC9QTU9YY0VEYnNteUkzZUVlTVJUc3pRcSthbVRV?= =?utf-8?B?WVRGSTRwTFJZSkUweWs3a2k2NGNpOVFjMzBKUEhxbWhmWENLYitzRmdFUllI?= =?utf-8?B?ZzBrU3JtMnpsRkh3YmRTV08ycmNWQitQeFYrV1FpbjdwbFFSeXEvYzRBODRQ?= =?utf-8?B?anlqeXMwUGNjMlgxaDNlait5VEptaUZJWFF6SWRaUmRLT2w3cXZGalBNUkY4?= =?utf-8?B?Ujd3UE9UVHgxdUgzVWw2L3ZzSGUvMGFrQjQxUGtwU0RrVEozY04rWnNkYUE3?= =?utf-8?B?TTc0RHphb3VMRGFJR1duWmFyMFBKYlRBUGFHNkhnUmFoZXhhQW5BMG1OcjJa?= =?utf-8?B?ZFE0MDM5bDhrTmpwei9ZTXlPQmxVNkU0ZG1ZWDFocEFTVGdBbk10dHE5dW5s?= =?utf-8?B?WDU1YU05WkFIZ01WQXJobHlJR1NwV2oxR2IxMGpBOTBMbXQwMmQySEhIVWhz?= =?utf-8?B?SG0rZVhvWnR4bnNHYThhUHNUaU5EWkJKd29KeVhDcXRGWEFxb1JhV1A0Tzhl?= =?utf-8?B?YWpidHIwb0JZbFZqYjBmall1U1Y0cmJjdkFDampPMFFMek5Id3Q0bHhWdjdH?= =?utf-8?B?cWRaOTlRR1ZlSHhsZ0xzMlRSVHhianNVdG5SekNvYnphR0ppVjRpQnFHS3A2?= =?utf-8?B?ak9ka2tDUDFtVXJZeklEdWZpa3RoRHhjM2V3YXg4bEhldXJ5bUFxRDd4L1pt?= =?utf-8?B?SVVDK2ZqQTRla3VRcUlLaHVhdTNWRS9GaHo0ZFc3S0t1NGJCZjkxU012RGZr?= =?utf-8?B?Wll3bXlHRnZidm14dWJTam4yL3hNSWxXQ0c3QkF5a1lqbGNqMHNrbUNjdHA3?= =?utf-8?B?MEczTTVsL2phVkdsVVdGeUYya3hmaEU1VWlXV2JKYmRMMmZzck1LZEFBNG1X?= =?utf-8?B?VUNNbS9WbEYrS05nM2JWNkdrTStZSDM1UnYyTFpnc0hnb2pIRnpjRzFKU1px?= =?utf-8?B?UnFpUUI2bkdjeVprcXBpbVpHSjJVRTF2NXRnTDhrSXJnNnhURGFlMG9IZy9W?= =?utf-8?B?TlZrTmJNc2JaYnRjTEthZG1KK0NONitvMG5vVi9BMW51QWc0ZzVCUnIwektQ?= =?utf-8?B?em4veGlIY1lJQkFudVZyRWV4b0ZlbDQzbm9wbUhmR25YMlhBNTFWZS9LLzVR?= =?utf-8?Q?CRiUHt88gJnLxMWYoOMUhYkJWqpDOBtC?=
X-Microsoft-Exchange-Diagnostics: 1; KAWPR01MB0131; 5:jEUEa02yx8z/1xf12zj75KEWt72c8e4mt5tFAEndfC3vrkCy1fZ4b/BXeMeP2ci341ZkaOgtHq9A3IOaybFORFuQHhJ839r2RNyxxjWJmqFtTDYyVv6kyaF05leA6zNUxdk7/3TlbXgZRkjxHfGDZw==; 24:fHgrQ+16aYKwUf7kGrMYkbE8b2jUyXTqznttyYpJxyo+81fomsORCAWQrHbpMCbSSdgNV8xQBB0Loxgb+AnsXKpBUtggN69HdXkQ8Jdu4eI=; 20:XVCfapeeF7YjuD952URFnuIQWzn07HR8hARwbb3a0sYSsGbEvseQFGwx+jLmLpP248VxoEvDr0lFqD+pPwvL5w==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Sep 2015 05:24:18.5102 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: KAWPR01MB0131
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/Hue7DgoPCP3peohXs8xJrU7CiBA>
Subject: Re: [urn] terminology
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 14 Sep 2015 05:24:25 -0000

On 2015/09/14 13:54, Hakala, Juha E wrote:
> Hello Peter,
>
> your definition of resolution is too narrow, since in addition to translating a name into locators resolvers are - or will be - able to do many other things as well. People who claim that resolution is an extra step which should be avoided will get more ammunition into their hands if we are too modest about what resolvers may do, so it is in our interest to leave room for future developments in our specification of resolution.
>
> You might say something like this to provide a more polished definition and still avoid mentioning URCs:
>
> "... "resolution" is the act of supplying services related to the identified resource, such as translating the persistent name into 1-n current locators of the resource, or delivering resource metadata in an appropriate format. Resolution services are currently defined in [RFC2483]. In order to underline the difference between the names and locations, this document uses the term Uniform Resource Locator (URL) rather than the generic term Uniform Resource Identifier (URI) to refer to locators; see also Section 1.1.3 of [RFC3986].
>
> If there are or will be resolution services available for a URN, this document calls it a resource identifier in roughly the sense from [RFC3986].  If there is no intention to provide any resolution services, this document calls URN an abstract designator."

Some grammar fixes are needed in the last paragraph:

- "calls it a resource" -> "calls the URN a resource"

- "calls URN an abstract designator" ->
   "calls the URN an abstract designator"

Regards,  Martin.


From nobody Mon Sep 14 08:14:58 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3834F1B2ED1 for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 08:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 YEkUV8-G36uE for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 08:14:55 -0700 (PDT)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A7731B41F7 for <urn@ietf.org>; Mon, 14 Sep 2015 08:14:55 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so92486231igb.0 for <urn@ietf.org>; Mon, 14 Sep 2015 08:14:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=JJGjre96ks2XHAXNFnjI0bZd56AkgSr6bpftDI9quSQ=; b=FyODfQVVqq+uFFILGjU/oQ0vILsiSxoBqWQXD+d+l9511DnhxeiBj1exm0GHrMyZMb TqHelZC/j5u65+ecj/GPVWpCXk1q59TNGDJSiJ4LgknfWTqTcQs4vKuvskzzKvTwe5tL k90UzXoikmFqAh+5AvVC4C/tf22OZL8u0ACB23PTtvr/PldgPVl+Umt+Ft4WUf8wBEQr jh3qRVDcys/QsdFUlaF5MMMBgQfnka4MfQmHjaiLC6Q8tmuKMdsSUCzFDpQJ3qUcTnTe X+A/4f4KysHhVmVG3AVjxAg+WRgv01LvHJ9HnLu6k2MSafNMmt8OAsVhjYWxq1RNyyDp MBtw==
X-Gm-Message-State: ALoCoQlBDqiRAuYEQHWBY2zNM6mUydtnwweUnQ3X8ero4A1Irr+7BiqK1Do5pKwDggpA3YG2DEeF
X-Received: by 10.50.124.39 with SMTP id mf7mr18100509igb.36.1442243694505; Mon, 14 Sep 2015 08:14:54 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:4181:f22:ef58:94fe]) by smtp.googlemail.com with ESMTPSA id m18sm6057334ioi.44.2015.09.14.08.14.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Sep 2015 08:14:54 -0700 (PDT)
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>, "urn@ietf.org" <urn@ietf.org>
References: <55F5F110.8020007@andyet.net> <AMSPR07MB454BD1586B695D98C9595A6FA5D0@AMSPR07MB454.eurprd07.prod.outlook.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F6E46D.7070800@andyet.net>
Date: Mon, 14 Sep 2015 09:14:53 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <AMSPR07MB454BD1586B695D98C9595A6FA5D0@AMSPR07MB454.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/4Gl_MnIwXJBAmKQjZMtwt5ivoMI>
Subject: Re: [urn] terminology
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 14 Sep 2015 15:14:57 -0000

On 9/13/15 10:54 PM, Hakala, Juha E wrote:
> Hello Peter,
>
> your definition of resolution is too narrow, since in addition to translating a name into locators resolvers are - or will be - able to do many other things as well. People who claim that resolution is an extra step which should be avoided will get more ammunition into their hands if we are too modest about what resolvers may do, so it is in our interest to leave room for future developments in our specification of resolution.
>
> You might say something like this to provide a more polished definition and still avoid mentioning URCs:
>
> "... "resolution" is the act of supplying services related to the identified resource, such as translating the persistent name into 1-n current locators of the resource, or delivering resource metadata in an appropriate format. Resolution services are currently defined in [RFC2483]. In order to underline the difference between the names and locations, this document uses the term Uniform Resource Locator (URL) rather than the generic term Uniform Resource Identifier (URI) to refer to locators; see also Section 1.1.3 of [RFC3986].
>
> If there are or will be resolution services available for a URN, this document calls it a resource identifier in roughly the sense from [RFC3986].  If there is no intention to provide any resolution services, this document calls URN an abstract designator."

Yes, that is more descriptive. Thanks for the proposed text.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Mon Sep 14 20:13:24 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E7A1AD0B9; Mon, 14 Sep 2015 20:13:23 -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] autolearn=ham
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 zpNAigUfxqim; Mon, 14 Sep 2015 20:13:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DF51B32C7; Mon, 14 Sep 2015 20:13:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150915031322.25000.29830.idtracker@ietfa.amsl.com>
Date: Mon, 14 Sep 2015 20:13:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/LgkoopznpnKB6d52GiEgGPCKT7c>
Cc: urn@ietf.org
Subject: [urn] I-D Action: draft-ietf-urnbis-rfc2141bis-urn-13.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 03:13:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Uniform Resource Names, Revised Working Group of the IETF.

        Title           : Uniform Resource Names (URNs)
        Authors         : Peter Saint-Andre
                          John C Klensin
	Filename        : draft-ietf-urnbis-rfc2141bis-urn-13.txt
	Pages           : 32
	Date            : 2015-09-14

Abstract:
   A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
   that is assigned under the "urn" scheme and a particular URN
   namespace, with the intent that the URN will be either a persistent,
   location-independent resource identifier or in some cases an abstract
   designator that is persistent but that does not identify a resource.
   With regard to URN syntax, this document defines the canonical syntax
   for URNs (in a way that is consistent with URI syntax), specifies
   methods for determining URN equivalence, and discusses URI
   conformance.  With regard to URN namespaces, this document specifies
   a method for defining a URN namespace and associating it with a
   namespace identifier, and describes procedures for registering
   namespace identifiers with the Internet Assigned Numbers Authority
   (IANA).  This document obsoletes both RFC 2141 and RFC 3406.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-urnbis-rfc2141bis-urn-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep 14 20:19:31 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 107BF1B2E82 for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 20:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 xYNqc1N1bqog for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 20:19:27 -0700 (PDT)
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A77B1B2ADA for <urn@ietf.org>; Mon, 14 Sep 2015 20:19:27 -0700 (PDT)
Received: by igcrk20 with SMTP id rk20so6383626igc.1 for <urn@ietf.org>; Mon, 14 Sep 2015 20:19:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=02zrZ/+1F7kBt5z7eI/FU22J4H6WIg71L/de2ZEB9MM=; b=cxCsY+yQhBq+HcUe7Q55mMtMvDLg9v9W6We4+MPUxyMNr119ZZHyNsQLyQVlcxB7GW W7kjGFgJT9g78NLTeTjGEdFqjvMRsI1wq5CkeAn+fkKp1Wb4rSpmcGm5AgkY0Y+dQa9I 4P8D4+yx/TOizNwm3JG6keNU0JBLXpy9ieK5Ds9FVqyNOLFH8Cjg3MEDZv3JYa7h+rme mcVOKbIt3vBAX4ZJ6Cvjtc2Zr/Agc4O/QHUqR7UIuOJFe1ea6OOigWQCYReWOU8bec9i lVkNZ7Zh/UwRP8eJVTT9M9kWC/GLaosiy6XvS6xYnLrsJ+RNGd7d1R7I3FIC+kGSupEv eknA==
X-Gm-Message-State: ALoCoQn3zGI4azD6F6YVx8K15XeWn/M92Edr2AA06Z0jpctPbSM0IO/XfsSnJFC8vwdCb0jcgh1i
X-Received: by 10.50.41.71 with SMTP id d7mr1841500igl.79.1442287166568; Mon, 14 Sep 2015 20:19:26 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id s14sm2948413igr.15.2015.09.14.20.19.25 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Sep 2015 20:19:25 -0700 (PDT)
To: urn@ietf.org
References: <20150915031322.25000.29830.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F78E3E.7000103@andyet.net>
Date: Mon, 14 Sep 2015 21:19:26 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150915031322.25000.29830.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/RsmR0tVVevm-DTjFehsFPE5Kq_M>
Subject: Re: [urn] I-D Action: draft-ietf-urnbis-rfc2141bis-urn-13.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 03:19:29 -0000

In the interest of making progress toward consensus, I decided to submit 
-13.

Please note that I held the pen on this version, and that John might not 
agree with all the changes I've made!

In particular, I made a somewhat experimental change to the ABNF and 
immediately after hitting "submit" I realized that I should have thought 
about it more and discussed it on the list before submitting -13. 
(That's what I get for submitting an I-D after a 14-hour work day.)

I would be happy to be corrected and will endeavor to publish -14 soon 
based on list discussion of the text, examples, ABNF, etc.

Peter

On 9/14/15 9:13 PM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Uniform Resource Names, Revised Working Group of the IETF.
>
>          Title           : Uniform Resource Names (URNs)
>          Authors         : Peter Saint-Andre
>                            John C Klensin
> 	Filename        : draft-ietf-urnbis-rfc2141bis-urn-13.txt
> 	Pages           : 32
> 	Date            : 2015-09-14
>
> Abstract:
>     A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)
>     that is assigned under the "urn" scheme and a particular URN
>     namespace, with the intent that the URN will be either a persistent,
>     location-independent resource identifier or in some cases an abstract
>     designator that is persistent but that does not identify a resource.
>     With regard to URN syntax, this document defines the canonical syntax
>     for URNs (in a way that is consistent with URI syntax), specifies
>     methods for determining URN equivalence, and discusses URI
>     conformance.  With regard to URN namespaces, this document specifies
>     a method for defining a URN namespace and associating it with a
>     namespace identifier, and describes procedures for registering
>     namespace identifiers with the Internet Assigned Numbers Authority
>     (IANA).  This document obsoletes both RFC 2141 and RFC 3406.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-13
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-urnbis-rfc2141bis-urn-13
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn
>


From nobody Mon Sep 14 23:36:07 2015
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602FD1A1A1C for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 23:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level: 
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 1CdGS0G34_hP for <urn@ietfa.amsl.com>; Mon, 14 Sep 2015 23:36:03 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0114.outbound.protection.outlook.com [104.47.125.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A45661A014B for <urn@ietf.org>; Mon, 14 Sep 2015 23:36:02 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [133.2.210.64] (133.2.210.64) by OS2PR01MB0138.jpnprd01.prod.outlook.com (10.161.77.146) with Microsoft SMTP Server (TLS) id 15.1.268.17; Tue, 15 Sep 2015 06:35:58 +0000
To: John C Klensin <john-ietf@jck.com>, <urn@ietf.org>
References: <65C29163B6F527DF836969A9@JcK-HP8200.jck.com>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <55F7BC49.6090505@it.aoyama.ac.jp>
Date: Tue, 15 Sep 2015 15:35:53 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <65C29163B6F527DF836969A9@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: TY1PR06CA0007.apcprd06.prod.outlook.com (25.164.91.17) To OS2PR01MB0138.jpnprd01.prod.outlook.com (25.161.77.146)
X-Microsoft-Exchange-Diagnostics: 1; OS2PR01MB0138; 2:dt20yYZg2E5vDS1c1hOwyM+2lu3jGg9cnLQrghhvuRuOgvhJDQJH0zAolq91vEQROafq2NYT0P2M/PLtW8LaP8lX/ULVPjH5u7VhMVdVkPdliSCuKsJdGXC8/kDJd0rVE2Qp/ZWGCvcDWEtKMf9BQxCrRcrucHdD+9kqFz25/ZU=; 3:BnnkiML9scE8/iZ+BOtuMoR1UPXMK5dq/J+K5tVXu1Np5dHsamcXKGtRbWQ8gOBv1+9aUtlYXjX1V35nYo6e8NAHfuy4xjzZVKve5BXPCAjfAKv/sTpwSpYiIY4oh+2+ZaqJHHECvvv3o/0I8L7UOg==; 25:WlYMFbHd6Jf5itUmMaglZUkSbqkdsWNUdIbQ1ui26hOrUrGkLJkgEVElgJYY8sG2K8mYExplHtEEkthHNTX04h2Tb8+6VgD8Btf9TNmk5mQGMQ7+b35heW7b9DnwguMqxF5KB1cmUXrJtpcwbj6UOGrptG+0pNZ/ksSNzw/4ZV5t6ykV1KskvHFcHl5C+SlnF4WHZc/8McsPtfVqH7H9VcXhkQasMv69Zx4UxyMFvf4/V9NM9cEjIy9z4nYrn4Us74Ns/PUava+I/6iHEkgHwA==; 4:ZGMJ9ksKfn/ORXg1hGQAKV7Bsu5iKTgZX+wzAlubtecHYWYRe0ysvJ9TO5ijF1/ppAQmLhUEBR3+BGcAVRcCevC64KjeZPPHHj1qxwNDUqgE1hlIPIU9ZPZ+2jb2o+NmIQvxEWiTHL1HFvAO+CLfcnzxm8gWMPA0ZPyfhUHtDyTuyWnqdybj1y1upfh5f0Hb6BjXcZdYGIFL7PRq/8pXLKR+OAdlWuiyGUtgFB+rrKzNuWpZEIvbl/5cEW4bpw+4kbITHGcKZDngK9UiGjZCE/nybQFJygo0dng9FTBrBQxNMPa5CujwKm8vfY77CDNUfvvVYBjQ32AHQA2J4DjvDQ==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:OS2PR01MB0138;
X-Microsoft-Antispam-PRVS: <OS2PR01MB01383222A812205997E6FA34CA5C0@OS2PR01MB0138.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(8121501046)(520075)(5005006)(520078)(3002001); SRVR:OS2PR01MB0138; BCL:0; PCL:0; RULEID:; SRVR:OS2PR01MB0138; 
X-Forefront-PRVS: 070092A9D3
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(24454002)(189002)(479174004)(199003)(107886002)(47776003)(189998001)(92566002)(5001860100001)(80316001)(5001960100002)(2950100001)(5004730100002)(62966003)(5001770100001)(68736005)(81156007)(77156002)(4001540100001)(59896002)(122386002)(4001350100001)(40100003)(5007970100001)(50466002)(5001830100001)(74482002)(46102003)(77096005)(64126003)(105586002)(97736004)(23676002)(42186005)(87266999)(83506001)(76176999)(106356001)(65956001)(54356999)(33656002)(87976001)(101416001)(65816999)(50986999)(64706001)(65806001)(86362001)(66066001)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:OS2PR01MB0138; H:[133.2.210.64]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtPUzJQUjAxTUIwMTM4OzIzOmZFak9TR1Q4VkFDdVArK1dhVGEyRnBhMWVD?= =?utf-8?B?UHdKUW5LOGFvaDlMVkIvNlNtNmdLaVZmSmNBaHhQZFkycEUxbTQ5U1pmRUUr?= =?utf-8?B?d0k2SzhJRndabjc1MGx0NThvYzhvU1hPSHR1T3dpcUx2MjRrZ0VnTVRKQ1c1?= =?utf-8?B?QlgvOFc2Z1pscFI4QUI4eGxQZlRjeWZUU3JNUlM4dk9XZjlpMnp0OU54elNt?= =?utf-8?B?ZmQ4d2R0RDdaSkJJQXJKUEwzbDdLcDRDR3VSNVY2WTJvcUl5bzNwUDVEM0ZR?= =?utf-8?B?dFB2NmQ3ZlIwM3g4alNxOHprVGZUL1paNEZFdk5JQ0ZuME9FVUpzSndzN25x?= =?utf-8?B?NTJnaEdjRk9Pa2VSeFRwNVBITTQvNGNSNmtRT012TzRDdlZzUGxOOGQ3enFj?= =?utf-8?B?QkNtd2JvblVpQ1VjdVlmcXkxeGtnQlFYdFZiSGJDaCt4NlZNMTNicWpoRU5J?= =?utf-8?B?UWdBczViZ1djMHVqT3BUc3RrYnB0eGt4eDZzYzVCaEZySTNVcWxmTHd0Ky90?= =?utf-8?B?cjdNM1ZlTEtraEsvZVRVa3U4ays2a1RDUUlaaGkwc2xwVVN3dnBZR3U2Zklh?= =?utf-8?B?TUZiUlBtRFY5M1dzTnc0N2p5aG9rOGk5OEhJVVhLeExIb0lTTXZQV3VleEdw?= =?utf-8?B?akpyekhWVXZzV01tM1U3OHk4aE10L1E2c09UeHRPZjJMSVpKdGl0c2ppSW1x?= =?utf-8?B?OENDcGdGUG9lUGllNHc1SWF1bDJiamVzWHhTc0RIWW1aaWRsclZzT2szQjYx?= =?utf-8?B?RUZ1MlRaK0lJWFhpVzd3U0lBT1h2bW5QSDFFRkdrYUNRdGFRUXpQckRrelhR?= =?utf-8?B?TTFQMktZQ1Mvblpldm5kd2RQbllKdHlLbXN2WFVteWVSdHkxRXl1Zm5FRnN2?= =?utf-8?B?Y2x4ckZ1N2I1a25NeUo4V2xJUnZRK1VMQTJyYTZucUd5MmtPcHUrM0tpOGRl?= =?utf-8?B?bWE4ZkJGWE5kdldYVC9PVmJzeG1QV3dUODlaYi9TTVQ1QWZpc2tYdE9Fb0oz?= =?utf-8?B?czl3TElzb3ZmV285R2tpcnNyM0FKaG56ZDRUWGJzMnU1bXlrUDNQaTcxb2Fz?= =?utf-8?B?QkxJRm11eWIwUXdyS2ZzZ1ZHSjVJSjhJaWFtSWpLRXllUjVLaU5HVEs3MTVz?= =?utf-8?B?aDhUYXMrekNLNmRpc0FrOUlRYWRpMGZxNHQxOVdkY1AzMUZ2d3RCRlA2blN0?= =?utf-8?B?RC9vOXpaSUpHUHcySjJmWFZjWjZyN2VaM3hjMWtHR3BLM0t0TSt6TWZtRGZN?= =?utf-8?B?WVpwakZWbnhJZzZjQk9rb3Z5ODhPZnlGSUFXU2hvV3pod0oyKzdLYzhrUFAr?= =?utf-8?B?ZkNhYXVSTEU4NE1CUTRFcXRNSnRqcDM1YVhKRndUVjF2dUZXSkJRR1BqNUds?= =?utf-8?B?Q3JuUlM3UE0wbEp2Y1ZBc1pBNVNROXQzVHJVTUJ4NDhSSDBpMEVhNndqazhI?= =?utf-8?B?ekJUeE1BWjNtL2d1bjhyc2t2b1ovOEFqTHZxWVFucGljWDEveVg5RlRqSTV6?= =?utf-8?B?V1VCZ3Y3b01LMmZyd1NmYW5xb3FkRmtqakEvL2lhODQzODdmRG1ZT08vOXlZ?= =?utf-8?B?WmJib2tkRVhFY0NPN3I0akZYK0dWQTdQbE5iTExMcE9BQjduYXRiQnlKQXRH?= =?utf-8?B?Ky8yOG5kODlLVHd6Z1EzdElPdms3cXlCRWZZUnRVNmR3S0xBd0o1WktyQjNu?= =?utf-8?B?NVQ2bk1MWDBXQUgyRlY1bWc3RUdzeGZKaXJEU0pjYnNMYncvUlQxSDh6MFlx?= =?utf-8?B?Z0FVMjY1bXB0ejZkSDNja21KVnVKRTl4UThTd1NkRkkvU1pydWFqQWpBaXNE?= =?utf-8?B?SW1GZG5UZkZFbURIcCtlTS9xaEZjbVJ1TGdUUnNwd0RwWXExSTloejhsYUhz?= =?utf-8?Q?nFuhxE5r6x8=3D?=
X-Microsoft-Exchange-Diagnostics: 1; OS2PR01MB0138; 5:kTbArJeinWvrycQ1cqZA3DWm2MGk4lm19Crb36sc0YGWclXmyxBtMl/q8HOj9tNWCon93C222zj65zXjxFv0m6md74JTWHz4jVUOiRG53rsUv/xcbwTfQ8w+EV8KNdlzFUiE+pfCPibq05vsbQJd0A==; 24:FZhwh03kYQ1c0lqpW5QUKMTKCrw0gA/KeX+bFp2qspmNZcU72S2QmTBV9kiWQm6vyysj/QxnzX4T+pSGcln3Dj6hiyRFNxZDJFs6asehArE=; 20:hTqhGO7XOxF1qMvXc+2xfoQE1q4/mMm8bUPlL4hB8L3xJZyzaQ+duMwyPWjYgA5QBOjUYAUhhdaHO2tB5e84Kw==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 15 Sep 2015 06:35:58.8094 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS2PR01MB0138
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/YWAdB_D8VkUGF6UuW5XQ8yluDVY>
Subject: Re: [urn] Approval process for new URNs based on non-IETF standards
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 06:36:05 -0000

Hello John, others,

On 2015/09/14 02:50, John C Klensin wrote:

> We encountered a similar issue in thinking about media types and
> developed the idea of delegating most of the responsibility in
> such situations to "recognized standards-related organization"
> (see Section 3.1 of RFC 6838 for the current version, but
> variations on the idea go back many years).  Adapting that model
> to URNs seems wise to me.
>
> If there is agreement about that as a principle, I suggest we
> make approximately the following changes to Section 7 or
> draft-ietf-urnbis-rfc2141bis-urn-12 (or equivalent, if Peter
> gets -13 finished before agreement is reached on this):

I agree with Peter that in general, this is reasonable.

>    -----------
>
> (1) At the end of Section 7.1, add:
>
> 	"While the registration templates are the same, slightly
> 	different procedures are used depending on the source of
> 	the registration."
>
> (2) Change the title of Section 7.2 to "Registration Policy and
> Process: Community Registrations".
>
> (3) Add a new Section 7.3, titled "Registration Policy and
> Process: Fast Track for Recognized Standards Development
> Organizations and Scientific Societies" that reads:
>
> 	The IETF recognizes that situations will arise in which
> 	URN namespaces will be created to either embed existing
> 	and established standards or to reflect scientific
> 	knowledge, terminology, or information organization that
> 	lie well outside the IETF's scope or the likely subject
> 	matter knowledge of its Designated Experts.  In
> 	situations in which the registration request originates
> 	from, or is authorized by, a recognized
> 	standards-related organization or scientific society, a
> 	somewhat different procedure is available at the option
> 	of that body:
> 	
> 	1.  The namespace registration template is filled out
> 	and submitted as in steps 1 and 2 above.
> 	
> 	2. A specification is required that reflects of points
> 	to the needed external standards or specifications.
> 	Publication in the RFC Series or through an IETF process
> 	(e.g., posting as an Internet Draft) is not expected and
> 	would be appropriate only under very unusual
> 	circumstances.

Why not simply say "is not necessary".

> 	3.  The reviews on the discussion list and by the
> 	designated experts are, however, strictly advisory, with
> 	the decisions about what advice to accept and the length
> 	of time to allocate to the process strictly under the
> 	control of the external body.

I agree that this should be the case for the content aspect of the 
request (what stuff is given URNs,...), but I think we should make 
extremely clear that the overall syntactic restrictions that the spec 
makes are not up for negotiation or reinterpretation.

Regards,   Martin.


From nobody Tue Sep 15 07:04:48 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09DCB1B4DEE for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 07:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.09
X-Spam-Level: *
X-Spam-Status: No, score=1.09 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 tj0hHf-sHksr for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 07:04:42 -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 246D11B4D1A for <urn@ietf.org>; Tue, 15 Sep 2015 07:04:42 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Zbqqc-000AIw-GQ; Tue, 15 Sep 2015 10:04:38 -0400
Date: Tue, 15 Sep 2015 10:04:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>, urn@ietf.org
Message-ID: <1ECD3A3077BAB0F3916E3D0A@JcK-HP8200.jck.com>
In-Reply-To: <55F7BC49.6090505@it.aoyama.ac.jp>
References: <65C29163B6F527DF836969A9@JcK-HP8200.jck.com> <55F7BC49.6090505@it.aoyama.ac.jp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
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: <http://mailarchive.ietf.org/arch/msg/urn/KcrYbzk76ih53-wW6TPi4e96bdo>
Subject: Re: [urn] Approval process for new URNs based on non-IETF standards
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 14:04:46 -0000

Hi.

I'm responding to Martin's note as a convenience, but some
things below address Peter's comment and a brief offlist
conversation.

--On Tuesday, September 15, 2015 15:35 +0900 "Martin J. =
D=C3=BCrst"
<duerst@it.aoyama.ac.jp> wrote:

>...
>> 	2. A specification is required that reflects of points
>> 	to the needed external standards or specifications.
>> 	Publication in the RFC Series or through an IETF process
>> 	(e.g., posting as an Internet Draft) is not expected and
>> 	would be appropriate only under very unusual
>> 	circumstances.
>=20
> Why not simply say "is not necessary".

This is mostly a textual matter and I don't feel strongly about
it one way or the other.  FWIW, what I was thinking when I wrote
the above was that, in general, when we are dealing with other
bodies that have their own approval and publication procedures,
we let them finish whatever they are doing and publish and we
then either reference their publication or work our permission
to republish in the RFC Series.  The disadvantage of having an
I-D posted and considered in the IETF is that the risks of
inconsistent specifications resulting from two groups tuning
things in different directions and creating inconsistencies are
significant (especially if the IETF community starts making
modifications it may not understand to documents it doesn't
understand, which was exactly the case that the Media Types
mechanism and this proposal were intended to bypass).

But, while that was my reasoning and the answer to "why not", I
again don't feel strongly about this so, if others prefer "not
necessary", go for it (although a sentence about understanding
the consequences or being clear about change control would seem
useful).

>> 	3.  The reviews on the discussion list and by the
>> 	designated experts are, however, strictly advisory, with
>> 	the decisions about what advice to accept and the length
>> 	of time to allocate to the process strictly under the
>> 	control of the external body.
>=20
> I agree that this should be the case for the content aspect of
> the request (what stuff is given URNs,...), but I think we
> should make extremely clear that the overall syntactic
> restrictions that the spec makes are not up for negotiation or
> reinterpretation.

While I agree, my usual concerns about the protocol police and
the advantages of having even bad stuff registered and known
kick in.  So the WG has a choice that applies to both this fact
track case and the normal one:  Assume some organization decides
that it is going to use something that looks like a URN (e.g.,
something that looks like a URI starts with "urn:") but that
violates "overall syntactic restrictions", design assumptions,
or something else fundamental.  If we cannot convince them to
not do that, is the Internet better off with a registration that
can identify the non-conforming use or not registering it at all
but hoping that no one will use or notice it (or that our
condemnation through silence will prevent its use).  =20

At the moment, my instinct says that we are better off with the
documentation, even if it means creating an extra section of the
registry or a registration category for non-conforming names and
namespaces just to reduce the odds or name conflicts and
identify the uses.  I think the Internet is better off that way
than if we try to pretend the usage doesn't exist.

None of that suggests that we should be willing to negotiate or
reinterpret.  The question is only about what we do if, e.g.,
someone has a namespace and syntax that uses "#" as an
introducer that has absolutely nothing to do with the 3986
requirements for fragments.

Noting that exactly the same question applies to non-conforming
URI schemes as to non-conforming URN namespaces, I don't feel
strongly about this or feel a need to spend a lot of time on it
because I think that the number of cases in which someone will
come forward and say "I have this namespace and URN syntax for
it that violates a bunch of your rules but want to register it
with you anyway" will be very few, maybe few enough to be safely
ignored.  However, if we are going to make strong statements
about what people cannot do, I think we need to understand and
should consider the issue.



--On Sunday, September 13, 2015 16:15 -0600 Peter Saint-Andre -
&yet <peter@andyet.net> wrote:

>> (3) Add a new Section 7.3, titled "Registration Policy and
>> Process: Fast Track for Recognized Standards Development
>> Organizations and Scientific Societies" that reads:
>=20
> I have two concerns about "scientific societies":
>=20
> 1. The IETF has experience in judging when another
> organization is an SDO, but not in judging when it is a
> scientific society.

I'm not in a good position to debate "experience", but note that
"scientific societies" were explicitly recognized a decade ago
in RFC 4288.  FWIW, while we have never formalized a
relationship or, AFAIK, even seriously discussed doing so, but,
for those who don't know, there is a body known as the
International Council of Scientific Unions (ICSU) whose
membership (and the membership of its their subsidiaries and
ICSU formal affiliates) comes fairly close to an authoritative
list.   In that sense, "scientific societies" may actually be
easier to make objective judgments about than SDOs where, for
example, the boundaries between "trade association", "industry
consortium", and "SDO" may get very subjective and difficult to
evaluate fairly.  But see below.

> 2. It seems to me that the realm of organizations that might
> deserve to be on the fast track is not limited to scientific
> ones. What about organizations whose purpose is cultural
> (e.g., the British Museum), scholarly (e.g., the London
> Philological Society), educational (e.g., TERENA - see RFC
> 6338), governmental (e.g., the United Nations), military
> (e.g., NATO), charitable (e.g., Creative Commons),
> professional (various industry consortia), and so on?

What we did in RFC 4288 and the later 6838 was to leave
"recognized" completely in the hands of the IESG without even
trying to spell out criteria.  In a way, that turns the
criterion into "are you, IESG, willing to trust this body
sufficiently to give up some authority to it".  In the media
types case, I don't believe that there has ever been controversy
about the decisions the IESG has made.  Neither the IESG nor the
community have felt the need for a formal application procedure
for someone to be recognized as a standards body (or whatever).
I take those as good signs and suggest that it would be wiser to
say, perhaps, "recognized SDOs, scientific societies, and
similar bodies" and then drop the subject in 2141bis, leaving it
to the IESG to figure out what to "recognize" and what
constitutes "similar".

FWIW, some notes about Peter's "what about" list.  Picking the
first example and based on discussions in other contexts, the
British Museum is _very_ unlikely to try to create or register
something that has broad international or long-term implications
as an individual initiative.  They are historically much more
likely to take the idea to an international industry association
(perhaps ICOM), UN body (UNESCO or ECOSOC more generally), or
someone we would almost certainly recognize as a standards body
(like ISO TC 46).    So that may be a non-problem.  Conversely,
one of the reasons I want to pass this to the IESG rather than
trying to lay out lists of bodies or even specific
guidelines/criteria, while the British Museum would be fine
_and_ is unlikely to generate a direct, single-organization,
request, I suspect we would be less enthused about waiving
expert review, etc., for the National Museum of Lower Slobbovia
or, given recent events, the Caliphate Museum Authority of
Palmyra. =20

The idea of picking a list (or an organization that keeps a
list) rather than having the IETF try to figure one out on a
case-by-case basis has a very long tradition with IANA, long
before ICANN.  Country-code TLDs would not exist, at least in
the form we know them, had Jon not found ISO 3166 and been able
to use it an authoritative list of both entities who would
qualify and the codes to be used -- he felt that having IANA try
to figure out what was or was not a "country" or how its name
should be code would quickly lead to madness.  A few other TLDs
with global scope would have been created had their proponents
been able to come up with an authoritative, generally recognized
and accepted list of second level eligibility.  It probably
doesn't apply here and would presumably be part of a hint to the
IESG anyway, but use of ICSU membership and their subsidiaries
and affiliates could be the basis for a similar
externally-generated and maintained list if that were needed.
Probably worth keeping the principle in mind.

    john



[1]




From nobody Tue Sep 15 08:11:46 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31C7B1B4FFC for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 08:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 g0GPyBgQBPMs for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 08:11:42 -0700 (PDT)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D7BA1B41B2 for <urn@ietf.org>; Tue, 15 Sep 2015 08:11:42 -0700 (PDT)
Received: by igcpb10 with SMTP id pb10so16452530igc.1 for <urn@ietf.org>; Tue, 15 Sep 2015 08:11:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=reOGZarjz2dcwr5ACkDuOOmH3g3FPfO5elrSBymBFJQ=; b=Y/2YPEEvpLbJ7UDdNWqYd/uyjYIm47lUePRl9mb9xOk2MCnhFkXJbmhBc1IJyPdAmK mS62UtLqWTaS2bQchfn1SE63H73+YDsr6VwfyuTjrm5m8hUKK1NTG/EmlRXejgaMqN3n y4YRDWCli+Ps6gllx+98hv2Ckx6PYcNZuijkfSEvjLODHSULM6EXV+nluiNkMku/CsU3 2TH/aPoHxk7hZdN9zEy09V1gkjdXGiex9oQImQmxH955y67b3uq4dE8jKT6lDC+8B8lV xROq7s8Mo88K9cPUbdSRM9C+6sbOsMl6DjSboG0AJ3/B38Qaz7TwKTVEmSHfDIAQp/UV HWng==
X-Gm-Message-State: ALoCoQmD4P952pE+ogyW94B7VLmC5Z4Z0uw0Cys66h8l1+08n8ZyHJ67/6O1ELTH5Whx2UF0I++1
X-Received: by 10.50.30.65 with SMTP id q1mr6832620igh.28.1442329901435; Tue, 15 Sep 2015 08:11:41 -0700 (PDT)
Received: from aither.local ([2601:282:4201:ef5b:5df9:8c69:a7b1:88f]) by smtp.googlemail.com with ESMTPSA id d82sm8258258iod.43.2015.09.15.08.11.40 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Sep 2015 08:11:40 -0700 (PDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <55F8352B.4090305@andyet.net>
Date: Tue, 15 Sep 2015 09:11:39 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/z4Luk3mLM7GKdgy9uqveJ1JJdqc>
Subject: [urn] ABNF
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 15:11:44 -0000

As mentioned last night, I have been experimenting with the ABNF so that 
we can capture the fact that we don't want "??" in a q-component, only 
at the start of an r-component.

Unfortunately my experiments were not complete when I submitted -13, so 
let's try to get this right in -14.

I see two primary approaches:

1. Approximate things in the ABNF (as they were in -12) and supplement 
the ABNF with some additional text (e.g., "a q-component MUST NOT 
contain any sequences of two question mark characters, since that 
sequence is to be used only at the beginning of an r-component").

2. Try to capture things in the ABNF. Here is where I ended up after 
publishing -13 last night (the only difference from -13 is that I 
changed the terms 'word' and 'phrase' to the less suggestive terms 
'ustring' and 'uset'):

       namestring    = assigned-name
                       [ "?" q-component ]
                       [ "??" r-component ]
                       [ "#" f-component ]
       assigned-name = "urn" ":" NID ":" NSS
       NID           = (alphanum) 0*30(ldh) (alphanum)
       ldh           = alphanum / "-"
       NSS           = ustring
       q-component   = ustring *uset
       r-component   = ustring *uset
       ustring       = pchar *(pchar / "/")
       uset          = "?" ustring
       f-component   = fragment

I am not an ABNF expert, so suggestions are welcome (including the 
suggestion that #2 is impossible and I should give up).

Peter


From nobody Tue Sep 15 08:44:44 2015
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 115BA1A1A9A for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 08:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level: 
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, J_CHICKENPOX_44=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=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 MPT2REfkWF_U for <urn@ietfa.amsl.com>; Tue, 15 Sep 2015 08:44:40 -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 CC5CF1A1AA3 for <urn@ietf.org>; Tue, 15 Sep 2015 08:44:40 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ZbsPO-000AXC-VF; Tue, 15 Sep 2015 11:44:38 -0400
Date: Tue, 15 Sep 2015 11:44:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, urn@ietf.org
Message-ID: <343D92700F25A9E6609B5F39@JcK-HP8200.jck.com>
In-Reply-To: <55F8352B.4090305@andyet.net>
References: <55F8352B.4090305@andyet.net>
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: <http://mailarchive.ietf.org/arch/msg/urn/f012n7Fg53t65ri6RzpCYnG-97c>
Subject: Re: [urn] ABNF
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Sep 2015 15:44:42 -0000

--On Tuesday, September 15, 2015 09:11 -0600 Peter Saint-Andre -
&yet <peter@andyet.net> wrote:

> As mentioned last night, I have been experimenting with the
> ABNF so that we can capture the fact that we don't want "??"
> in a q-component, only at the start of an r-component.
> 
> Unfortunately my experiments were not complete when I
> submitted -13, so let's try to get this right in -14.
> 
> I see two primary approaches:
> 
> 1. Approximate things in the ABNF (as they were in -12) and
> supplement the ABNF with some additional text (e.g., "a
> q-component MUST NOT contain any sequences of two question
> mark characters, since that sequence is to be used only at the
> beginning of an r-component").
> 
> 2. Try to capture things in the ABNF. Here is where I ended up
> after publishing -13 last night (the only difference from -13
> is that I changed the terms 'word' and 'phrase' to the less
> suggestive terms 'ustring' and 'uset'):
> 
>        namestring    = assigned-name
>                        [ "?" q-component ]
>                        [ "??" r-component ]
>                        [ "#" f-component ]
>        assigned-name = "urn" ":" NID ":" NSS
>        NID           = (alphanum) 0*30(ldh) (alphanum)
>        ldh           = alphanum / "-"
>        NSS           = ustring
>        q-component   = ustring *uset
>        r-component   = ustring *uset
>        ustring       = pchar *(pchar / "/")
>        uset          = "?" ustring
>        f-component   = fragment
> 
> I am not an ABNF expert, so suggestions are welcome (including
> the suggestion that #2 is impossible and I should give up).

Peter,

I don't think it is impossible.   I continue to prefer something
resembling your first approach. #2 illustrates why:  It is
really hard to look at that and efficiently deduce that the
intent is to ban "??" except as the introducer for an
r-component.  It is more likely to induce an "eyes glaze over"
effect.   Because of that, if you were to use #2 (or a variation
that works if #2 does not), I'd ask that we include a comment
about that intent.  For better or worse, that comment is more or
less equivalent to what you'd need for #1, so, especially
because I believe no one would study the ABNF if the comment
were there the main advantage of #2 over #1 would be to prove
that you/we could do it.

Trying to sort out the syntax does nave one good feature in
terms of forcing clarity of discussion.  It is not clear to me
that we have discussed and decided whether
    abcd?efgh
    abcd??efgh
    abcd?efgh??
    abcdefgh?

are valid r-components or not.   While I can't imagine anyone
really caring about these sorts of cases in practice, pushing
everything into ABNF forces us to decide, while a prose
statement (as in #1) would allow us to say something like
"question marks, especially consecutive ones, inside the
r-component string or a question mark at the end of either an
r-comonents or q-component, are bad ideas and likely to confuse
people and computers alike, but not prohibited."

By the way, as I read your #2, the first of those four cases is
valid, the other three are not.   Is that what the WG wants?

     john


From nobody Sat Sep 19 07:48:13 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD651B5DB9 for <urn@ietfa.amsl.com>; Sat, 19 Sep 2015 07:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level: 
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 bkEiHcZJeyrp for <urn@ietfa.amsl.com>; Sat, 19 Sep 2015 07:48:09 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91C011B5DB4 for <urn@ietf.org>; Sat, 19 Sep 2015 07:48:09 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 565E3509BB for <urn@ietf.org>; Sat, 19 Sep 2015 10:48:05 -0400 (EDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <55FD75CA.70504@seantek.com>
Date: Sat, 19 Sep 2015 07:48:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000908010807090601080708"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/8h_OFYPbnJumuZXlcPEBIXppw3s>
Subject: [urn] draft-ietf-urnbis-rfc2141bis-urn-13 editorial comments
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Sep 2015 14:48:11 -0000

This is a cryptographically signed message in MIME format.

--------------ms000908010807090601080708
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Editorial comments on draft-ietf-urnbis-rfc2141bis-urn-13:

Section 5.4:
(for example by cut and past techniques).

should read:
(for example by cut-and-paste techniques).

"cut and paste" behaves like an adjective, because they modify the noun=20
"techniques" and act as a single idea. Therefore, the compound words=20
should be hyphenated.

(semi-technical)
Section 6.1:
list item 4:

    4.  It MUST NOT start with "aa-", where "aa" is any combination of
        two ASCII letters and the hyphen is followed by something other
        than another hyphen.


should read something like:

    4.  It MUST NOT start with
                    ALPHA ALPHA "-" alphanum
        i.e., any combination of
        two ASCII letters and the hyphen, which is then followed by somet=
hing other
        than another hyphen.


In that list, all quoted strings are literals except for list item 4.=20
"aa-" is not actually a literal, so it is confusing.

Actually it is not clear to me what kind of rule is being articulated.=20
Which are permitted, and which are prohibited, for formal URN NIDs:

br-
br--
br-a

?

Sean


--------------ms000908010807090601080708
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MTkxNDQ4NDJaMC8GCSqGSIb3DQEJBDEiBCAvqGoQZra3z3R/4lZqAb1gWVy7jT81iTTZOJ/G
xUIa+TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQAMB/a6kB1nk49zHFY/
ut0pXqxaLGr+5LpD57Z96a0Y1SfVX9GMpCg7VE4xnhU2HsBiVKaBppejxI44PWs1KNsouIYi
E5l4Jj0C6Tj+mDJXqTXLdAWfIu6OP7kZxZEwczi9X0mW8u88UNGlEh+6Cpda0VJevrTWoCTk
D222zvsZS/5bTx6hqNnuWHtmbxWe5UbPOGuKzZfgUrVVrQgiX2MUQAvYxeJXDGlluDRezsc7
qiCOId0PwYLszLiprRm+oulWsdmi466OzgT9o2Gnbvs8NuXyhSNUx8wOAzUM/D7h33MWI+96
ox9tmlrqhnjzalvisBBAKCtNTUtGJWR8hg36AAAAAAAA
--------------ms000908010807090601080708--


From nobody Tue Sep 22 20:14:56 2015
Return-Path: <peter@andyet.net>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00E91B311D for <urn@ietfa.amsl.com>; Tue, 22 Sep 2015 20:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level: 
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 uq0yeN5MH1x7 for <urn@ietfa.amsl.com>; Tue, 22 Sep 2015 20:14:53 -0700 (PDT)
Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3551B311F for <urn@ietf.org>; Tue, 22 Sep 2015 20:14:53 -0700 (PDT)
Received: by iofb144 with SMTP id b144so33238125iof.1 for <urn@ietf.org>; Tue, 22 Sep 2015 20:14:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=7EjMXNgoYaHlfmHKQPRNTtW13yUsqloK1S4c+hNJt70=; b=A0BdkE2cFFOLGeOOmvxVkNBR3aU7M8Soj9VVQATnHuPKCb/YBio4dYOxLWpz9APOZu 2KPg3Y+sYRdYIgv24quzQt9yLgBucS0ZYS6T0EIk1SiQxduTZHw0s5hfVRgeFLqOqHvO SsaYPBu30VQp+Z31ZD13uRRUfYmTOmFebT7q1WsXlW2GqQRFelsZQL1t1cTxtXg9A3Db LjCSg5MsY344fHEnl4rQE5Fk/XXNdEAtcnFOKrtTiyye6nSHOcAt4emvbPkTRE6eOST2 boola63O58qYgytGKCJ9tQD6ooC0fKu0YHtLUJ7yGJDvmeLaFo2YZ4FIZPoCPs0kdA8J lygg==
X-Gm-Message-State: ALoCoQkY9hSZYoXTysIychrxcBpE7Tdwm87A8igjruTQ6NoKmUbMycSFdtYAjSo2gKU4m8UgSCXE
X-Received: by 10.107.132.222 with SMTP id o91mr39268400ioi.172.1442978092367;  Tue, 22 Sep 2015 20:14:52 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id b10sm2026923igb.9.2015.09.22.20.14.50 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Sep 2015 20:14:51 -0700 (PDT)
To: Sean Leonard <dev+ietf@seantek.com>, "urn@ietf.org" <urn@ietf.org>
References: <55FD75CA.70504@seantek.com>
From: Peter Saint-Andre - &yet <peter@andyet.net>
Message-ID: <56021929.5090704@andyet.net>
Date: Tue, 22 Sep 2015 21:14:49 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55FD75CA.70504@seantek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/dr0Z2B79kgQTW-lTKA9hUp6Akfw>
Subject: Re: [urn] draft-ietf-urnbis-rfc2141bis-urn-13 editorial comments
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 03:14:54 -0000

Hi Sean, thanks for reviewing the document.

On 9/19/15 8:48 AM, Sean Leonard wrote:
> Editorial comments on draft-ietf-urnbis-rfc2141bis-urn-13:
>
> Section 5.4:
> (for example by cut and past techniques).
>
> should read:
> (for example by cut-and-paste techniques).
>
> "cut and paste" behaves like an adjective, because they modify the noun
> "techniques" and act as a single idea. Therefore, the compound words
> should be hyphenated.

Agreed.

> (semi-technical)
> Section 6.1:
> list item 4:
>
>     4.  It MUST NOT start with "aa-", where "aa" is any combination of
>         two ASCII letters and the hyphen is followed by something other
>         than another hyphen.
>
>
> should read something like:
>
>     4.  It MUST NOT start with
>                     ALPHA ALPHA "-" alphanum
>         i.e., any combination of
>         two ASCII letters and the hyphen, which is then followed by
> something other
>         than another hyphen.

That is better. Even better would be this:

    4.  It MUST NOT start with ALPHA ALPHA "-", i.e., any string
        consisting of two letters followed by one hyphen.

However, that is really a special case of rule #5:

    5.  It MUST NOT start with the string "xn--" or any other string
        consisting of two letters followed by two hyphens.

Nevertheless I think it is fine to describe them separately.

> In that list, all quoted strings are literals except for list item 4.
> "aa-" is not actually a literal, so it is confusing.
>
> Actually it is not clear to me what kind of rule is being articulated.
> Which are permitted, and which are prohibited, for formal URN NIDs:
>
> br-

Prohibited according to the rephrased rule #4.

> br--

Prohibited according to rule #5.

> br-a

Prohibited according to the rephrased rule #4.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Wed Sep 23 11:42:33 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528EE1A9125 for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 11:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.601
X-Spam-Level: 
X-Spam-Status: No, score=-4.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 1Oi0ixCccvxP for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 11:42:30 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1AFC1A88CA for <urn@ietf.org>; Wed, 23 Sep 2015 11:42:30 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 26D74509BF; Wed, 23 Sep 2015 14:42:28 -0400 (EDT)
To: Peter Saint-Andre - &yet <peter@andyet.net>, "urn@ietf.org" <urn@ietf.org>
References: <55FD75CA.70504@seantek.com> <56021929.5090704@andyet.net>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <5602F27D.4070805@seantek.com>
Date: Wed, 23 Sep 2015 11:42:05 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56021929.5090704@andyet.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020509030903070502000309"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/Y4c9KvqiTChQHymzwjBL6Xv5g5w>
Subject: Re: [urn] draft-ietf-urnbis-rfc2141bis-urn-13 editorial comments
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 18:42:32 -0000

This is a cryptographically signed message in MIME format.

--------------ms020509030903070502000309
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

On 9/22/2015 8:14 PM, Peter Saint-Andre - &yet wrote:
> Hi Sean, thanks for reviewing the document.
>
> On 9/19/15 8:48 AM, Sean Leonard wrote:
>> Editorial comments on draft-ietf-urnbis-rfc2141bis-urn-13:
>>
>> Section 5.4:
>> (for example by cut and past techniques).
>>
>> should read:
>> (for example by cut-and-paste techniques).
>>
>> "cut and paste" behaves like an adjective, because they modify the nou=
n
>> "techniques" and act as a single idea. Therefore, the compound words
>> should be hyphenated.
>
> Agreed.

OK.

>
>> (semi-technical)
>> Section 6.1:
>> list item 4:
>>
>>     4.  It MUST NOT start with "aa-", where "aa" is any combination of=

>>         two ASCII letters and the hyphen is followed by something othe=
r
>>         than another hyphen.
>>
>>
>> should read something like:
>>
>>     4.  It MUST NOT start with
>>                     ALPHA ALPHA "-" alphanum
>>         i.e., any combination of
>>         two ASCII letters and the hyphen, which is then followed by
>> something other
>>         than another hyphen.
>
> That is better. Even better would be this:
>
>    4.  It MUST NOT start with ALPHA ALPHA "-", i.e., any string
>        consisting of two letters followed by one hyphen.
>
> However, that is really a special case of rule #5:
>
>    5.  It MUST NOT start with the string "xn--" or any other string
>        consisting of two letters followed by two hyphens.
>
> Nevertheless I think it is fine to describe them separately.

OK. Up to you (all).

>
>> In that list, all quoted strings are literals except for list item 4.
>> "aa-" is not actually a literal, so it is confusing.
>>
>> Actually it is not clear to me what kind of rule is being articulated.=

>> Which are permitted, and which are prohibited, for formal URN NIDs:
>>
>> br-
>
> Prohibited according to the rephrased rule #4.
>
>> br--
>
> Prohibited according to rule #5.
>
>> br-a
>
> Prohibited according to the rephrased rule #4.

Thank you for clarifying.

Sean


--------------ms020509030903070502000309
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjMxODQyMDVaMC8GCSqGSIb3DQEJBDEiBCAtkdEcolCWTVwgYpI6yQSJGS2Gbv0plJsS2p6M
ft6yJzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQCbE2DvDTo/GOgBBkzX
o8reqPmE7agNdcXEoyP6SxKaVflc9WfJnGOy8WmkT4VG9ioUJ6UK76Z17AiRJt0cyQhMNeiJ
B3Pegfd8nvvZFFa4M92jDB0iVJ7nYZ5m5u9q//YQYQ8i2qlvRT5WolZ6HTn3NUXw5MqtLJ+n
p+E04BsIIGUqbaeO+qnCp9EZnC0V/UDmv+YW34iVWZnhUG6n4s8ihWdMJHDUbP3XkKOV50Vk
Q0W52XnB6wJ2JH4wRLPdaQoSmR/ld05Fj5XDnWKGPghwOBf7uU1BkmGfYCzhMDRyizyyWGZd
M3pcNmNT9Ew1IFCoYxrV54OrFpDAgz+SjN2aAAAAAAAA
--------------ms020509030903070502000309--


From nobody Wed Sep 23 16:21:02 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04DD31B32E5 for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 ISxciwQXHFMS for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:20:59 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 029641B32E7 for <urn@ietf.org>; Wed, 23 Sep 2015 16:20:59 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D3E18509BD for <urn@ietf.org>; Wed, 23 Sep 2015 19:20:57 -0400 (EDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <560333C2.8080201@seantek.com>
Date: Wed, 23 Sep 2015 16:20:34 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010103060600080404050606"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/tJGuMHZrI7mbMynJAv3TWaU47Ao>
Subject: [urn] Please use real (or at least plausible) examples
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 23:21:01 -0000

This is a cryptographically signed message in MIME format.

--------------ms010103060600080404050606
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello URNies:

I am catching up on a backlog of e-mail, including about seven months'=20
worth of URN mailing list mail.

Having just attempted to absorb seven months' worth of "p-component=20
this", "q-component that", "how many ? should we put in and what about=20
LR vs. LALR grammar this and that" etc., I would like to ask the=20
participants of this group, at least, *please* to use real (or at least=20
plausible) examples of URNs that one reasonably expects to become common =

use. For example:

urn:isbn:978-3-598-24287-8??s=3DI2C&recordSchema=3Ddc
    (note: the thread that I got this example from was very helpful)
urn:ietf:rfc:3986?ct=3Dtext/html#section-2.1
urn:oid:2.16.840.1.101.3.4.2.1


There has been a lot of theory in this WG but (relative to the=20
ubiquitous use of URIs/URLs in modern society) we are short on=20
implementations. Theorizing day and night about what URNs are has gotten =

us a lot of circumlocutory e-mail from a shrinking set of participants.=20
As I recall asking this WG before, how about we pick several examples=20
that we can agree to rough consensus are URNie, and then make sure that=20
the URN requirements fit those things?

Identification schemes for produced works, such as ISBN, NBN, ISSN, etc. =

are clearly a class of identifiers that are intended for URNs. But that=20
is only one class. I think that OID URNs are another distinct class,=20
namely of identifiers for arbitrary objects that are of interest to some =

world, such as the world of telecommunications [see X.660], where the=20
other design criteria for URNs are met (assigned once, not reassigned,=20
kept track of, etc.). Yet another distinct class is identifiers that are =

very likely to yield a single media type or small handful of known media =

types, such as my proposed urn:cert (now withdrawn), which would have=20
always yielded application/pkix-cert and thus f-components would be=20
(potentially) well-defined. Presumably XML things such as schema and RDF =

node URIs would fall into a similar situation.

Respectfully submitted,

Sean


--------------ms010103060600080404050606
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjMyMzIwMzRaMC8GCSqGSIb3DQEJBDEiBCBfiDyog6J+Pf39lVv3BO9WYpvkbftBYvdxBbFF
S13jnzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQDOV2JcZ8K26ORV246z
r/4vLnXzBvbLpyvkH0GNT1L+ARohI9cQFLLTXccDvHRv2HhAZuoqOFZFaZ+6AK+/+vBi/SA3
Mr8UO4lFgP/Cc9ORVD8R8njzoGRsOHuf34OYPForvgGHsJByHokbvSVaeWMcofPHsiQEVvTO
/xELV4AhyuI1xqvo/J4WHtMKTfKfcpYyxMy+7CxYHfVPdUrKwVxkTnGoE0ddFRBsM6GoPbLV
sACTIx/yWgfcb0sSqcma5XBDPhYtZhOBrqPO3VcT3W8BKt61G+6T2RGh0YQVtCFwcuXShKDl
akhsCAIBpFrGpehatXrSr+4AEbSKnJ4O7ZXFAAAAAAAA
--------------ms010103060600080404050606--


From nobody Wed Sep 23 16:22:58 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD6721B32F3 for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 75s6CWpYWkfK for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:22:51 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 623EA1B2F2E for <urn@ietf.org>; Wed, 23 Sep 2015 16:22:50 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 311F6509BB for <urn@ietf.org>; Wed, 23 Sep 2015 19:22:49 -0400 (EDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <56033432.3040506@seantek.com>
Date: Wed, 23 Sep 2015 16:22:26 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010305080801040905090804"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/JtmFiuyaX-l_tHNcGE1DddTGO9I>
Subject: [urn] Think about r-components and q-components differently
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 23:22:53 -0000

This is a cryptographically signed message in MIME format.

--------------ms010305080801040905090804
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

URNies:

The introduction of r-components and separating out directives to the=20
resolver, from directives to the resource*, is a welcome development.

For my part I want to put a big +1 to putting the r-component before the =

q-component. I.e.:

urn:isbn:0385537670??service=3Dshowscanned?dpi=3D600#chapter2

I read all the arguments both ways. My reasoning is this from left to=20
right: first, we have URN scheme. Then we have the namespace. Then we=20
have the actual identifier. Beyond that, we get into "okay, what do we=20
do with this identified resource?" We need to tell the *resolver* to do=20
something, to the extent that we want the resolver to do one particular=20
thing over a default act (whatever that act could be). The resolver may=20
(or may not) give us a location by URL--so from there, we then=20
dereference the URL to retrieve the representation of the resource, at=20
which point we want to qualify the nature of the resource that we want=20
back (i.e., the q-component, which gets translated into the query=20
component). Finally, we have some resource in memory, so we want to=20
identify a particular part of that resource, which is what f-component=20
gives us.

URN protocol [urn] -> namespace [nid] -> persistent identifier [nss] --v

parse/view/act upon [f]  <-   locate/deref  [q]   <-  resolve [r]

Very nice diagram; 6 components.

To the extent that we ask the resolver to do something with the URN=20
(resolve it) FIRST, before using the q-part, it's worth considering that =

the resolver should get a crack at interpreting the q-component part as=20
well. Consider an ISBN resolver that resolves the URN above into a URL.=20
Well, the resolver might be set to use some scanned book service that=20
requires extra parameters for payment information, federated login=20
information (OpenAthens, etc.), screen information, etc.:

https://www.readbooksonline.com/scans?isbn=3D0385537670&dpi=3D600&payment=
_transaction=3DXYZABC#chapter2

In this case, the resolver needs to be able to have the latitude to=20
piece together a URL that includes the q-component, but possibly in a=20
translated or transposed form. The alternative is that you force the=20
URN->URL protocol always to output:
https://www.readbooksonline.com/scans/byisbn0385537670/payment_transactio=
nXYZABC?dpi=3D600#chapter2

This violates the "hierarchical information" vs. "non-hierarchical=20
information" distinction between path and query components, as the isbn=20
and payment transaction information are not necessarily hierarchical=20
with respect to each other.

Ultimately an HTTP(S) server can deal with this, as it can just be=20
configured to redirect that URI to a URI that the site operator deems to =

be "cooler". But other schemes may not be so lucky, and ultimately, it's =

just a kludge.

Sean

* [see following e-mail on "resource"]


--------------ms010305080801040905090804
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjMyMzIyMjZaMC8GCSqGSIb3DQEJBDEiBCCEcIjciZ28r51fw12zc6AONuBlofl7qtpaqp7X
1a6+FzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQA7259ydlKoVvLf51lY
BGZhrNyiBNko69La1lX7Ta3KvWUDU1HctOc760BmVdAgHjEEw0R6z7Y/XCy8lUL3n6+IzYzo
kK1zQaQrbtf8x3hb1OIxUlNTp1omPSN5lJD6Zt99XBJRqWS3Jdf2jc0yhL5fQjpRnX9B2nqg
OTWo7G3SvuVFIAtMawptZQELk3pIHQTT2/vY2Vmi5h8SXEXEwVwiiwrdg/ki/VNqwycYx8vr
Kvs/gBVal1ESiTYnygK16NyPNENEQuPJeEqPU6q+wfJ1EYY+WjxpcoTLta8pJrV5Yd6z/LRl
087xHr8NntVrC/JYjRukJEr0KGa3yGmZXf4wAAAAAAAA
--------------ms010305080801040905090804--


From nobody Wed Sep 23 16:24:28 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9101B3303 for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 nPLXZThOep2g for <urn@ietfa.amsl.com>; Wed, 23 Sep 2015 16:24:26 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEB331B32F5 for <urn@ietf.org>; Wed, 23 Sep 2015 16:24:22 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9D0C1509BD for <urn@ietf.org>; Wed, 23 Sep 2015 19:24:21 -0400 (EDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <5603348F.9020307@seantek.com>
Date: Wed, 23 Sep 2015 16:23:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070609050108020103000200"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/FMqVoAuXwvZ1uhFO9nj_uP0rmW0>
Subject: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 23:24:27 -0000

This is a cryptographically signed message in MIME format.

--------------ms070609050108020103000200
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

URNies:

Section 3.3 says "The q-component is intended for parameters to be=20
transmitted to the named resource and interpreted by that resource." At=20
the same time, it is also written that when a URN resolves to a URL, the =

q-component gets copies verbatim to the query portion of the URL. But=20
RFC 3986 says that query "serves to identify a resource within the scope =

of the URI's scheme and naming authority (if any)." My concern is that=20
the RFC 3986 query really is a non-hierarchical directive (along with=20
the hierarchical path directive) addressed to the naming authority or=20
*service* (i.e., web server, in the case of=20
http://www.amazon.com/get_some_book_info ) to *return* a resource; it's=20
not a directive addressed to the resource itself. Clearly the semantics=20
of "resource" in draft-ietf-urnbis-rfc2141bis-urn-13 and RFC 3986 are a=20
bit different, but it's something to consider.

Is it more accurate to state that a "URN will be a persistent,=20
location-independent identifier of a resource or a class of resources=20
that share the same designation" (Section 1)? I wrote that based on a)=20
the Wikipedia definition of "identifier" combined with Section 1.1 of=20
RFC 3986.

Generally speaking, it seems that fragments/f-components are actually=20
directed to "the resource".

Sean


--------------ms070609050108020103000200
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjMyMzIzNTlaMC8GCSqGSIb3DQEJBDEiBCCxGXFY1Qy4zPNGKa/m9VAnZrLZcYkIl4BakWR6
OF2xBDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQAO7Zk+VQM8PqcOhKEH
Sjez6tNPgauR/Th15WjpzGnd4/oz7UMsNr8II6LYkDjXBtwwkyfW8OMLrIrPynFD87CNnp++
3x0FnZScTtMJd8K/upwBCpKbCEK3RVf9Oz+uCw7SADZs8oayhS6eJLfPwwbwiTn5z2Hgqgki
6PAVKZRE1wKrDCXMyIKV8fkY86+KzVH4e700zwDBSXQ1a4PyrmZNUKa2HW2qr5/8DSymVYrU
g7+29rHdBg8IhYVHlRKZPGqq2rT4NJ0ycMe3ICX2qUQ28dHVrNSXUVeHFYJwMterh4rZc0kZ
vwF0S6jGJPfSUi5TL8gmBhADXlYg726fhCukAAAAAAAA
--------------ms070609050108020103000200--


From nobody Thu Sep 24 00:50:04 2015
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63991B37CB for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 00:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 z9sDDIKKet0W for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 00:49:59 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0119.outbound.protection.outlook.com [104.47.125.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7FA1A6F3B for <urn@ietf.org>; Thu, 24 Sep 2015 00:49:58 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0144.jpnprd01.prod.outlook.com (10.161.134.148) with Microsoft SMTP Server (TLS) id 15.1.280.20; Thu, 24 Sep 2015 07:49:54 +0000
To: Sean Leonard <dev+ietf@seantek.com>, "urn@ietf.org" <urn@ietf.org>
References: <5603348F.9020307@seantek.com>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <5603AB1D.6010703@it.aoyama.ac.jp>
Date: Thu, 24 Sep 2015 16:49:49 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5603348F.9020307@seantek.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: TY1PR01CA0015.jpnprd01.prod.outlook.com (25.161.131.153) To TY1PR01MB0144.jpnprd01.prod.outlook.com (25.161.134.148)
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 2:0+WfcegllgBMWnDgNHhlx7dtH0bgY8s6IIHlbsiW2zqDkq4ZQW9uZMg/4Mf9IuZX5/hBji92fGraxQNX3CxxI3m2I+B5sVH9v6YhJ8fOY2l/tZJlFGnMYzahJ4tlJYhzzEsvd/UGEXMRH5QW+Z+0CZBfSOf3iojEfjbs3fnesOU=; 3:RPzybXGtBFGw5U83ejzY3OXu+LHfQ6zMZvpk9iCRWHnUWhh/xKsHl1L+JnL6IWUFkESbOCD8m7y2tclQlzD84EoyYM1Nqqyh985TGo7lcVQnr42wDcBelLAbfBwZ54rYeYekJtLpzbG0r2+YrjzZwg==; 25:6qK5MBd0v0yVso65Y+4R1KF82Igr78WhLiQUg0X9LJX+cOu3v9RjRqe6XFd439BetzfvYj0gueNCH1gTBbTTYaoytuxwHMvv8MRnhwqCVg1ZLmuZZ5tR+CPkg7ekfnxNzb106iA8LPCW91B2HLJa9ulqDsSBTn8u57L2+GDBYnR18hGfkxlQ/kecxtN3A8bq/TiQ56chp0Raa6H2IrWB24683gxMEXYfON6nE2on+n5+/lmsFFbAhlzU8ZNAwQzegQxEr1svEkx9gz/Dlja9EQ==; 4:jqVN0u9QSLxkp+b7LtLoQJyb+8eK5eJ/fpm8LuxRfVU8+0k3Mkqf9gh5X9pvJLuG+hw804ws+MzRW8cqvM/3UB5B0jWyslwsOz62nE9nJKdPiHfkWoqcVh0mfFr/gZMMibGzKFlSn1/KMis/eZ7FSL4xqRhF1mNTA8AdNGs2sWyocHwXG78ab16W0nBL2c5r0q45HWPp0Sk6Fb/mYB7bcWMP76+xpoXERSf8v6wF5fN0Jz0X0TylmtCylTRfY+deTZFLi945LYaD2JcTw8LbG55nlky8JM3dtTZr62/XjAY7IuxZrbcRVxHEpe0rniy3R9H7mdfDNUnf7v4uYVcsvQ==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0144;
X-Microsoft-Antispam-PRVS: <TY1PR01MB014480AAC6F7EFC90138E084CA430@TY1PR01MB0144.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(8121501046)(520078)(5005006)(3002001); SRVR:TY1PR01MB0144; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0144; 
X-Forefront-PRVS: 070912876F
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(189002)(479174004)(24454002)(199003)(4001540100001)(74482002)(105586002)(33656002)(106356001)(77096005)(50466002)(68736005)(15975445007)(107886002)(5001960100002)(101416001)(23676002)(83506001)(189998001)(62966003)(76176999)(65816999)(77156002)(54356999)(50986999)(87266999)(5004730100002)(2501003)(46102003)(59896002)(5007970100001)(1720100001)(86362001)(40100003)(122386002)(2950100001)(19580395003)(5001830100001)(5001770100001)(87976001)(97736004)(81156007)(64126003)(5001860100001)(4001350100001)(80316001)(92566002)(65956001)(64706001)(47776003)(66066001)(42186005)(65806001)(7940600001)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0144; H:[133.2.210.64]; FPR:; SPF:None; PTR:InfoNoRecords; MX:3; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwMTQ0OzIzOko1NTgxNm9LQWF2VURkbzAwb3dBOHBuaXJ6?= =?utf-8?B?TU9jakxEclNyTXlFUkVaU0Z2N3N6YTlaak5DRU1MZUdIU0xDdURnMkRvMElF?= =?utf-8?B?NGRrc2RMTURVY2J0dENWWU1nd2hVK1NxK1laYVJ3bnNJM3hHRjQ1MmpOVUVh?= =?utf-8?B?ZFlRREZCU3RzTWg3WU9CUGRJNzBOaUtVaThkZTFzUW9seG5aUlJjRGhYVHRy?= =?utf-8?B?VFNPcXhCY3BmbEZVV3pvekhobloyd1BXcjNVUXBwNzZYcXlDeGkrZG5udDln?= =?utf-8?B?QlhCa2swVTVBNHNyVHdqbVVoV3FmMkJaZkRORjRNZmFHOW8xUmZ4T0E3eHJV?= =?utf-8?B?M240TjVPV09OOHZVc0JrM1ZpeGdNQ1p5N2N6RldBY1E0V1pzekJwY3BJZjJ6?= =?utf-8?B?ZnV3ZGRGYVhNQUZqYnc4YmpKY2Z4U2haUGlRenlTTjJONGFpWEJZTHcxM2hp?= =?utf-8?B?VzJQYStKM0dJTFhZajYzTTJOMGhUYmppajRyZC9CajNIeDVsSVVwaFpWTUlv?= =?utf-8?B?d1p0NEhyTmhTU25sR0Z2UDIxclZyOWMzUE5DR20rMG9MMmNXSnhGMzJiT1Fo?= =?utf-8?B?Z1FUK0ZBOGd5VXFJQjlwMlRRL1lsWWVXNEVzMVU1ZkpIaWx3MElYVjVCNFgv?= =?utf-8?B?NzY5L2Uyc3pJa05kek43U0d1VlhmMytRZUpZSDZUb2txTStMVjVrRjZWak9l?= =?utf-8?B?WVJ0dFJsNmw2TUtMRjhQSW9MWEY0WmhNMXYrTXBDNURPYWNVbGpqV0xlUkZX?= =?utf-8?B?RFdiQXNPb2NYZ2pKWTVpRWE2WDFHcDhBVGZMSDczWFM0T25hUVQrMjF5SEl5?= =?utf-8?B?VHl4cGEzTWM4TEROZjZ0N1ZXWmxLTFVxN1FrSllCc00vVDJmV2RpVjZkUVBR?= =?utf-8?B?WlgvUlh4Z0l0MTZkelphS2tHTGZaNnBZSU1sd0JvWkl2clhFRkFyQk03QTlN?= =?utf-8?B?dW95QldzaHA2SDVyTzgxUzJCMDZXZmZnSDNiY2lKSExObXpJVWFSaXg0Q1pQ?= =?utf-8?B?a1htTFhPSHpTa0JEYXR5aEF3dldpZUxUUlY4K1dwRlpsc0pTSWJDcHNUMTBU?= =?utf-8?B?N3FXZncrSnlYVC9jV1VPR2FFL1Q3OFdEczBEMUhVZ2dvY1BkdWpiY0FaNXJX?= =?utf-8?B?Y1ZocHRraThtZm5VVHF5QURwWm5RYzBXM1Y5TFFweHF3TjMxQ1ZOSDlyRDhs?= =?utf-8?B?UStKamRZZ29KRlV6dSttNVlVUTFqVXpnSm5aakVEMXdqMnJxMzhQTGJBdEF6?= =?utf-8?B?eWVPb3djQjZBWVg4aXlZNlNOQndKbVJXZVl3dk1kcjRzNGFja3ZCWmdISWZB?= =?utf-8?B?SGVDMFFEdDNFakxJNzRkT3FlUzNEU0YwZGc5aEVkSk1xWU5OS3lmNzBYTitl?= =?utf-8?B?M0J5MktkK0NvNHhRQUlWcnpuempZRVdwMkx3bGF2WERZZlJydkRVRlZ0a3BI?= =?utf-8?B?dnNYWkdWSGNGQlpTaDNEWHlYWjFKZmJaU2FjRnl2Z2ZFQVk1NEZqdERFSVNy?= =?utf-8?B?eGorUXhYb0dZRjAxd2RuQ2dJOVBVeFhPZTgrQUhqQjFtMkNheG5iR2tXWTNn?= =?utf-8?B?M2JGeXNLNklpZ3ZyMkdVUERJL2RhNW9RTkZGUmxLbzZOSlMvaDdmKytXcUgz?= =?utf-8?B?ZzZKMWFtMC9IYmowSkVvQkNjTVlENUQva0IzbHBOY25EOW8wVFl0SUwyYjVE?= =?utf-8?B?Sys4NGl6Y2VHcnhvdExzUDd3VHhad0I5VUszM3FBajRKbzRya2FPaUJ1R3Zv?= =?utf-8?B?Y2ZoZkRkQzlaRE1Vb2ZzZUxQMFNRREVpWFo5aUxDSHBrYUl5RUI1cnFROFhT?= =?utf-8?B?TkRodTRFaUxIUmlNS3QxNTErd05EK1V6OTNrUUFXdENJdDNFV2o5SXIwdTMw?= =?utf-8?B?MHdwR0J6cG5QUGZOYnFocm90RFROTGdzSzFOUlUzQ1ZaOGtKR2ZyMjlBV1ov?= =?utf-8?B?TkcyS2lvejAwTXUrWnZPYWZsWDhkNjNzcm5scVViTVhrZCt6aFNDYnhBaXZ2?= =?utf-8?B?VWJQWkFTaTVGTnZwZkEzTjB3ZGNreDJhcEhmLys1YUlVcUFkY3BDV3FQeldK?= =?utf-8?Q?WvOs=3D?=
X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 5:BwE+8qbRITvGxbD1shakSjjUr6zvKQoBXNMuNxUw7ywn3N+PozG7YyBrx87iteja0wQVvICgB2X4dqyFKahLCE3lmUXBsvq04If8Br3ZOPj65DDyXk07iA0BFbfZI1R3Obnlnly7SiEg4tdlLOR28A==; 24:rwWgFVnjXh3bwDS/xTHaAI7gE9A5HBp/T5PLLvCN5YKN8eVMPM3+7fLXyR/+MXgfSU2dy4j6w9GrdpEyc3ZBu2A1ItM7aF0dmT/c2lNj/OY=; 20:YvinI6+vhGu+85f9NBmRgp6xJd+TQtb7S7J4IYX2bmVH1nnuHRozZ9ZKkln3tTvRJ9myXtAq+HfscNDGU+PT7w==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Sep 2015 07:49:54.7421 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0144
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/lIEO5jwlpF0dEdOoFLp0b0TZsy4>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Sep 2015 07:50:01 -0000

On 2015/09/24 08:23, Sean Leonard wrote:
> URNies:
>
> Section 3.3 says "The q-component is intended for parameters to be
> transmitted to the named resource and interpreted by that resource." At
> the same time, it is also written that when a URN resolves to a URL, the
> q-component gets copies verbatim to the query portion of the URL. But
> RFC 3986 says that query "serves to identify a resource within the scope
> of the URI's scheme and naming authority (if any)." My concern is that
> the RFC 3986 query really is a non-hierarchical directive (along with
> the hierarchical path directive) addressed to the naming authority or
> *service* (i.e., web server, in the case of
> http://www.amazon.com/get_some_book_info ) to *return* a resource; it's
> not a directive addressed to the resource itself.

 From an outside view, this is correct. The whole path/query stuff gets 
sent to the server, and the server sends something back. And each 
different query is treated as a different resource, e.g. by proxies.

So I think it would be better to reword 3.3 to say "The q-component is 
intended for parameters that are part of resource identification, to be 
transmitted together with the other parts of the named resource."
(or something similar)

 From a server-internal view, it is very often the case that queries are 
implemented as code, and it is very often the case that this code is 
different for each different p-component. But that doesn't need to be 
the case, there is server software that puts identifiers for individual 
items into the path, which means that the software component is the same 
for a lot of different paths with the same few identical initial 
components. And of course, there are other ways of dealing with things, 
some more practical on some architectures and frameworks than others.

> Clearly the semantics
> of "resource" in draft-ietf-urnbis-rfc2141bis-urn-13 and RFC 3986 are a
> bit different, but it's something to consider.

As proposed above, I think it could easily be aligned.

Regards,   Martin.

> Is it more accurate to state that a "URN will be a persistent,
> location-independent identifier of a resource or a class of resources
> that share the same designation" (Section 1)? I wrote that based on a)
> the Wikipedia definition of "identifier" combined with Section 1.1 of
> RFC 3986.
>
> Generally speaking, it seems that fragments/f-components are actually
> directed to "the resource".

RFC 3986 explicitly says that fragments identify subresources. But 
saying that they are "directed to the resource" can lead to 
misundestandings. They are not actually sent to a server, but resolved 
locally after a representation of the resource is received.

Regards,   Martin.


From nobody Thu Sep 24 06:29:09 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD791AD06D for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 06:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level: 
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 RP2Drbsq9nb6 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 06:29:05 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D73281AC3B4 for <urn@ietf.org>; Thu, 24 Sep 2015 06:29:01 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 19003206F5 for <urn@ietf.org>; Thu, 24 Sep 2015 09:29:01 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 24 Sep 2015 09:29:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=POJ1Dxw2GOApKkW 8l8VVajyPppI=; b=N6O0s3or91B2Gqjuxplaz9krGNuMi2YSKgQevN800ns4lDq s16AxUs2gU6BdZU3WvAp4yrNuvXH4QdkW95OKY7XVE4Rnw79KpjxV3AuI2o00vd8 1aIVE+4sVELwwWN2fMsZJvt+KvQ1VUVIsuCFheL+VrMD8ZF15EJSWCRc3+0M=
X-Sasl-enc: ro3hZG5V9KnCoKDl4HBJcTmafquZnOzS5FPZmuRYUjFY 1443101340
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 97CB8C0001D; Thu, 24 Sep 2015 09:29:00 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <5603FA95.5080609@network-heretics.com>
Date: Thu, 24 Sep 2015 09:28:53 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5603AB1D.6010703@it.aoyama.ac.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/5dHs320zucRkZzilaWzdcnZ8hww>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Sep 2015 13:29:07 -0000

On 09/24/2015 03:49 AM, Martin J. Dürst wrote:
>
> So I think it would be better to reword 3.3 to say "The q-component is 
> intended for parameters that are part of resource identification, to 
> be transmitted together with the other parts of the named resource." 

I don't think "part of resource identification" is a good way to 
describe it because r-components can also be part of resource 
identification.  We need to make a clear distinction between parameters 
that are transmitted to the service that provides the resource, and 
parameters that influence the resolution process. Also, the q-components 
aren't "transmitted together with the other parts of the named 
resource"; they're not even necessarily transmitted together with the 
other parts of the URL (HTTP works that way but that's not true for 
other protocols in general).

I need to look more at the 3986 language.   But 3986 is simply wrong 
about so many things, that it certainly wouldn't surprise me if it were 
completely wrong about how it characterizes queries also.

Keith


From nobody Thu Sep 24 06:56:27 2015
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE04E1AD0D6 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 06:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 AjiV2H44xrnX for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 06:56:23 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0749.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::749]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6BD91AD0CF for <urn@ietf.org>; Thu, 24 Sep 2015 06:56:21 -0700 (PDT)
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB439.eurprd07.prod.outlook.com (10.242.23.142) with Microsoft SMTP Server (TLS) id 15.1.274.16; Thu, 24 Sep 2015 13:56:00 +0000
Received: from AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) by AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) with Microsoft SMTP Server (TLS) id 15.1.280.20; Thu, 24 Sep 2015 13:55:59 +0000
Received: from AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) by AMSPR07MB454.eurprd07.prod.outlook.com ([10.242.106.145]) with mapi id 15.01.0280.017; Thu, 24 Sep 2015 13:55:59 +0000
From: "Hakala, Juha E" <juha.hakala@helsinki.fi>
To: Keith Moore <moore@network-heretics.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] q-components, r-components, and resource transmission: Section 3.3
Thread-Index: AQHQ9p2oxzFKKoS3ckqC9QF0XoDGQp5LrK2AgAAEQXA=
Date: Thu, 24 Sep 2015 13:55:59 +0000
Message-ID: <AMSPR07MB454CAF5AAF0B8277115D366FA430@AMSPR07MB454.eurprd07.prod.outlook.com>
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <5603FA95.5080609@network-heretics.com>
In-Reply-To: <5603FA95.5080609@network-heretics.com>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=juha.hakala@helsinki.fi; 
x-originating-ip: [163.173.9.4]
x-microsoft-exchange-diagnostics: 1; AMSPR07MB455; 5:l7yOI1RSGR1SbNXg4+/ENEaqPN5PqMgqwb8K85itvpfpnMnUjFNrpCtWUwDnsDoZxvFp+Iuohxkgaxq1jnMcUNZPdniSuPY0oj7SWMnMypEYHERXEIDR90KEyppn1mQ6SVxDhbYHBdZNowiwYE4dEw==; 24:RYGcUXsyAlp0mTPf99YS7aXH4yED5PWPb54NuTLzrbNOTcpLVoBg2sRfhXDG93dhgywqb0Hsc5SmWLZ5jyoyi3m3wEO/u8BCcZ8GeQbO324=; 20:P7IG8ZVcbAwrlKTIWVPpOXvMtprOa2vx63VaaWnlXCTZSEB0kV/X+ge0kKl4xJXNa+0RybS4atCFc5tIllnVQA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB455;
x-microsoft-antispam-prvs: <AMSPR07MB4556485DC5793E9DFEFBBBAFA430@AMSPR07MB455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(520078)(5005006)(3002001); SRVR:AMSPR07MB455; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB455; 
x-forefront-prvs: 070912876F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(24454002)(199003)(479174004)(377454003)(189002)(5007970100001)(122556002)(66066001)(2900100001)(5004730100002)(5002640100001)(5001860100001)(107886002)(105586002)(5001960100002)(40100003)(92566002)(106116001)(189998001)(76176999)(11100500001)(54356999)(81156007)(4001540100001)(15975445007)(77156002)(102836002)(5001770100001)(62966003)(97736004)(2950100001)(76576001)(10400500002)(106356001)(68736005)(5003600100002)(5001830100001)(77096005)(74316001)(86362001)(33656002)(19580405001)(101416001)(2501003)(87936001)(50986999)(46102003)(74482002)(19580395003)(64706001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB455; H:AMSPR07MB454.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: helsinki.fi does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Sep 2015 13:55:59.5144 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 98ae7559-10dc-4288-8e2e-4593e62fe3ee
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB455
X-Microsoft-Exchange-Diagnostics: 1; AMSPR07MB439; 2:QJfNMI0Jib128TNrXhQH8JqOfBNJlaCyWXVjkuA65jXjQVlV2HOU7lvofBUlEQs+bopaSCvhgGu33ZTpqAe9wlnvo2//rVSmtn5ANHLktnmzm+VRltGcNZORWAMGUnV+i66Ewwarhf6WPjAhUZvO59J+wbUNF75MgNmqMuUfUt8=; 23:CJM2LThq4SGpErGFYIWnfm8/Jy5P9UySK8ITYrDBHB6w2iMc5G3s/IaN+kZT2HvU5UY/li08MDOIJHoMXdYvy7nkakVcUea/KzVdrkxVFLGKVFmLi1FNgA9OC7L5s0Vl6YSpV71J8wMVLZmWwm/km8nmg74/LPHeapdvEfod2HXY6BJFjtSSCjEo2XjOKAqu
X-OriginatorOrg: helsinki.fi
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/B8X_fnY05cf20KMYFlKPYTg5Zmg>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Sep 2015 13:56:26 -0000

Hello,=20

"part of resource identification" should be avoided since neither q-compone=
nt nor r-component have anything to do with identification in the URN conte=
xt. So saying that they are part of resource identification (which is what =
RFC 3986 says about query) would create confusion.=20

I am happy with the current formulation of 3.3.=20

As regards 3986 language: what the RFC says about query in chapter 3.4 is I=
MO one of the most opaque sections of the text. For instance:=20

The query component contains non-hierarchical data that, along with
data in the path component (Section 3.3), serves to identify a
resource within the scope of the URI's scheme and naming authority
(if any).

I do not know where this naming authority comes from, how users are suppose=
d to be able to see it, and why some URIs may not have any if all URIs are =
a priori supposed to identify something.=20

Juha

> -----Original Message-----
> From: urn [mailto:urn-bounces@ietf.org] On Behalf Of Keith Moore
> Sent: 24. syyskuuta 2015 15:29
> To: urn@ietf.org
> Subject: Re: [urn] q-components, r-components, and resource transmission:
> Section 3.3
>=20
> On 09/24/2015 03:49 AM, Martin J. D=FCrst wrote:
> >
> > So I think it would be better to reword 3.3 to say "The q-component is
> > intended for parameters that are part of resource identification, to
> > be transmitted together with the other parts of the named resource."
>=20
> I don't think "part of resource identification" is a good way to describe=
 it
> because r-components can also be part of resource identification.  We nee=
d
> to make a clear distinction between parameters that are transmitted to th=
e
> service that provides the resource, and parameters that influence the
> resolution process. Also, the q-components aren't "transmitted together
> with the other parts of the named resource"; they're not even necessarily
> transmitted together with the other parts of the URL (HTTP works that way
> but that's not true for other protocols in general).
>=20
> I need to look more at the 3986 language.   But 3986 is simply wrong
> about so many things, that it certainly wouldn't surprise me if it were
> completely wrong about how it characterizes queries also.
>=20
> Keith
>=20
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn


From nobody Thu Sep 24 17:25:22 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E48B51B42CC for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 0gRMq_dKLpy8 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:25:20 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED7BD1B33DE for <urn@ietf.org>; Thu, 24 Sep 2015 17:25:19 -0700 (PDT)
Received: from [10.1.4.130] (unknown [208.77.234.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8D5C522E272; Thu, 24 Sep 2015 20:25:00 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_337AA6E5-F2B5-48FA-8240-66C57667B95F"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <5603AB1D.6010703@it.aoyama.ac.jp>
Date: Thu, 24 Sep 2015 17:24:26 -0700
Message-Id: <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com>
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp>
To: =?iso-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/3TyoLvakrF17IyFHpSYW4MDcqkc>
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 00:25:22 -0000

--Apple-Mail=_337AA6E5-F2B5-48FA-8240-66C57667B95F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Sep 24, 2015, at 12:49 AM, Martin J. D=FCrst <duerst@it.aoyama.ac.jp> =
wrote:

> On 2015/09/24 08:23, Sean Leonard wrote:
>> URNies:
>>=20
>> Section 3.3 says "The q-component is intended for parameters to be
>> transmitted to the named resource and interpreted by that resource." =
At
>> the same time, it is also written that when a URN resolves to a URL, =
the
>> q-component gets copies verbatim to the query portion of the URL. But
>> RFC 3986 says that query "serves to identify a resource within the =
scope
>> of the URI's scheme and naming authority (if any)." My concern is =
that
>> the RFC 3986 query really is a non-hierarchical directive (along with
>> the hierarchical path directive) addressed to the naming authority or
>> *service* (i.e., web server, in the case of
>> http://www.amazon.com/get_some_book_info ) to *return* a resource; =
it's
>> not a directive addressed to the resource itself.
>=20
> =46rom an outside view, this is correct. The whole path/query stuff =
gets sent to the server, and the server sends something back. And each =
different query is treated as a different resource, e.g. by proxies.
>=20
> So I think it would be better to reword 3.3 to say "The q-component is =
intended for parameters that are part of resource identification, to be =
transmitted together with the other parts of the named resource."
> (or something similar)
>=20
> =46rom a server-internal view, it is very often the case that queries =
are implemented as code, and it is very often the case that this code is =
different for each different p-component. But that doesn't need to be =
the case, there is server software that puts identifiers for individual =
items into the path, which means that the software component is the same =
for a lot of different paths with the same few identical initial =
components. And of course, there are other ways of dealing with things, =
some more practical on some architectures and frameworks than others.

(Nods head)

>=20
>> Clearly the semantics
>> of "resource" in draft-ietf-urnbis-rfc2141bis-urn-13 and RFC 3986 are =
a
>> bit different, but it's something to consider.
>=20
> As proposed above, I think it could easily be aligned.

OK

>=20
> Regards,   Martin.
>=20
>> Is it more accurate to state that a "URN will be a persistent,
>> location-independent identifier of a resource or a class of resources
>> that share the same designation" (Section 1)? I wrote that based on =
a)
>> the Wikipedia definition of "identifier" combined with Section 1.1 of
>> RFC 3986.
>>=20
>> Generally speaking, it seems that fragments/f-components are actually
>> directed to "the resource".
>=20
> RFC 3986 explicitly says that fragments identify subresources. But =
saying that they are "directed to the resource" can lead to =
misundestandings. They are not actually sent to a server, but resolved =
locally after a representation of the resource is received.

Yes, I agree. I am aware of what RFC 3986 says.

To clarify my initial comment, I was contrasting q-components with =
f-components for Section 3.3. Section 3.3 currently says =93The =
q-component is intended for parameters to be transmitted to the named =
resource and interpreted by that resource.=94 (Which is addressed =
above.) I believe we are in agreement that q-components are part of =
resource identification. In contrast, f-componetns identify subresources =
after the main (representation of the) resource is received. In that =
sense, f-components =93address=94 (=93speak to=94) the main resource. =
(For example, once a webpage is downloaded, either the web browser or =
some JavaScript on the webpage can interpret the fragment part and =
scroll to some part of the webpage.) That is all.

Regards,

Sean

--Apple-Mail=_337AA6E5-F2B5-48FA-8240-66C57667B95F
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ9jCCBK8w
ggOXoAMCAQICEQDgI8sVEoNTia1hbnpUZ2shMA0GCSqGSIb3DQEBCwUAMG8xCzAJBgNVBAYTAlNF
MRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5l
dHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMTQxMjIyMDAwMDAw
WhcNMjAwNTMwMTA0ODM4WjCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNV
BAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAibEN2npTGU5wUh28VqYGJre4SeCW
51Gr8fBaE0kVo7SMG2C8elFCp3mMpCLfF2FOkdV2IwoU00oCf7YdCYBupQQ92bq7Fv6hh6kuQ1JD
FnyvMlDIpk9a6QjYz5MlnHuI6DBk5qT4VoD9KiQUMxeZrETlaYujRgZLwjPU6UCfBrCxrJNAubUI
kzqcKlOjENs9IGE8VQOO2U52JQIhKfqjfHF2T+7hX4Hp+1SA28N7NVK3hN4iPSwwLTF/Wb1SN7Az
aS1D6/rWpfGXd2dRjNnuJ+u8pQc4doykqTj/34z1A6xJvsr3c5k6DzKrnJU6Ez0ORjpXdGFQvsZA
P8vk4p+iIQIDAQABo4IBFzCCARMwHwYDVR0jBBgwFoAUrb2YejS0Jvf6xCZU7wO94CTLVBowHQYD
VR0OBBYEFJJha4LhoqCqT+xn8cKj97SAAMHsMA4GA1UdDwEB/wQEAwIBhjASBgNVHRMBAf8ECDAG
AQH/AgEAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAw
RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJu
YWxDQVJvb3QuY3JsMDUGCCsGAQUFBwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNl
cnRydXN0LmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAGypurFXBOquIxdjtzVXzqmthK8AJECOZD8Vm
am+x9bS1d14PAmEA330F/hKzpICAAPz7HVtqcgIKQbwFusFY1SbC6tVNhPv+gpjPWBvjImOcUvi7
BTarfVil3qs7Y+Xa1XPv7OD7e+Kj//BCI5zKto1NPuRLGAOyqC3U2LtCS5BphRDbpjc06HvgARCl
nMo6x59PiDRuimXQGoq7qdzKyjbR9PzCZCk1r9axp3ER0gNDsY8+muyeMlP0dpLKhjQHuSzK5hxK
2JkNwYbikJL7WkJqIyEQ6WXH9dW7fuqMhSACYurROgcsWcWZM/I4ieW26RZ6H3kU9koQGib6fIr7
mzCCBT8wggQnoAMCAQICEBpCSs8n+cQbczyWKtueyecwDQYJKoZIhvcNAQELBQAwgZsxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAY
BgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQg
QXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xNTAyMDIwMDAwMDBaFw0xNjAy
MDIyMzU5NTlaMCUxIzAhBgkqhkiG9w0BCQEWFGRlditpZXRmQHNlYW50ZWsuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz4n20qAOzUtC1oNz5zgTny0JRBE1mJZszV2s6EurahKP
vku7E+utnLhcaNahAWr2oZgeCK9uhEqijaC4qLZHnGt/+lnbsQtjmMJrcFCzhDZjDOJdYzmuS2cU
vZqY7YwzCG6jSfs4gwNh+29MS6faY6ucncbnfO9rBB0xu5GIdI3BzsPNYnACNlBYU7w4X4GA0/Mw
NAabNhDgxU2Tw1fl5w1Vt+6xRTXBk6V93LyVZN9wBIOpr2MuhoCJLHZrLirv/mbQE5ao4pkJLR/s
yYhS1Ko4MSiJmR3ugKPkxEo6DZkuJrfck36hLmtMo3yuzi7hkXmDzPKkdLlNj+Xek1GWtwIDAQAB
o4IB8jCCAe4wHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFBpm5d7y
8PBT6NqnIVbfNK8hbpPGMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7Bgwr
BgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMw
XQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPU0hBMjU2Q2xp
ZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYBBQUHAQEEgYMwgYAw
WAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNsaWVudEF1
dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3Nw
LmNvbW9kb2NhLmNvbTAfBgNVHREEGDAWgRRkZXYraWV0ZkBzZWFudGVrLmNvbTANBgkqhkiG9w0B
AQsFAAOCAQEAeIf/Nevvv10ssk0unrJb9FC8lJi41sSpq5AFYtmC8IXwUmNxL7L5uE3tGlNJVoTK
ZvGeklYWDRCzq6zqte221TowXYmFO7G27rJZbQRjLzQoY63rMlFPFrjqQCEA6rDgo9DlFO9/81P7
ZC7xvZ52WH7e3p/yJNA4Av8E0eeavhC+l+cwtrw0wCp3gUs5xJT0koGVvli2wR18zecG3ib3ml+G
nDDv2AH7OhcyhVoj6V9AeGQa2HqaVpOQVRUNPamqr3xeARKk5sUSeBvxlF+0FWhl+AnhqNdxmeEp
qpgSvbcS1jbTsqApvgsBcDzjC09wV8mtBoMCtqlHvF3YY2z55jGCA8MwggO/AgEBMIGwMIGbMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3Jk
MRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xp
ZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEBpCSs8n+cQbczyWKtueyecw
CQYFKw4DAhoFAKCCAecwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTUwOTI1MDAyNDU1WjAjBgkqhkiG9w0BCQQxFgQUYPXauxcgqJ/fCh3/2og2WZep9zgwgcEGCSsG
AQQBgjcQBDGBszCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3Rl
cjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMT
OENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENB
AhAaQkrPJ/nEG3M8lirbnsnnMIHDBgsqhkiG9w0BCRACCzGBs6CBsDCBmzELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqGSIb3DQEB
AQUABIIBALGTF6NPKXUSl5h9xaP3q1WCqDz8nOqLeNuJMGUIupK0PjtQbwZM8jhYO6MxWkS2+7w9
PSn9f0eqRXyag5cByxUzeJrwjzFsKyNIMspYmNfnwsQXlmNET23GBAFK2wCTLA2yRw9BxR6uKqsR
C58CZr+uJ3OJso8hR6xPKAiQPN/AYCzuiVdH2NW1UCdVVfKbdriHUzQZuQthmnlhZMBarwDIwiKi
AA22Se6tMwxk5FJdYlLxB1xwl2rMc4SMUgLB/Xc9hdhWr79czw0ypsAaGk4Ba5ZiMCN8G3/q0SI8
8LCTF9YVo6jNq8a5NLJhWaF7CDq80+A0FxOHWZOC5WOO02gAAAAAAAA=

--Apple-Mail=_337AA6E5-F2B5-48FA-8240-66C57667B95F--


From nobody Thu Sep 24 17:29:49 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 284041B3438 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 re40cw-dGJ5k for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:29:46 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8550E1B3435 for <urn@ietf.org>; Thu, 24 Sep 2015 17:29:46 -0700 (PDT)
Received: from [10.1.4.130] (unknown [208.77.234.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 871D822E25F; Thu, 24 Sep 2015 20:29:43 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_89F9EFEE-0715-400E-8873-1C2539C52C69"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <AMSPR07MB454CAF5AAF0B8277115D366FA430@AMSPR07MB454.eurprd07.prod.outlook.com>
Date: Thu, 24 Sep 2015 17:28:56 -0700
Message-Id: <F3CCD760-FF77-437B-9792-78866BD53F32@seantek.com>
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <5603FA95.5080609@network-heretics.com> <AMSPR07MB454CAF5AAF0B8277115D366FA430@AMSPR07MB454.eurprd07.prod.outlook.com>
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/pgFBcXHUlMqycshoB63x-7-eIvk>
Cc: "urn@ietf.org" <urn@ietf.org>, Keith Moore <moore@network-heretics.com>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 00:29:48 -0000

--Apple-Mail=_89F9EFEE-0715-400E-8873-1C2539C52C69
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Sep 24, 2015, at 6:55 AM, Hakala, Juha E <juha.hakala@helsinki.fi> =
wrote:

> Hello,=20
>=20
> "part of resource identification" should be avoided since neither =
q-component nor r-component have anything to do with identification in =
the URN context. So saying that they are part of resource identification =
(which is what RFC 3986 says about query) would create confusion.=20
>=20
> I am happy with the current formulation of 3.3.=20
>=20
> As regards 3986 language: what the RFC says about query in chapter 3.4 =
is IMO one of the most opaque sections of the text. For instance:=20
>=20
> The query component contains non-hierarchical data that, along with
> data in the path component (Section 3.3), serves to identify a
> resource within the scope of the URI's scheme and naming authority
> (if any).
>=20
> I do not know where this naming authority comes from, how users are =
supposed to be able to see it, and why some URIs may not have any if all =
URIs are a priori supposed to identify something.=20

I believe that the term =93authority=94 in RFC 3986 refers to:
      authority   =3D [ userinfo "@" ] host [ ":" port ]

I.e., some server on the network.

In a broader sense, it can be any abstract or concrete naming authority, =
including a reserved keyword such as =93left-usb-hub=94. See Section 3.2 =
of RFC 3986.

When there is no naming authority, the URI scheme itself serves as the =
authority. For example, the data URI (RFC 3987) does not depend on the =
network at all; the entirety of the data is crammed into the URI.

Sean


--Apple-Mail=_89F9EFEE-0715-400E-8873-1C2539C52C69
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ9jCCBK8w
ggOXoAMCAQICEQDgI8sVEoNTia1hbnpUZ2shMA0GCSqGSIb3DQEBCwUAMG8xCzAJBgNVBAYTAlNF
MRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5l
dHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMTQxMjIyMDAwMDAw
WhcNMjAwNTMwMTA0ODM4WjCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNV
BAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAibEN2npTGU5wUh28VqYGJre4SeCW
51Gr8fBaE0kVo7SMG2C8elFCp3mMpCLfF2FOkdV2IwoU00oCf7YdCYBupQQ92bq7Fv6hh6kuQ1JD
FnyvMlDIpk9a6QjYz5MlnHuI6DBk5qT4VoD9KiQUMxeZrETlaYujRgZLwjPU6UCfBrCxrJNAubUI
kzqcKlOjENs9IGE8VQOO2U52JQIhKfqjfHF2T+7hX4Hp+1SA28N7NVK3hN4iPSwwLTF/Wb1SN7Az
aS1D6/rWpfGXd2dRjNnuJ+u8pQc4doykqTj/34z1A6xJvsr3c5k6DzKrnJU6Ez0ORjpXdGFQvsZA
P8vk4p+iIQIDAQABo4IBFzCCARMwHwYDVR0jBBgwFoAUrb2YejS0Jvf6xCZU7wO94CTLVBowHQYD
VR0OBBYEFJJha4LhoqCqT+xn8cKj97SAAMHsMA4GA1UdDwEB/wQEAwIBhjASBgNVHRMBAf8ECDAG
AQH/AgEAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAw
RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJu
YWxDQVJvb3QuY3JsMDUGCCsGAQUFBwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNl
cnRydXN0LmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAGypurFXBOquIxdjtzVXzqmthK8AJECOZD8Vm
am+x9bS1d14PAmEA330F/hKzpICAAPz7HVtqcgIKQbwFusFY1SbC6tVNhPv+gpjPWBvjImOcUvi7
BTarfVil3qs7Y+Xa1XPv7OD7e+Kj//BCI5zKto1NPuRLGAOyqC3U2LtCS5BphRDbpjc06HvgARCl
nMo6x59PiDRuimXQGoq7qdzKyjbR9PzCZCk1r9axp3ER0gNDsY8+muyeMlP0dpLKhjQHuSzK5hxK
2JkNwYbikJL7WkJqIyEQ6WXH9dW7fuqMhSACYurROgcsWcWZM/I4ieW26RZ6H3kU9koQGib6fIr7
mzCCBT8wggQnoAMCAQICEBpCSs8n+cQbczyWKtueyecwDQYJKoZIhvcNAQELBQAwgZsxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAY
BgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQg
QXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xNTAyMDIwMDAwMDBaFw0xNjAy
MDIyMzU5NTlaMCUxIzAhBgkqhkiG9w0BCQEWFGRlditpZXRmQHNlYW50ZWsuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz4n20qAOzUtC1oNz5zgTny0JRBE1mJZszV2s6EurahKP
vku7E+utnLhcaNahAWr2oZgeCK9uhEqijaC4qLZHnGt/+lnbsQtjmMJrcFCzhDZjDOJdYzmuS2cU
vZqY7YwzCG6jSfs4gwNh+29MS6faY6ucncbnfO9rBB0xu5GIdI3BzsPNYnACNlBYU7w4X4GA0/Mw
NAabNhDgxU2Tw1fl5w1Vt+6xRTXBk6V93LyVZN9wBIOpr2MuhoCJLHZrLirv/mbQE5ao4pkJLR/s
yYhS1Ko4MSiJmR3ugKPkxEo6DZkuJrfck36hLmtMo3yuzi7hkXmDzPKkdLlNj+Xek1GWtwIDAQAB
o4IB8jCCAe4wHwYDVR0jBBgwFoAUkmFrguGioKpP7GfxwqP3tIAAwewwHQYDVR0OBBYEFBpm5d7y
8PBT6NqnIVbfNK8hbpPGMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcG
CCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7Bgwr
BgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMw
XQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPU0hBMjU2Q2xp
ZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBkAYIKwYBBQUHAQEEgYMwgYAw
WAYIKwYBBQUHMAKGTGh0dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNsaWVudEF1
dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3Nw
LmNvbW9kb2NhLmNvbTAfBgNVHREEGDAWgRRkZXYraWV0ZkBzZWFudGVrLmNvbTANBgkqhkiG9w0B
AQsFAAOCAQEAeIf/Nevvv10ssk0unrJb9FC8lJi41sSpq5AFYtmC8IXwUmNxL7L5uE3tGlNJVoTK
ZvGeklYWDRCzq6zqte221TowXYmFO7G27rJZbQRjLzQoY63rMlFPFrjqQCEA6rDgo9DlFO9/81P7
ZC7xvZ52WH7e3p/yJNA4Av8E0eeavhC+l+cwtrw0wCp3gUs5xJT0koGVvli2wR18zecG3ib3ml+G
nDDv2AH7OhcyhVoj6V9AeGQa2HqaVpOQVRUNPamqr3xeARKk5sUSeBvxlF+0FWhl+AnhqNdxmeEp
qpgSvbcS1jbTsqApvgsBcDzjC09wV8mtBoMCtqlHvF3YY2z55jGCA8MwggO/AgEBMIGwMIGbMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3Jk
MRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xp
ZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEBpCSs8n+cQbczyWKtueyecw
CQYFKw4DAhoFAKCCAecwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTUwOTI1MDAyOTQzWjAjBgkqhkiG9w0BCQQxFgQUvGzIsydjX3/OQP6mVjdw3keekYswgcEGCSsG
AQQBgjcQBDGBszCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3Rl
cjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMT
OENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENB
AhAaQkrPJ/nEG3M8lirbnsnnMIHDBgsqhkiG9w0BCRACCzGBs6CBsDCBmzELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqGSIb3DQEB
AQUABIIBAKFMo3WpbQbCvfabWC+O4F+pDFi/DIJlU02ORChVKbTSind6oKNIImKuXZoZWnThhCN6
c5TJ+XBeuCYnl0zh8PZJgfO6VjvwXUWV8HNRT0j4gMrzuaD+g23hYAf44kqKITwiEq0WqADEdmJK
JOnWcWKWtohcnaqGVNIyC33jIjNiyPTSnyN9IathpNS4MRf+1fEud0UdxtwJ0cpyUS44JY5P1/eQ
1E8vz+N+900waz4YD14mVGMLSff3H2U1NshAdnQiFxPJDBDzvx2IoQ36BbhbxOok5QLqV8Dl6e1c
zqd1GsdDFluqKibFxDg1nt1s01PNmHRud/zDbYw6aKGfkOQAAAAAAAA=

--Apple-Mail=_89F9EFEE-0715-400E-8873-1C2539C52C69--


From nobody Thu Sep 24 17:56:47 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89CE11B2F5E for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 oOeOlVVQX3Gc for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 17:56:45 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0392C1B2F59 for <urn@ietf.org>; Thu, 24 Sep 2015 17:56:45 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id EE7512076D for <urn@ietf.org>; Thu, 24 Sep 2015 20:56:42 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 24 Sep 2015 20:56:42 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Gx8dsDBSWT5UOuq kjUrTjBbcyLE=; b=BQTdwFKuuk47akD+XQ7uSoBm0rZK4Xc4fymYEQFN7CVezRH oS6caHcyeXWy39xABLvaOvohyjNWveJ1cY/eCaVUC4LgjgLgqfOpBkiqex3KLWfG egynTvNBXUuTCXLjTT2egZWuOEJyLlAlkV+AsM9nJht4AM3Vnxf56Dhm5Izw=
X-Sasl-enc: 2n+4KH0jRh02rJQByg3LbmdZERlH6eRsfH3JDBdUoKik 1443142602
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F86D680088; Thu, 24 Sep 2015 20:56:42 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <56049BC2.2050109@network-heretics.com>
Date: Thu, 24 Sep 2015 20:56:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/PiK4FR-Z6zu8jXoY5BkPqUKGpjY>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 00:56:46 -0000

On 09/24/2015 08:24 PM, Sean Leonard wrote:
>   I believe we are in agreement that q-components are part of resource identification.
This is simply not the case.

Keith


From nobody Thu Sep 24 18:06:05 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446961B342A for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 18:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 w9lMrQqDvwCq for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 18:06:03 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 936FB1B3425 for <urn@ietf.org>; Thu, 24 Sep 2015 18:06:02 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id F1A27204F7 for <urn@ietf.org>; Thu, 24 Sep 2015 21:06:00 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 24 Sep 2015 21:06:00 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=CJ69pjmwE7i8oyY TSMYtR6TvvRE=; b=lRmyOouKv6lhNRs5GVpgZeM1wA9Em8YexiJNSMKkZd1mnut e+UyqUdYtNEaW3foJeBEcil7Wi/KYs1w0OsC6PlYf58+WzeUXZg7ffx4IDOv0vW4 oWrPrNnf7v96pBHLtjFBFwqgCaWn0e2eKH63NAXOgQAJeAs5iBXfWvQIXiYI=
X-Sasl-enc: fs2CBMGqeT9QJQFYDNoy/ChWYp2iDBoJD9DoufssrhOC 1443143160
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 99AE26800C5; Thu, 24 Sep 2015 21:06:00 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com> <56049BC2.2050109@network-heretics.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <56049DF0.6090508@network-heretics.com>
Date: Thu, 24 Sep 2015 21:05:52 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56049BC2.2050109@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/Q_1AFd8Ft7eMeeKqW7EgktaLw3I>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 01:06:04 -0000

On 09/24/2015 08:56 PM, Keith Moore wrote:
> On 09/24/2015 08:24 PM, Sean Leonard wrote:
>>   I believe we are in agreement that q-components are part of 
>> resource identification.
> This is simply not the case.

In the case of a URL query or a URN q-component, I think the confusion 
results because there are actually two resources:

1) The resource that produces the response.
2) If there are no errors resulting from the request to the resource, 
the response is also a resource, separate from resource #1.

The base URL or the assigned portion of the URN names resource #1.    
But it's debatable whether either the entire URL nor the entire URN is a 
"name" for resource #2, because resource #1 is really not constrained to 
produce consistent output even when presented with the same 
query/q-component.   (Such a resource might however be expected to 
generate correct HTTP response headers to defeat caching.)

At least for URNs I don't think we want to treat the entire URN + 
components as a "name" for resource #2, because even if it is properly 
termed a "name" it doesn't have the persistence properties of URNs and 
calling it a name seems likely to create confusion.

Keith


From nobody Thu Sep 24 21:48:12 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1241B2D57 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 21:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 X3tFx-hFKE73 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 21:48:09 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31E8B1B2D53 for <urn@ietf.org>; Thu, 24 Sep 2015 21:48:09 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 89B53509BB for <urn@ietf.org>; Fri, 25 Sep 2015 00:48:07 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com> <56049BC2.2050109@network-heretics.com> <56049DF0.6090508@network-heretics.com>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <5604D1F0.9040300@seantek.com>
Date: Thu, 24 Sep 2015 21:47:44 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56049DF0.6090508@network-heretics.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030301060901090909020101"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/xBfUj2wq6vfjFLhs-G0r9iB6XY0>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 04:48:11 -0000

This is a cryptographically signed message in MIME format.

--------------ms030301060901090909020101
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

On 9/24/2015 6:05 PM, Keith Moore wrote:
> On 09/24/2015 08:56 PM, Keith Moore wrote:
>> On 09/24/2015 08:24 PM, Sean Leonard wrote:
>>>   I believe we are in agreement that q-components are part of=20
>>> resource identification.
>> This is simply not the case.
>
> In the case of a URL query or a URN q-component, I think the confusion =

> results because there are actually two resources:
>
> 1) The resource that produces the response.
> 2) If there are no errors resulting from the request to the resource,=20
> the response is also a resource, separate from resource #1.
>
> The base URL or the assigned portion of the URN names resource #1.   =20
> But it's debatable whether either the entire URL nor the entire URN is =

> a "name" for resource #2, because resource #1 is really not=20
> constrained to produce consistent output even when presented with the=20
> same query/q-component.   (Such a resource might however be expected=20
> to generate correct HTTP response headers to defeat caching.)
>
> At least for URNs I don't think we want to treat the entire URN +=20
> components as a "name" for resource #2, because even if it is properly =

> termed a "name" it doesn't have the persistence properties of URNs and =

> calling it a name seems likely to create confusion.

Keith, I find myself agreeing with you, and also being confused because=20
I cannot agree with you and disagree with you at the same time. The=20
issue here seems to be that "resource" is a very broad term, and RFC=20
3986's definition is at variance from what urnbis is trying to express.

Your first resource #1 seems more like the (naming) authority in RFC=20
3986 terms. Effectively this sounds like the web server or the Internet=20
infrastructure more broadly--whatever machinery is producing a response=20
that gets you to #2. Resource #1 could possibly also be the URN=20
resolver, which is also part of the machinery that is producing a respons=
e.

I would surmise that the entire URN (NID + NSS) + components is not *the =

name*, because it lacks the persistence properties of URNs. The uniform=20
resource "Name" part is just the NID + NSS parts, not the other component=
s.

Regards,

Sean



--------------ms030301060901090909020101
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjUwNDQ3NDRaMC8GCSqGSIb3DQEJBDEiBCBhW/1ZORpDnfW1CpJ83VBGPZLMdMcq9PB8jDtp
yQbbhjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQBEihQcza3Q6bg+SWa+
XwNfaNqAM2tjlY9iBgihInd/SHof3cRYFXRrkGgZCDN49k2Es5RoYvyqa2h9mm3SNPJ0HFfY
XZmh5tB1dHGm45X5WDW+ZUavoyuV/4kqNKPdK1M5gzMLe/9lfOasBXbiLVemCTxpeQrR0fFt
Y1zUnQW1rTsfMBc7PY5C1RiHFQzmvpzT5BahSGAuhDggUhwY/wMORRJWOEq3//7oLts7g/cb
fdAIfwJoXORGACb+FR5BBiAgoP3zOSZAksCCALriMmdQJ1YUBhIcSC1e7ZpOLyDMIGeBhSJJ
PJGI85eWJeFO4rbKbKUuHOuEqjiBtjRV5RbQAAAAAAAA
--------------ms030301060901090909020101--


From nobody Thu Sep 24 22:20:32 2015
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DD71B3017 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 22:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level: 
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 Lkkb2RdEUcj5 for <urn@ietfa.amsl.com>; Thu, 24 Sep 2015 22:20:25 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0110.outbound.protection.outlook.com [104.47.125.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC9C71B2D9F for <urn@ietf.org>; Thu, 24 Sep 2015 22:20:24 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [133.2.210.64] (133.2.210.64) by OS2PR01MB0140.jpnprd01.prod.outlook.com (10.161.77.148) with Microsoft SMTP Server (TLS) id 15.1.274.16; Fri, 25 Sep 2015 05:20:19 +0000
To: Keith Moore <moore@network-heretics.com>, <urn@ietf.org>
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <5603FA95.5080609@network-heretics.com>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <5604D98B.1060406@it.aoyama.ac.jp>
Date: Fri, 25 Sep 2015 14:20:11 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5603FA95.5080609@network-heretics.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: TY1PR06CA0035.apcprd06.prod.outlook.com (25.164.91.45) To OS2PR01MB0140.jpnprd01.prod.outlook.com (25.161.77.148)
X-Microsoft-Exchange-Diagnostics: 1; OS2PR01MB0140; 2:olSbT0WN1JF7sQQAjywdxvp99QdruAR7+cx0Bul3c6rbsl3W2OzRKA3/4OWQnBvM3t8X816cUqxIKYoCg3EG/eLl1h6rkZVXttPmwb2d9tQFuUw+zvzqTWpmFuV2nm09R6nyJefYtHTML0OuFSDkf/b0LKUstp5vGtbkJX9Tv48=; 3:Y8ud9jKvocRk7yBNl0TzDNb+m214Zrke+zXYClWXuIoHRi0qwtqLQ/Kov8EhKPFYjjKiVp+5xjujAkR55zsMKO78RDh4bigOiKYEekT7dxG6DsF7XawucYlSXg7H5HlVaZNx0pce848lqDdL4YBcVA==; 25:gGJWogoSVZyXrCaSuLxIYk49E98ohW87RyoOz0INvWseUtnHobPn8GkLV6kNwjyS2S9hhqrmYMaSF7lp/BLt9mANd6jMcSadSnF9AfOpsWvL1+E2R3q3Q57LsqSGOVguPjajNVqK3qF8qp4wNNXMVHa5A3LwbitlJ1sfg3084K5JBiwqMlMXF7kU+FkB3p7xuU1nhXKVLvYVuN+dTT2ryg/aGWuEtUKs8YCOXYhjKKYrauHe/tNjN4dS2p9x9KjE; 4:5AqVbb4lqbrDdzhC4v18WCmPWAnZRyg+hJhTirTDhld1j6wJU7AuHgyQl0+cqUTerLjLz+sPRhv2JZFI2S3DKc7NXZw+DZw28VCz2D2CuRWP8nksbPuDWKUTuYetFnwtjJdo5Gpx7nmjVg2UaiT51NwjIipzAvhVclx7szAgZlvGJJnkJZHm4kiDKWT3fB/PWCmL2wucKguDFVH56gZg+P+1dfY4hmo6tKw90wMKSQeVDYo/6rM72ELcacgt1b2vxHOBLEOaunj3wVef2K/hpDoDnUCVlosgCqNS+DNVfh2AIMtwtMRVNK3xRHB6xHbmTQEuc4A2M/TV9OMiG8HELQ==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:OS2PR01MB0140;
X-Microsoft-Antispam-PRVS: <OS2PR01MB0140F9E3E5BBE93323C84F08CA420@OS2PR01MB0140.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(520078)(5005006)(8121501046)(3002001); SRVR:OS2PR01MB0140; BCL:0; PCL:0; RULEID:; SRVR:OS2PR01MB0140; 
X-Forefront-PRVS: 07106EF9B9
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(199003)(479174004)(377454003)(189002)(24454002)(64126003)(86362001)(77096005)(68736005)(46102003)(122386002)(106356001)(42186005)(105586002)(50466002)(80316001)(66066001)(77156002)(62966003)(59896002)(74482002)(87976001)(65956001)(47776003)(40100003)(101416001)(64706001)(83506001)(65806001)(76176999)(50986999)(65816999)(33656002)(5001860100001)(189998001)(5001830100001)(97736004)(5001920100001)(4001540100001)(81156007)(2950100001)(23676002)(54356999)(5001770100001)(107886002)(5001960100002)(5007970100001)(4001350100001)(5004730100002)(92566002)(87266999)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:OS2PR01MB0140; H:[133.2.210.64]; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtPUzJQUjAxTUIwMTQwOzIzOmFKcnFWSTJxWHJ3NFQwRjJjVGs4OXhUbm1n?= =?utf-8?B?eWU4ZlZMTnlXWEFpOGFDTjNhempMMUpmYjIvWnZ3dVZPNWE1WGFzWlduZ28y?= =?utf-8?B?N1UwOXF1alBCdUxQem9IMXJ1WUFnYzNZY0RSNjB1amlxWGxVWnpiQk1UQlND?= =?utf-8?B?U09CbjhtaElSQ0M0cldEdng1NWU1TW9iZ3VJeDhEQ3FVbzdNbTZGNXBuWXFD?= =?utf-8?B?cUZQWnJXR3RuMDVjRFBxVHNCUjc3RDhTYjVHbjNpckhKQXBvMzFjUWJFZ3dt?= =?utf-8?B?YW91SHVKc2RwN0g3Y3FxQS9qWTBBam1YVkx2SmhOVHNjNXJQQUxQUExyd0gv?= =?utf-8?B?Y1BnbkxvaHRQaXJ3STFQZzNwUlFDdTlBUXQ3bGhRN1VFVllidmtMZTcyQ0lP?= =?utf-8?B?WDNtT2tLWDdtd0dWNVBvdGhjaEpaUXdjSWJZeWlEc3g2cnkrUzIxblZaN0Vz?= =?utf-8?B?Y1hzNHFRbEo1eGgyaDVYM1o1cXdPYmZOVTh6WmtIQTFBRWVSU04vamZXdWNZ?= =?utf-8?B?bnJpWks5ZlVBRHdoNmtWdG1nU1NoWUFTSnNFY2RoNFZJaFE4WHhzRDR2amhn?= =?utf-8?B?MVRZV1h3TzBELzVpaTlzWkc0WERFc2svYkRCbzh4eWVOSTM3YTFja2wydy83?= =?utf-8?B?cnV3VURScmxHcFIvN241djU3MzdhN3RSZmFXLzIyTE03dEpUbjRLL1EzVnM3?= =?utf-8?B?M0lvUDNsL1p6aXdoWXpRbk41N0toVU5GZi9Xb2xNSVhzZjhiUXZUWHB2Qksr?= =?utf-8?B?c3BTWEwva3JJaWhVV1Z6TTE0bGpBVGxBRm9heGxXUCttVEd1Z2FObzZ5MWRt?= =?utf-8?B?Q0liN1BrUTFHODg3ZWw5bk84ZVlHNnU3ZkdsaWViM0VVdXg5Y3FwMHZEdHhx?= =?utf-8?B?VFBZVXUvY3BBeGNBVUowLy91NUpvaDlQOXhWWStZMlpFcVJsRzEwZFFOOHhh?= =?utf-8?B?dHp4MmlYa3Q2QkhCOXZpZnRObUlmanFZVW9pV0VzOXVOc1FCV3J6RGhzZzZq?= =?utf-8?B?V2h0SUlqRW8vM3lyZkg1SDhubVZiSXMwMEJFQnltVFg4S0x3NHRSUTI5NFRW?= =?utf-8?B?SmxRYU5jWWlFYTdrWjU3N3Z5a1k0QndWb0pvV09XazF2VEg4TlIzOERBOEVW?= =?utf-8?B?bVNVTWJzaEludkNGbktWYTJoTmFmYTBnVjdGR1F4SUlaR2huUXFSQmxrWkE5?= =?utf-8?B?eExkUXVKUk96azNoem51dTZadDkzSkNzbVByRWFGTU5nZ1p3MGEwbnpOOGRV?= =?utf-8?B?cTMvMUxoR1MrNGN3eVBUSWR1aktqZjVxR0VCaXNwem9OQVJuTUtid0FMdDBv?= =?utf-8?B?NHhQeVdiTnQxQmRTWXU3L0Z4NE56U3grRE1sTVVCVnZPaWdFcHZVMXhkZHR4?= =?utf-8?B?RU9wRVcrTFloQUxFWitzTzBYeXRZaDVWMTZoM1FmUHcwd1VKdXFQMnAzUWo0?= =?utf-8?B?MlRsQW4rWWEybCtDZG9uY3ZuK01SNVV4MmpoelFSQ0NGY29lWTFYRVlEc3Ny?= =?utf-8?B?WU9uTWpaU3pxUFJkSjdYL0g2Rmp4bFRCZ0FXUEsxcDNWVGMzemRHc1dBR21t?= =?utf-8?B?VUd0R25rWHBjVW9na25ZeW43VHJ0S3lnQ3VmZUl6czVLb21rb1RIWFR3OVpJ?= =?utf-8?B?MHk2c2NIT3dYOVJaVEZ6ZjFPZUFMUTBuNzlrd2Iva2NiS203RGdhL1RvaW12?= =?utf-8?B?QVV5TVJJL2tvWVpGWnIxRGpVLzJvZDdFWll2c3d3b0xNeDJ6T1N3RDhFdWpP?= =?utf-8?B?OWY2N1FQVk9qb1BSRTFYd0lVdDlwSGd3TTk2WEYxQTBXSTRPNmJYbnpVTG14?= =?utf-8?B?Y2MrSHN5ZWtRRks3dTdnTWFhM3VxaEtnSWZUTW5DVERKRDYvSUFRWWRrVGtp?= =?utf-8?B?aEF2VVhnQW5WOXBiSktIZHR4R1FzQTFBbU9ZWG8rQS9GSFExSlNYYWxRMkZC?= =?utf-8?B?U0Q2WlZURXZnPT0=?=
X-Microsoft-Exchange-Diagnostics: 1; OS2PR01MB0140; 5:KeJClhIBl3YgSh+ITas/SxSPFe8JispIB5/cSqfzxnqvM3jNApMiHR/JJzIEFHYC/VmbAWi5ctYoLRKPtMBMfyf1LTMkEG0jHFq+Mb5DLKgCf/jEG/TzJWXRX2YTYPYznlufnM0uHvpc5VVlckKYOA==; 24:2w/uYCW4snoitXk/iaCzHSo7/Cgz+Zp4WVPCmWDK3ao/ovqcWBJ7Pif75/uMl9CYqUfkWQqETAIPJ5RxcRJn+l+apGGGcsymDtBL0dxVVdw=; 20:7hiSqtWX9Gc2XSFgB0B6PkD0BCKossfqLeCKEiRu4IpBaVF1FxSTndtN3vvY6ZsVGHDPCL6/5DO+QmxEphA9Lg==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Sep 2015 05:20:19.9489 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS2PR01MB0140
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/xmBqtEJ7MHC75CUIV2DNAsQW47g>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 05:20:28 -0000

On 2015/09/24 22:28, Keith Moore wrote:
> On 09/24/2015 03:49 AM, Martin J. DÃ¼rst wrote:
>>
>> So I think it would be better to reword 3.3 to say "The q-component is
>> intended for parameters that are part of resource identification, to
>> be transmitted together with the other parts of the named resource."
>
> I don't think "part of resource identification" is a good way to
> describe it because r-components can also be part of resource
> identification.

In my understanding, the r-components just help a resolver find the 
resource, or some metadata about the resource (which of course in turn 
also can be seen as a resource), but don't actually say anything about 
the (primary) resource.

> We need to make a clear distinction between parameters
> that are transmitted to the service that provides the resource, and
> parameters that influence the resolution process. Also, the q-components
> aren't "transmitted together with the other parts of the named
> resource"; they're not even necessarily transmitted together with the
> other parts of the URL (HTTP works that way but that's not true for
> other protocols in general).

But that's how it would work for URNs, or not?

> I need to look more at the 3986 language.   But 3986 is simply wrong
> about so many things, that it certainly wouldn't surprise me if it were
> completely wrong about how it characterizes queries also.

Could we please, as agreed earlier, refrain from such general statements 
without any supporting information? Thanks!

Regards,   Martin.


From nobody Fri Sep 25 00:35:42 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23C6A1B31C9 for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 00:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 FOCR9_XJzh5d for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 00:35:39 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 004F21B31EB for <urn@ietf.org>; Fri, 25 Sep 2015 00:35:37 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 5B4E0204E9 for <urn@ietf.org>; Fri, 25 Sep 2015 03:35:37 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 25 Sep 2015 03:35:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=rxbMFIrOAOx0/3/ Ea9wO6OVlIkg=; b=HPffRbEpw5QPOW0thcbD/Q824g5SxLVV3NeO7IkAlAGMx/r RTlT4vuY6zy+dZe8VPdNGRDterhabaBFDp+5L3ByrvIDLtogbuZSHa6XV23n7Wr5 oRmasSJCP5B4Gt7ky4BM17TsQy3G+WKpGHquEab4mEHaTT9dene2PlwefE9Q=
X-Sasl-enc: dsF2OAIe2Ph7nQs6HDWBSCZHI/4RIvviNmW9KNZMkJc2 1443166537
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id F384E680194; Fri, 25 Sep 2015 03:35:36 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <B1EAFC33-5FFA-460F-B15D-FD1228724D51@seantek.com> <56049BC2.2050109@network-heretics.com> <56049DF0.6090508@network-heretics.com> <5604D1F0.9040300@seantek.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <5604F93E.50605@network-heretics.com>
Date: Fri, 25 Sep 2015 03:35:26 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5604D1F0.9040300@seantek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/7qpp1TACau2dXqf29vSdc9O8Dpc>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 07:35:41 -0000

On 09/25/2015 12:47 AM, Sean Leonard wrote:
> On 9/24/2015 6:05 PM, Keith Moore wrote:
>> On 09/24/2015 08:56 PM, Keith Moore wrote:
>>> On 09/24/2015 08:24 PM, Sean Leonard wrote:
>>>>   I believe we are in agreement that q-components are part of 
>>>> resource identification.
>>> This is simply not the case.
>>
>> In the case of a URL query or a URN q-component, I think the 
>> confusion results because there are actually two resources:
>>
>> 1) The resource that produces the response.
>> 2) If there are no errors resulting from the request to the resource, 
>> the response is also a resource, separate from resource #1.
>>
>> The base URL or the assigned portion of the URN names resource #1.    
>> But it's debatable whether either the entire URL nor the entire URN 
>> is a "name" for resource #2, because resource #1 is really not 
>> constrained to produce consistent output even when presented with the 
>> same query/q-component.   (Such a resource might however be expected 
>> to generate correct HTTP response headers to defeat caching.)
>>
>> At least for URNs I don't think we want to treat the entire URN + 
>> components as a "name" for resource #2, because even if it is 
>> properly termed a "name" it doesn't have the persistence properties 
>> of URNs and calling it a name seems likely to create confusion.
>
> Keith, I find myself agreeing with you, and also being confused 
> because I cannot agree with you and disagree with you at the same time. 

:)  As far as I can tell, that sort of thing happens all the time.

> The issue here seems to be that "resource" is a very broad term, and 
> RFC 3986's definition is at variance from what urnbis is trying to 
> express.
>
> Your first resource #1 seems more like the (naming) authority in RFC 
> 3986 terms. Effectively this sounds like the web server or the 
> Internet infrastructure more broadly--whatever machinery is producing 
> a response that gets you to #2.

at least where URNs are concerned, resource name #1 specifically names 
whatever it is that produces instances of resource #2 (presumably some 
combination of code+data, but it could be something else, like a 
physical machine), but it doesn't include the internet infrastructure - 
IP routers, DNS, etc - or the content-neutral part of the web server.   
another example of the same resource could exist, with the same name, 
but independent of the Internet (say on a storage medium), or on a 
private network that was completely disconnected from the Internet.

> Resource #1 could possibly also be the URN resolver, which is also 
> part of the machinery that is producing a response.

no.   It's very important that there be a clean separation between URN 
resolvers (of which there can be an arbitrary number) and the named 
resources themselves.   For example, we do not want resolvers to be 
central points at which resource access can be monitored or controlled.

>
> I would surmise that the entire URN (NID + NSS) + components is not 
> *the name*, because it lacks the persistence properties of URNs. The 
> uniform resource "Name" part is just the NID + NSS parts, not the 
> other components.

agree about that.

Keith



From nobody Fri Sep 25 00:42:31 2015
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6521ACDF9 for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 00:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 a5GCjU4vS3L5 for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 00:42:29 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 049221A923A for <urn@ietf.org>; Fri, 25 Sep 2015 00:42:28 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 3EAB720723 for <urn@ietf.org>; Fri, 25 Sep 2015 03:42:28 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 25 Sep 2015 03:42:28 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=jKarzZ80oSPJll7 qIWkPYgNazcc=; b=ZCwx5OvVk3U3JcplvGXcHN33rRihdl5bDXnoTKPiZzshsAO t5220M0HvQXVMAVrXGrcynwMnDu38+iU+aRdmx11NLvX4ZlLnGqEpdtbhK9ie1Uc 6diRZYeRPnu0TVtCRpU4Xvl42Iz7Vkne6+XWtYIXWELmc5lr+zvZqzNOXuV0=
X-Sasl-enc: gOqFKFG46nV+FPBUcvgpjRwoTsg4kuIfQUxe3bbCYNkH 1443166947
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id D6A3C680104; Fri, 25 Sep 2015 03:42:27 -0400 (EDT)
To: urn@ietf.org
References: <5603348F.9020307@seantek.com> <5603AB1D.6010703@it.aoyama.ac.jp> <5603FA95.5080609@network-heretics.com> <5604D98B.1060406@it.aoyama.ac.jp>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <5604FADA.6050309@network-heretics.com>
Date: Fri, 25 Sep 2015 03:42:18 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <5604D98B.1060406@it.aoyama.ac.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/9IgBnOA1facYt2Wi9LOmJyLJAjs>
Subject: Re: [urn] q-components, r-components, and resource transmission: Section 3.3
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 07:42:30 -0000

On 09/25/2015 01:20 AM, Martin J. DÃ¼rst wrote:
> On 2015/09/24 22:28, Keith Moore wrote:
>> On 09/24/2015 03:49 AM, Martin J. DÃ¼rst wrote:
>>>
>>> So I think it would be better to reword 3.3 to say "The q-component is
>>> intended for parameters that are part of resource identification, to
>>> be transmitted together with the other parts of the named resource."
>>
>> I don't think "part of resource identification" is a good way to
>> describe it because r-components can also be part of resource
>> identification.
>
> In my understanding, the r-components just help a resolver find the 
> resource, or some metadata about the resource (which of course in turn 
> also can be seen as a resource), but don't actually say anything about 
> the (primary) resource.

One potential way to use r-components is to narrow a selection between 
multiple representations of a resource, and of course each of those 
representations is itself a resource.

>
>> We need to make a clear distinction between parameters
>> that are transmitted to the service that provides the resource, and
>> parameters that influence the resolution process. Also, the q-components
>> aren't "transmitted together with the other parts of the named
>> resource"; they're not even necessarily transmitted together with the
>> other parts of the URL (HTTP works that way but that's not true for
>> other protocols in general).
>
> But that's how it would work for URNs, or not?

No.  URNs don't impose that constraint on the access protocol. (though 
to some degree this depends on what is meant by "transmitted together" - 
while it might be the case that a client has to pass both the location 
URL and the q-component/query to the resource, because the resource 
can't be expected to produce the correct result without having both of 
those pieces of information, nothing says that this has to be done by 
concatenating them together the way HTTP does.)

Keith


From nobody Fri Sep 25 06:19:51 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0A71A01FC for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 06:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 pRstx2xPqChs for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 06:19:49 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F51E1A0263 for <urn@ietf.org>; Fri, 25 Sep 2015 06:19:42 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0B045509BF for <urn@ietf.org>; Fri, 25 Sep 2015 09:19:40 -0400 (EDT)
To: "urn@ietf.org" <urn@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <560549D6.7060503@seantek.com>
Date: Fri, 25 Sep 2015 06:19:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020309000601050405060402"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/mQjkBK1HTOb1k3zc0h4vOVOvUmQ>
Subject: [urn] xmlns and rdf URNs moving forward
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 13:19:50 -0000

This is a cryptographically signed message in MIME format.

--------------ms020309000601050405060402
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

I just posted an announcement about the xmlns and rdf URN draft=20
(draft-seantek-xmlns-rdf-urns-01) to urn-nid@ietf.org. Interested=20
commentators are welcome to review the revised draft and provide feedback=
=2E

Thank you,

Sean


--------------ms020309000601050405060402
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjUxMzE5MThaMC8GCSqGSIb3DQEJBDEiBCDHzolPLtV2vNtg8XG/5uCx2odK/IlSVxb/1pae
ojegQDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQBQsjljPu22wZGM8FtL
xrQ+0IUEXEpBrS4RXe5Gb6Glyb1TXRJgksPt7QMO4jc7Ni+XxSjOPM1isUJ5lxNTtQ2RCDDU
kVxzCHFS4nm9YUAdxKvihLTsL/vNsN1pCwgnZInHKZKF6UwIvh92F2OjvGyTQLQ96G6Lm9Rx
L+WsG+lW9alBxm97ggImDv/m/emSDBgCL3HBM58kWaUIw7SMfZHu5M3qWqguLNqZME2fVMqI
cxCAnMzRPvxbCankLGy2F9n3s1vZOG1S0GwQ6dz5mHzAHQwDzBVY+CBC/Tt7LXx3BS5CbJmz
rM6CqRNdXuO3c8axQFDXc9UXIHNI3kmbXj/JAAAAAAAA
--------------ms020309000601050405060402--


From nobody Fri Sep 25 06:24:26 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49771A033B for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 06:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 drhMpUhBF8o9 for <urn@ietfa.amsl.com>; Fri, 25 Sep 2015 06:24:23 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0B41A0318 for <urn@ietf.org>; Fri, 25 Sep 2015 06:24:22 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C9E5B509C1 for <urn@ietf.org>; Fri, 25 Sep 2015 09:24:21 -0400 (EDT)
From: Sean Leonard <dev+ietf@seantek.com>
To: "urn@ietf.org" <urn@ietf.org>
Message-ID: <56054AEF.7000800@seantek.com>
Date: Fri, 25 Sep 2015 06:23:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040203010003020500030607"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/IzODvAsYrfxBR7kZk6Ws9vZXwvo>
Subject: [urn] resolver profiles: a generative POWER-UP for r-component
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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 Sep 2015 13:24:25 -0000

This is a cryptographically signed message in MIME format.

--------------ms040203010003020500030607
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

URNies:

What URNs really need is a way to ensure that the resolution process=20
delivers more consistent and predictable results.

Since the introduction of the r-component, URNs are now able to address=20
(speak to) the resolver directly to control aspects of the resolution=20
process. Yet the specifics are woefully absent in=20
draft-ietf-urnbis-rfc2141bis-urn-13.

I propose that the r-component begin with a resolver profile (or=20
resolution profile, or directive), which is an opaque string that=20
identifies the nature of the resolution services being requested by the=20
particular urn: URI. It's a POWER-UP =F0=9F=8D=84 for the r-component!

Consider our favorite urn:isbn. Given an ISBN, what can we do with it?=20
What do we want to get for it? And how can we make the f-component=20
meaningful, if the urn: URI string is not going to give us back some=20
kind of predictable media type/type of resource?

Answer: the namespace registration can include profiles, and these=20
profiles better specify what happens when resolution occurs. In our ISBN =

case, profiles can include:
showbook
librarycatalog
pricing
buybook
covershot
bibliographicinfo
referencedworks
=2E..and a potentially infinite range of other resolution things to do.

The absence of a profile string does not imply a "default" action. If=20
you specify urn:isbn:0385537670, you are left with just the identifier.=20
The implementation (context) can figure out whatever it wants to do.

To the extent that the resolver profile needs or accepts additional=20
data, this data can follow the profile string.

Examples include:

urn:isbn:0385537670?productphoto:dpi=3D600
urn:isbn:0385537670?pricing:au;used
urn:oid:1.3.6.1.5.5?info
urn:ietf:rfc:3986?getspec:ct=3Dtext/html#section-2.1

The syntax is:


       namestring    =3D assigned-name
                       [ "?" r-component ]
                       [ "#" f-component ]
       assigned-name =3D "urn" ":" NID ":" NSS
       NID           =3D (alphanum) 0*30(ldh) (alphanum)
       ldh           =3D alphanum / "-"
       NSS           =3D word
       r-component   =3D profile [":" query]
       profile       =3D NID
       ; query is from RFC 3986
       word          =3D pchar *(pchar / "/")
       f-component   =3D fragment



Unlike the NSS, which needs to be well-defined, durable, immutable,=20
etc., profiles are intended to be very lightweight and capricious. To=20
the extent that a namespace uses profiles at all, registration of=20
profiles would be either First-Come, First-Served, or Specification=20
Required. The namespace registration can impose restrictions on profiles =

(including disallowing profiles altogether), but anyone should be=20
permitted to invent a new profile, document it, and register it. [This=20
is a generative proposition--see David G. Post, The Theory of=20
Generativity, <http://ir.lawnet.fordham.edu/flr/vol78/iss6/2/>.]

Resolver profiles are namespace-specific, so "info" for the oid: URN=20
would have totally different semantics from "info" for the nato: URN or=20
service: URN.

The profile functions as a contract on how specific resolvers should=20
behave, including how the resolver should interpret the query parameters =

(string) and translate the information into resources (or into URLs that =

can be dereferenced into resources).

With this definition, there is no longer a q-component. Everything is on =

the r-component. Effectively the r-component is the query, but it's=20
addressed to and interpreted by the resolver.

That's the proposal. Comments welcome.

Sean


--------------ms040203010003020500030607
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CfYwggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw
CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4
dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu
dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh
TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak
+FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC
ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr
vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC
ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC
4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud
HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs
Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz
ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj
mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb
4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ
26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT
9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl
tukWeh95FPZKEBom+nyK+5swggU/MIIEJ6ADAgECAhAaQkrPJ/nEG3M8lirbnsnnMA0GCSqG
SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy
MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0EwHhcNMTUwMjAyMDAwMDAwWhcNMTYwMjAyMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkB
FhRkZXYraWV0ZkBzZWFudGVrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AM+J9tKgDs1LQtaDc+c4E58tCUQRNZiWbM1drOhLq2oSj75LuxPrrZy4XGjWoQFq9qGYHgiv
boRKoo2guKi2R5xrf/pZ27ELY5jCa3BQs4Q2YwziXWM5rktnFL2amO2MMwhuo0n7OIMDYftv
TEun2mOrnJ3G53zvawQdMbuRiHSNwc7DzWJwAjZQWFO8OF+BgNPzMDQGmzYQ4MVNk8NX5ecN
VbfusUU1wZOlfdy8lWTfcASDqa9jLoaAiSx2ay4q7/5m0BOWqOKZCS0f7MmIUtSqODEoiZkd
7oCj5MRKOg2ZLia33JN+oS5rTKN8rs4u4ZF5g8zypHS5TY/l3pNRlrcCAwEAAaOCAfIwggHu
MB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBQaZuXe8vDwU+ja
pyFW3zSvIW6TxjAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggr
BgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQv
Q1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NI
QTI1NkNsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUF
BwEBBIGDMIGAMFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9T
SEEyNTZDbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUF
BzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUZGV2K2lldGZAc2Vh
bnRlay5jb20wDQYJKoZIhvcNAQELBQADggEBAHiH/zXr779dLLJNLp6yW/RQvJSYuNbEqauQ
BWLZgvCF8FJjcS+y+bhN7RpTSVaEymbxnpJWFg0Qs6us6rXtttU6MF2JhTuxtu6yWW0EYy80
KGOt6zJRTxa46kAhAOqw4KPQ5RTvf/NT+2Qu8b2edlh+3t6f8iTQOAL/BNHnmr4QvpfnMLa8
NMAqd4FLOcSU9JKBlb5YtsEdfM3nBt4m95pfhpww79gB+zoXMoVaI+lfQHhkGth6mlaTkFUV
DT2pqq98XgESpObFEngb8ZRftBVoZfgJ4ajXcZnhKaqYEr23EtY207KgKb4LAXA84wtPcFfJ
rQaDArapR7xd2GNs+eYxggRBMIIEPQIBATCBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP
IENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhAaQkrPJ/nEG3M8lirbnsnnMA0GCWCGSAFlAwQC
AQUAoIICYTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA5
MjUxMzIzNTlaMC8GCSqGSIb3DQEJBDEiBCArvhMfGYwddmreZmpfDC1yheKQZbsHZecav4qK
2yp6zjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI
hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMIHBBgkrBgEEAYI3EAQxgbMwgbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQGkJKzyf5xBtzPJYq257J5zCBwwYLKoZIhvcNAQkQ
AgsxgbOggbAwgZsxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQD
EzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFp
bCBDQQIQGkJKzyf5xBtzPJYq257J5zANBgkqhkiG9w0BAQEFAASCAQA1Hrcbp/Myy28V4+Cj
3bcMtytE33JREcyMZMjXbBEheTM6Gypvi2zMRqS8kW0y/b9QNOcA7S5kBVV24BItGyfE72Sh
H2KUWsGsxnY49/2ASI4ahFeiI6g8BjOj9CGTAg/qHt6p0jNAF+nBxlkGZKRPj1jJ26Se7Ix1
BidpWllq0Ty3NN3ScNJkhLJ7YF7aQSh/CSYxzKVEX493NjhQKGCadx6c4yT5xMXv5+kk0UTu
s5uBfKZWSxIRvyxwep5VGAWq67LU6dTyzuUnFfDSq7NMF6FwbeVMYUES4bl+E/Vd2TtpMwQd
Gw95tqkdorI8z/sOyNi1v+3ES/jpmZ5wR1ZvAAAAAAAA
--------------ms040203010003020500030607--


From nobody Tue Sep 29 12:14:26 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1424C1B2B02 for <urn@ietfa.amsl.com>; Tue, 29 Sep 2015 12:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.122
X-Spam-Level: 
X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 uxQ_YTbBp4Gj for <urn@ietfa.amsl.com>; Tue, 29 Sep 2015 12:14:24 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E46EA1B4BA3 for <urn@ietf.org>; Tue, 29 Sep 2015 12:14:23 -0700 (PDT)
Received: by ioii196 with SMTP id i196so22261027ioi.3 for <urn@ietf.org>; Tue, 29 Sep 2015 12:14:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xxcYH9WuTSJ7LiULn9hGHz+u7FFi1P0dK+X1QcHJGUc=; b=TiNz3d8E3O3eLhIGFOG1Y98R0QboqvalMYrSMwN5wcR89yUgVNjjpJKmZ3YHD+nnCX bacjLClJaue+earlFwqrtQhtzkzPY1AWD5iAWlVL8mZpmIWFFROhWvfHmJqJL/57TUQz klhQMP3t7KCKZJLa/y0mvtTkm9zNFv5u9usn3H8e4qrctRz2uXF+Iw157S9pWYvBKhbs N5gt3YFURsD2hiDRTu/eUMjPIyWxr2fMZCBxJc1bQ7FfItYCWHnObevOStEU68wOg2fO UmDN+vABsSf5/SPpkOmPQ0MbEkPPz6Qcdn6J3xoPhIoZSAEPNxCf7C6Z6ycxP9druyZF NIyQ==
MIME-Version: 1.0
X-Received: by 10.107.18.231 with SMTP id 100mr410477ios.15.1443554063196; Tue, 29 Sep 2015 12:14:23 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.17.24 with HTTP; Tue, 29 Sep 2015 12:14:23 -0700 (PDT)
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6113A9EBA38@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <2D09D61DDFA73D4C884805CC7865E6113A9EBA38@GAALPA1MSGUSRBF.ITServices.sbc.com>
Date: Tue, 29 Sep 2015 15:14:23 -0400
X-Google-Sender-Auth: GSEKrA7ob9NvUrCxPzGr8UIBv_Y
Message-ID: <CAC4RtVD3PXRBTDT37EzUW2_sAPmO_uFn++kgcm+7PRSMaiUkhA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "STARK, BARBARA H" <bs7652@att.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/S5fZTokaKwFgii_ZntyFW0TYdFQ>
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] questions on new namespace registrations
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 29 Sep 2015 19:14:25 -0000

Hi, Barbara.  I'm sorry you haven't gotten a response to this yet, so
in the hope of getting either a "Yes, what Barry said," or a "Oh, my,
Barry's totally full of potatoes, and here's what you should do
instead of listening to him," I'll give an answer.

> I have a "friend" [...]  I think my friend needs advice.

Wink-wink.

> The 2 squatted namespace NIDs are derived from the current and former
> domain names. Hypothetically, I'll call these "dslforum-org" and
> "broadband-forum-org".
>
> Would it make sense to register both of these once the new
> registration process is in place?
>
> My friend has expressed some sensitivity that these look nothing like
> currently registered formal URNs (none of which have hyphens, and
> which are all shorter). Would it make sense to register a new formal
> NID (for example, "bbf") that looks more like the other formally
> registered URNs? Or, if the squatted ones were to be registered, would
> those be just fine, and my friend should feel no shame in the lengthy
> and hyphenated nature of those NIDs?

If the two in the first paragraph are already in use, I see no reason
to change them, and I'd suggest registering them as is.  If they're
theoretical, or if the current use is limited and easy to change, and
if they belong to the same organization (hypothetically, BBF), then
it'd be nicer (but not really because of the hyphens) to group them
together under the same NID, and just make them two "branches" that
are defined there (and then BBF could hypothetically define more
branches now or later if it needs them).

Barry

