RE: urn:oid:

Phillip Maness <> Mon, 17 March 2014 18:16 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 68FE51A0462 for <>; Mon, 17 Mar 2014 11:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2lHomvqFZypO for <>; Mon, 17 Mar 2014 11:16:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EA0241A01D5 for <>; Mon, 17 Mar 2014 11:16:55 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.898.11; Mon, 17 Mar 2014 18:16:45 +0000
Received: from (2a01:111:f400:7c10::1:164) by (2a01:111:e400:2c16::40) with Microsoft SMTP Server (TLS) id 15.0.898.11 via Frontend Transport; Mon, 17 Mar 2014 18:16:45 +0000
Received: from LAX-EXCA02.dts.local ( by ( with Microsoft SMTP Server (TLS) id 15.0.898.8 via Frontend Transport; Mon, 17 Mar 2014 18:16:44 +0000
Received: from LAX-EXMB02.dts.local ([fe80::b50e:9af7:de19:4aa9]) by LAX-EXCA02.dts.local ([fe80::5efe:]) with mapi id 14.03.0181.006; Mon, 17 Mar 2014 11:16:43 -0700
From: Phillip Maness <>
To: "Dale R. Worley" <>, "Martin J. DC<rst" <>
Subject: RE: urn:oid:
Thread-Topic: urn:oid:
Thread-Index: AQHPPy1/azGiyYDURGqVULMjcCC13prlk3IBgAABiSA=
Date: Mon, 17 Mar 2014 18:16:42 +0000
Message-ID: <520A56052CF01E42B1C128F990FBE681A47200AE@LAX-EXMB02.dts.local>
References: <520A56052CF01E42B1C128F990FBE681A4715F92@LAX-EXMB02.dts.local> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(438001)(85714005)(189002)(199002)(377454003)(377424004)(164054003)(51704005)(13464003)(92566001)(85852003)(92726001)(83072002)(23726002)(33656001)(93136001)(90146001)(81342001)(56816005)(81542001)(85306002)(56776001)(76482001)(46102001)(54316002)(53806001)(2656002)(87936001)(46406003)(4396001)(69226001)(87266001)(47736001)(49866001)(47976001)(50986001)(19580395003)(55846006)(97186001)(19580405001)(83322001)(74876001)(94946001)(81686001)(65816001)(74366001)(80022001)(79102001)(50466002)(80976001)(77982001)(44976005)(94316002)(54356001)(59766001)(47776003)(97756001)(63696002)(20776003)(93516002)(86362001)(76786001)(81816001)(77096001)(6806004)(74706001)(31966008)(74662001)(47446002)(95666003)(76796001)(95416001)(74502001)(97336001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR01MB474; H:LAX-EXCA02.dts.local; FPR:CAEEF30D.AC23A798.E9F39DDB.C6E2CD41.20360; MLV:sfv; PTR:.; MX:1; A:1; LANG:en;
X-Forefront-PRVS: 0153A8321A
Received-SPF: Pass (: domain of designates as permitted sender) receiver=; client-ip=; helo=LAX-EXCA02.dts.local;
Cc: "" <>, "Mark R. Johnson" <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 17 Mar 2014 18:16:58 -0000

Hi Dale,

Just for clarification, when you say "permanent" are you referring to a persistent instance of "identifier" or a persistent meaning of "identifier".

In all applications where I would use an identifier, the meaning would never change (it couldn't, applications would cease to function correctly). They usually do have a value parameter that changes. The documents they appear in, (often an XML manifest), typically live for anywhere from a few minutes to a few days.


-----Original Message-----
From: Dale R. Worley []
Sent: Monday, March 17, 2014 5:40 PM
To: Martin J. DC<rst
Cc: Phillip Maness;; Mark R. Johnson
Subject: Re: urn:oid:

> From: "Martin J. DC<rst" <>

> Domain names are being changed and reused all the time. And
> people/organizations who reuse them usually don't know what URNs their
> predecessors have minted, nor would they care.

A workable solution is to attach to the domain name the date on which the organization had possession of the domain name.  That solution is used in the "tag" scheme (RFC 4151):

   Examples of tag URIs are:,2001:web/externalHome,2004-05:Sandro,2001-09-15:TimKindberg:presentations:UBath2004-05-19,1999:blog-555,2002:int

and in draft-ietf-salud-alert-info-urns "alert" URN extension elements:

But in general, domain names shouldn't be incorporated into permanent identifiers.



This message and any included attachments are intended only for the use of the addressee, and may contain information that is privileged or confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please destroy the original message and any copies or printouts hereof.