Re: [urn] call for comments: an alternative 2141bis document

Larry Masinter <masinter@adobe.com> Mon, 19 November 2012 09:58 UTC

Return-Path: <masinter@adobe.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1AB21F859D for <urn@ietfa.amsl.com>; Mon, 19 Nov 2012 01:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.949
X-Spam-Level:
X-Spam-Status: No, score=-103.949 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0t9NCC9O1sZF for <urn@ietfa.amsl.com>; Mon, 19 Nov 2012 01:58:52 -0800 (PST)
Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id 50A0D21F855E for <urn@ietf.org>; Mon, 19 Nov 2012 01:58:47 -0800 (PST)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUKoC1j9RaUy3eZb6/Vd6Af1xJXxc0uRQ@postini.com; Mon, 19 Nov 2012 01:58:51 PST
Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id qAJ9wjHP025780; Mon, 19 Nov 2012 01:58:45 -0800 (PST)
Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id qAJ9whXL022981; Mon, 19 Nov 2012 01:58:44 -0800 (PST)
Received: from SJ1SWM219.corp.adobe.com (10.5.77.61) by nacas01.corp.adobe.com (10.8.189.99) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 19 Nov 2012 01:58:43 -0800
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by SJ1SWM219.corp.adobe.com ([fe80::d55c:7209:7a34:fcf7%11]) with mapi; Mon, 19 Nov 2012 01:58:43 -0800
From: Larry Masinter <masinter@adobe.com>
To: Renato Iannella <ri@semanticidentity.com>
Date: Mon, 19 Nov 2012 01:58:41 -0800
Thread-Topic: [urn] call for comments: an alternative 2141bis document
Thread-Index: Ac3CAsOg49fkoc20RrOZBPf2a3a46AENqRmw
Message-ID: <C68CB012D9182D408CED7B884F441D4D1E3702754D@nambxv01a.corp.adobe.com>
References: <CAAQiQRe+wCBmKfm7up8XY-4RxLnktZiz+nuanprygGcHAYdqAw@mail.gmail.com> <C68CB012D9182D408CED7B884F441D4D1E36EF2DC4@nambxv01a.corp.adobe.com> <F97E15A0-480C-414B-A4E4-A8F5C2037153@semanticidentity.com>
In-Reply-To: <F97E15A0-480C-414B-A4E4-A8F5C2037153@semanticidentity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] call for comments: an alternative 2141bis document
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 09:58:53 -0000

> Hi Larry....as we all know, it is impossible to say that _anything_ will be
> persistent (even beyond our lifetimes) in this industry.
http://masinter.blogspot.com/2010/03/ozymandias-uri.html

> But I think that at least URNs _try_ to highlight to URN operators that they need
> to consider longevity
http://tools.ietf.org/html/draft-saintandre-urnbis-3406bis-00#section-5.1

There is no clear line between meeting the requirements for "formal" and not; we (the IETF reviewers) are being asked to judge something we have little qualification to judge, namely the likely longevity of an organization's ability to "resolve" names for some period of time (how long?), and whether that registration and resolution service will remain "open" (in what way?) for an indefinite amount of time (how long?).

I like the criteria, just I'm uneasy about IETF judging them without bikeshedding.

> and the fact the URNs are not dependent on the DNS and the opaque NSS help
> towards that goal....but still requires ORG support for this to be realised (hence
> a dependency on ORG persistence).

I assume you mean "organizational" by "ORG" and not something more formal.
Of course URLs aren't all dependent on DNS either.  You're not saying why tel: is a URI scheme and not a URN namespace? 
r
I'm not sure what you mean by "opaque NSS".

> Perhaps we can update 3406bis and 2141bis along these lines. That is, qualify the
> "persistent, location-independent" statement with qualification.

I think it's a mistake to believe that URNs accomplish either of those, and people often skip the qualifications. URNs are not persistent. And "location-independent" cannot be determined.