Re: [urn] Are ISO 3166 country codes stable enough for URN use?

"Phillips, Addison" <addison@lab126.com> Sun, 21 February 2016 20:56 UTC

Return-Path: <prvs=852589ea3=addison@lab126.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 CEB951A903B for <urn@ietfa.amsl.com>; Sun, 21 Feb 2016 12:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.3
X-Spam-Level:
X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-5, TVD_FROM_1=0.999] 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 FphhEQ0ADwVM for <urn@ietfa.amsl.com>; Sun, 21 Feb 2016 12:56:44 -0800 (PST)
Received: from smtp-fw-9101.amazon.com (smtp-fw-9101.amazon.com [207.171.184.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED2B1A92EF for <urn@ietf.org>; Sun, 21 Feb 2016 12:56:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,482,1449532800"; d="scan'208,217";a="469129173"
Received: from sea19-co-svc-lb5-vlan3.sea.amazon.com (HELO email-inbound-relay-64008.pdx4.amazon.com) ([10.47.22.166]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Feb 2016 20:56:40 +0000
Received: from ex10-hub-7001.ant.amazon.com (pdx1-ws-svc-lb16-vlan3.amazon.com [10.239.138.214]) by email-inbound-relay-64008.pdx4.amazon.com (8.14.7/8.14.7) with ESMTP id u1LKubYb000802 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 21 Feb 2016 20:56:38 GMT
Received: from EX13D08UWB004.ant.amazon.com (10.43.161.232) by ex10-hub-7001.ant.amazon.com (10.43.103.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Sun, 21 Feb 2016 12:56:37 -0800
Received: from EX13D08UWB003.ant.amazon.com (10.43.161.186) by EX13D08UWB004.ant.amazon.com (10.43.161.232) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sun, 21 Feb 2016 20:56:36 +0000
Received: from EX13D08UWB003.ant.amazon.com ([10.43.161.186]) by EX13D08UWB003.ant.amazon.com ([10.43.161.186]) with mapi id 15.00.1076.000; Sun, 21 Feb 2016 20:56:36 +0000
From: "Phillips, Addison" <addison@lab126.com>
To: Sean Leonard <dev+ietf@seantek.com>, John C Klensin <john@jck.com>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Are ISO 3166 country codes stable enough for URN use?
Thread-Index: AQHRbOC1lAcisi/u0kSqRw25RHBqK5829QeAgAAAnwCAAAVNKg==
Date: Sun, 21 Feb 2016 20:56:36 +0000
Message-ID: <7req9kjyve7mdncaaxk7omij.1456091779789@email.android.com>
References: <56CA13F5.7070707@seantek.com> <1804C7530E646E7F15CDD2E8@JcK-HP5.jck.com>,<56CA2012.3060504@seantek.com>
In-Reply-To: <56CA2012.3060504@seantek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_7req9kjyve7mdncaaxk7omij1456091779789emailandroidcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/b-KR2knShqY9lSplINNBizz9A34>
Subject: Re: [urn] Are ISO 3166 country codes stable enough for URN use?
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, 21 Feb 2016 20:56:48 -0000

If you were still concerned about 3166 stability, note the the language subtag registry (BCP 47) maintains a stabilized version for the region set of subtags. Because it still isn't okay to reuse the codes, even over periods longer than five years.

(Sent from my Fire tablet)


On February 22, 2016, at 12:39 AM, Sean Leonard <dev+ietf@seantek.com> wrote:

Ok.

It sounds like the durability and persistence requirements for URNs are
being relaxed somewhat, compared to the old days.

I'm fine with that, carry on.

Sean

On 2/21/2016 12:35 PM, John C Klensin wrote:
> Sean,
>
> Very briefly and having spend far too much time immersed in a
> well-known use of 3166 and it implications, two observations:
>
> (1) The "we can, and probably will, reassign a code after five
> years" rule have been dead for some years.  You should be
> careful about what you treat as an authoritative reference.
> Because of (2), I may regret even mentioning that.
>
> (2) The definition of "persistent enough" or "stable enough"
> inevitably has to be per-namespace.  One of the earliest
> examples in the discussions that led to URNs was "the weather
> in..." which can be as stable as location names are as a
> reference but whose object is typically entirely unstable.
>
> This isn't a WG topic.  When the NDN spec is revised, you can
> certainly have the discussion in the context of that revision
> (assuming they don't simply decide to register something based
> on a document published elsewhere which, fwiw, is certainly what
> I would be inclined to do if I were in their position).
>
>     john
>
>
> --On Sunday, February 21, 2016 11:45 AM -0800 Sean Leonard
> <dev+ietf@seantek.com> wrote:
>
>> In reviewing the latest draft-ietf-urnbis-ns-reg-transition, I
>> noticed the dependency on NBN [RFC3188], which in turn depends
>> on ISO 3166.
>>
>> An example is <URN:NBN:fi-fe19981001>.
>>
>> URNs are supposed to be stable and durable over time...
>>
>> but are ISO 3166 country codes stable enough for URN?
>>
>> I have not actually read all of the details of ISO 3166. But
>> ISO 3166 grapples with an intensely political question: how to
>> name countries. I read this PDF:
>> http://unstats.un.org/unsd/tradekb/Attachment194.aspx
>>
>> And it says that "withdrawn [codes] may not be reused for five
>> years". That means that they can be reused in five years. I
>> think that violates some URN principles.
>>
>> NBN isn't the first time we have seen ISO 3166 country codes
>> in URNs. There is the urn:lex proposal (not really sure where
>> that is now).
>>
>> There are also my proposals for urn:xmlns and urn:rdf. However
>> in my proposals, the entire NSS is assigned on a first-come,
>> first-served basis: the relationship between two- and
>> three-character ISO 3166 country codes being part of the NSS
>> is purely a coincidence and therefore reassignment of a
>> country code does not affect the durability and immutability
>> of the assigned string.
>>
>> Sean
>>
>> _______________________________________________
>> urn mailing list
>> urn@ietf.org
>> https://www.ietf.org/mailman/listinfo/urn
>
>
>

_______________________________________________
urn mailing list
urn@ietf.org
https://www.ietf.org/mailman/listinfo/urn