Re: Application for a formal URN NID ("EIDR")

Ted Hardie <> Wed, 05 February 2014 19:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B3A3B1A00FA for <>; Wed, 5 Feb 2014 11:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IE5wnFENT_zb for <>; Wed, 5 Feb 2014 11:14:18 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c05::22c]) by (Postfix) with ESMTP id 344CE1A00EB for <>; Wed, 5 Feb 2014 11:14:18 -0800 (PST)
Received: by with SMTP id k19so13922787igc.5 for <>; Wed, 05 Feb 2014 11:14:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+yU+sVRTKnGIlQLmO43xC5tbM9pQvA8Seru48WeyCeE=; b=iVuMWj77X4CDU0Xym9SPJd8NHYZlllmRjVsiDiUkexso6Tg6R+Vu+Dw0yZXVUBwKBH kxhLSI+zbRuage6uPBXpBs8lZMz+VQynuGAfRu8jEXJcTuJlU7hoJ2VSmQdfh6H+sKYp oKLa6+XuaVxTEqmVxXc4bPnv0HI1AxXKHz4RtFAuP6fKgXwMRptq7CjkGlyo0AToS4L6 jAb1VoB+2SOyz0l9+zK91u7UgNr17JwaWI22Lb6t43aO8xDuIMraeL78XaCL7qbnxuO2 keC8Nupm+/ATrEfjmuYReuifrigBX2Ezhy7ulesTEzVgEZomoOHp4JLbWBwnRJ3Stt6+ Z8Ow==
MIME-Version: 1.0
X-Received: by with SMTP id jd1mr2491733icb.62.1391627656241; Wed, 05 Feb 2014 11:14:16 -0800 (PST)
Received: by with HTTP; Wed, 5 Feb 2014 11:14:16 -0800 (PST)
In-Reply-To: <>
References: <>
Date: Wed, 5 Feb 2014 11:14:16 -0800
Message-ID: <>
Subject: Re: Application for a formal URN NID ("EIDR")
From: Ted Hardie <>
To: Pierre-Anthony Lemieux <>
Content-Type: multipart/alternative; boundary=001a1132e4cc1c274a04f1ad9067
Cc: "" <>
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: Wed, 05 Feb 2014 19:14:20 -0000

Thanks for sending your draft for review.  A few quick points:

The draft currently says:


This would seem to imply that any DOI prefix may be
encountered and that this NID could be used with any
registered DOI.  IF that were the intent, I would

suggest registering the namespace "DOI" instead.  I
understand that the DOI folks have consciously chosen not
to do that(cf:,

though, so I suspect your intent is to limit this to a subset
of DOIs.  Is that correct?  Is it essentially limited to 10.5240?
If not, how will the appropriate subset be identified?

This comes up again here:

When DOI-PREFIX is equal to "10.5240", the syntax of DOI-SUFFIX is
further constrained according to [SMPTERP2079] as follows:

           EIDR-SUFFIX  = 5*5(4*4HEXDIG "-") CHECK
           DIGIT        = %x30-39
           HEXDIG       = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
           ALPHA        = %x41-5A / %x61-7A
           CHECK        = DIGIT / ALPHA

I don't think this says quite what you intend.  I think what you

intend is to say is that the overall syntax is roughly either:




If the use of the URN is only for 10.5240, then you can just
drop the second syntax.  If it is for a set of DOI prefixes,
none of which but 10.5240 is intended to have this restriction,

then I believe you want to say, roughly:


where EIDR-SUFFIX has a choice pattern:


And the list of DOI prefixes suitable for EIDR-PREFIX is
set you register as such. The syntax of the prefix can still

match the general DOI prefix.

Later, the document says:

Rules for Lexical Equivalence:

      Two EIDR-NSS are equivalent if and only if they are equal.  EIDR-
      NSS are case-insensitive.

"equal" here doesn't have a precise meaning.  I'd suggest that

you say something like "are lexically equivalent based on
a case insensitive string match"


Ted Hardie

On Tue, Feb 4, 2014 at 10:32 PM, Pierre-Anthony Lemieux <>wrote;wrote:

> Good morning/evening,
> Per IETF RFC 3406, please find at the link below an application for a
> formal URN NID ("EIDR").
> Very much Looking forward to your comments and feedback. Let me know
> if you need additional information.
> Best,
> -- Pierre [on behalf of MovieLabs (]