Entertainment Identifier Registry (EIDR) URN Namespace Definition
draft-pal-eidr-urn-03

[Ballot discuss]
1515 Cordilleras Road in Redwood City is a residence.  This seems sketchy to me.  I'm not convinced that there's any action to take here, but I'd like to hear a bit more exposition on the topic, if the AD or authors have any to offer.

[Ballot comment]
Section 2:
"Additional prefix values conforming to the EIDR-PREFIX syntax
      might be introduced by EIDR organization in the future."

Is "EIDR organization" in the above sentence the same as the Entertainment Identifier Registry Association? If so, and if there is only one EIDR Association, it seems like it should be called "the EIDR Association" throughout this document.

Section 6:
"This document only specifies the syntax of the EIDR-URN namespace,
  and is therefore security-neutral."

This seems to imply that specifying a syntax is a security-neutral activity, but that's not always true, for example when the lexical equivalence procedure is poorly specified. I would recommend deleting this sentence and perhaps adding some text to the effect that failure to use the specified lexical equivalence procedure could result in granting unauthorized access to particular resources (if circumstances exist where EIDR-URNs identify resources that are under access control).

It also seems that https://doi.org/ is not accessible, so it may be worth noting that at present, the primary mechanism envisioned for resolving EIDR-URNs is not confidentiality protected.

IESG/Authors/WG Chairs:

IANA has reviewed draft-pal-eidr-urn-01.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

IANA's reviewer has the following comments/questions:

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

In the Formal URN Namespaces subregistry of the Uniform Resource Names (URN) Namespaces registry located at:

http://www.iana.org/assignments/urn-namespaces/

a single new URN Namespace is to be registered as follows:

URN Namespace: EIDR
Reference: [ RFC-to-be ]

IANA understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Entertainment Identifier Registry (EIDR) URN Namespace Definition) to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'Entertainment Identifier Registry (EIDR) URN Namespace Definition'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-05-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  Entertainment Identifier Registry (EIDR) Identifiers are used for the
  global unique identification of motion picture and television
  content.  This document defines the formal Uniform Resource Name
  (URN) Namespace Identifier (NID) for EIDR Identifiers.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-pal-eidr-urn/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-pal-eidr-urn/ballot/


No IPR declarations have been submitted directly on this I-D.

1. Summary
This document requests assignment of the URN NID "eidr", to be assigned
to the Entertainment Identifier Registry Association.  It is an
Informational document, required to be in the IETF stream by the
registration rules in RFC 3406.  Barry Leiba is the document shepherd
and responsible AD.

2. Review and Consensus
The document was reviewed in March on the urn-nid list, and the author
responded to comments by Ted Hardie and Dale Worley, making suitable
changes and clarifications.  There were no follow-up comments after the
update, and the document shepherd considers it to be ready to go.

[Note that the URNbis working group is in the process of proposing an
update to RFC 3406 that will change the registration procedure for URN
NIDs so that they no longer require IETF review.  In the meantime, we
will continue to get these rather straightforward requests in the IETF
stream.]

3. Intellectual Property
The author has no direct, personal knowledge of any IPR related to this
document.

4. Other Points
The "Intended status" line is missing from the draft's header.  It should
be thus: "Intended status: Informational"

1. Summary
This document requests assignment of the URN NID "eidr", to be assigned
to the Entertainment Identifier Registry Association.  It is an
Informational document, required to be in the IETF stream by the
registration rules in RFC 3406.  Barry Leiba is the document shepherd
and responsible AD.

2. Review and Consensus
The document was reviewed in March on the urn-nid list, and the author
responded to comments by Ted Hardie and Dale Worley, making suitable
changes and clarifications.  There were no follow-up comments after the
update, and the document shepherd considers it to be ready to go.

[Note that the URNbis working group is in the process of proposing an
update to RFC 3406 that will change the registration procedure for URN
NIDs so that they no longer require IETF review.  In the meantime, we
will continue to get these rather straightforward requests in the IETF
stream.]

3. Intellectual Property
The author has no direct, personal knowledge of any IPR related to this
document.

4. Other Points
None.

1. Summary
This document requests assignment of the URN NID "eidr", to be assigned to the Entertainment Identifier Registry Association.  It is an Informational document, required to be in the IETF stream by the registration rules in RFC 3406.  Barry Leiba is the document shepherd and responsible AD.

2. Review and Consensus
The document was reviewed in March on the urn-nid list, and the author responded to comments by Ted Hardie and Dale Worley, making suitable changes and clarifications.  There were no follow-up comments after the update, and the document shepherd considers it to be ready to go.

[Note that the URNbis working group is in the process of proposing an update to RFC 3406 that will change the registration procedure for URN NIDs so that they no longer require IETF review.  In the meantime, we will continue to get these rather straightforward requests in the IETF stream.]

3. Intellectual Property
The author has no direct, personal knowledge of any IPR related to this document.

4. Other Points
None.