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

[Ballot comment]
My initial comment: I guess that the Appendix A1 and, as a consequence, section 7.3, will disappear.

Discussing some more with Pierre-Anthony,  I was puzzled by the URIs section 7.3. I was thinking that this section would disappear, and that it was the reason for having this specific URIs section, as opposed to having an extra informative reference.

Pierre-Anthony's answer:
Yes, I was equally puzzled with xml2rfc creating a dedicated "URL"
section when referencing a URL, instead of merely adding the URL to
the informative reference.

rfcdiff

I assumed it was by design. It would be simply to create an
informative reference.

So whatever, the RFC-editor will take of this, if some changes are required.

Technical Summary

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

  This document revises RFC 7302 in order to introduce HTTPS resolution process.

Working Group Summary

  This is not a WG document.

Document Quality

  This is a minor update to RFC 7302.

Personnel

  Alexey Melnikov is the Responsible Area Director.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-pal-eidr-urn-2016-01.txt. If any part of this review is inaccurate, please let us know.

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

IANA notes that RFC7302 registered the eidr URN. This document appears to revise the template for that registration, but makes no change to the registration in the Formal URN Namespaces subregistry of the Uniform Resource Names (URN) Namespaces located at:

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

Upon approval of this document the reference for the eidr URN will be changed from RFC7302 to [ 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. 


Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: alexey.melnikov@isode.com, draft-pal-eidr-urn-2016@ietf.org
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 2016-07-01. 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
  globally unique identification of motion picture and television
  content.  This document defines the formal Uniform Resource Name
  (URN) Namespace Identifier (NID) for EIDR Identifiers.

  This document revises Request For Comments (RFC) 7302 -- see
  Appendix A for a summary of changes.




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

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


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