Last Call Review of draft-pal-eidr-urn-01

Request Review of draft-pal-eidr-urn
Requested rev. no specific revision (document currently at 03)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-05-16
Requested 2014-04-24
Authors Pierre-Anthony Lemieux
Draft last updated 2014-04-30
Completed reviews Genart Last Call review of -01 by Elwyn Davies (diff)
Genart Telechat review of -02 by Elwyn Davies (diff)
Secdir Last Call review of -01 by Magnus Nystrom (diff)
Opsdir Last Call review of -01 by Scott Bradner (diff)
Assignment Reviewer Elwyn Davies 
State Completed
Review review-pal-eidr-urn-01-genart-lc-davies-2014-04-30
Reviewed rev. 01 (document currently at 03)
Review result Ready with Nits
Review completed: 2014-04-30


I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at


Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-pal-eidr-urn-01.txt
Reviewer: Elwyn Davies
Review Date: 25 April 2014
IETF LC End Date: 16 May 2014
IESG Telechat date: (if known) -

Summary: Ready with very minor nits.

Query/Suggestion:  I don't know if creating IANA registries for
EIDR-PREFIXes and corresponding EIDR-SUFFIX types has been considered.
If additional prefixes are likely to have the same suffix format (i.e.,
just fulfilling a need for more space), then considerable future effort
could be avoided by using expert review by someone from EIRA or SMPTE to
add new prefixes.  Of course it may be that new prefixes are not likely
to be needed too often and anyway would need a new suffix format, in
which case this is irrelevant.  Just a thought!

Major issues:

Minor issues:

Nits/editorial comments:
Header: Shouuld spcify the intended status (which is Informational
according to the tracker).

Abstact: s/global/globally/

s1, para 2: s/time of registration/the time of registration/

s2 title and para 1: It would be more appropriate to title this section 
   'Completed URN Namespace Definition Template'
and make para 1 something like:
   The namespece definition according to the template in [RFC3406] is as

s2, example:
The example

 is a
working EIDR DOI for the movie "Superman Returns".  Whilst this
illustrates the namespace very well, it is normally good to use a dummy
example to avoid any downstream issues (I don't see that the owners of
the film would complain, but other might look on it as favouritism). 
Would it be possible to create a dummy working EIDR that could be used
in the RFC?