RFC 7302

Entertainment Identifier Registry (EIDR) URN Namespace Definition

📅 published July 2014, from ietf

RFC 7302: Entertainment Identifier Registry (EIDR) URN Namespace Definition 🎬✨

Okay bestie, so the author is P. Lemieux from Sandflow Consulting LLC 💅 This is an Informational doc, dated July 2014, with ISSN 2070-1721. It's published for info, not as a Standards Track spec, so it's not a must-follow protocol rule 🎀

Abstract

Okay so EIDR Identifiers are used to uniquely ID motion pictures and TV content, globally 🎥 This doc defines the official URN Namespace Identifier (NID) for them 🦋

Status of This Memo

This doc is not an Internet Standards Track spec. It's just published for info 🌸

It's an IETF product, so it reflects the consensus of the IETF community. It got public review and the IESG approved it for publication. Not every IESG-approved doc is a candidate for any level of Internet Standard, so see Section 2 of RFC 5741 for that 🧐

For the current status, errata, and how to send feedback, check http://www.rfc-editor.org/info/rfc7302 💖

Copyright Notice

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as of the publication date. Read them carefully, because they explain your rights and restrictions 📜 Code Components pulled from this doc must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License 🧡

1. Introduction 🌷

So this doc defines the formal URN Namespace Identifier (NID) for EIDR Identifiers. Iconic 🙌

EIDR Identifiers are centrally registered, globally unique IDs for audiovisual works and their variants, mostly film and TV. A unique set of metadata parameters describing the work gets bound to the EIDR Identifier when it's registered 🎞️

EIDR Identifiers are a special kind of DOI Name allocated by EIDR Association just for audiovisual works. The Digital Object Identifier (DOI) system gives you persistent unique IDs for objects of any type, and it's specified in [ISO26234]. A DOI Name is the identifier permanently assigned to an object. DOI Names give you persistence, global uniqueness, and an open resolution infrastructure, which is giving reliability 💅

As a DOI Name, an EIDR Identifier has two parts: a prefix assigned exclusively to EIDR Association by the DOI Registration Authority, and a suffix defined by EIDR Association. Right now EIDR Identifiers use the prefix 10.5240, but more prefixes might show up later ✨

Here's an example EIDR Identifier in its canonical form:

        10.5240/7791-8534-2C23-9030-8610-5

Here 10.5240 is the prefix and 7791-8534-2C23-9030-8610-5 is the suffix. The canonical URN form of the same EIDR Identifier is:

        urn:eidr:10.5240:7791-8534-2C23-9030-8610-5

Note that : is the separator between prefix and suffix, because / is a URN reserved character. Bestie, that's the detail that matters 🫶

[EIDR-OVERVIEW] and [EIDR-INTRO] have more background info 📚

2. Completed URN Namespace Definition Template 🎀

The namespace definition follows the template in [RFC3406], and here's the tea:

Namespace ID:

eidr

Registration Information:

Version 1

2014-03-03

Declared registrant of the namespace:

Name: Entertainment Identifier Registry Association

Address:

c/o Alliances Management 544 Hillside Road Redwood City, CA 94062 USA

Contact:

URL: http://eidr.org/contact/ Email: info@eidr.org

Declaration of syntactic structure:

An EIDR Identifier is a special kind of DOI Name (see [ISO26234]), so it has two parts: a prefix called EIDR-PREFIX and a suffix called EIDR-SUFFIX. The URN representation URN-EIDR of an EIDR Identifier conforms to this syntax (written in [RFC5234]):

           URN-EIDR = "urn:eidr:" EIDR-NSS
           EIDR-NSS = EIDR-PREFIX ":" EIDR-SUFFIX
           EIDR-PREFIX = 1*EIDR-CHARS
           EIDR-SUFFIX = 1*EIDR-CHARS
           EIDR-CHARS = ALPHA / DIGIT / "-" / "." / "_"

The only EIDR-PREFIX value in use right now is 10.5240. More prefix values that fit the EIDR-PREFIX syntax might be introduced by EIDR Association later. Each of those would be linked to suffix values that match a subset of the EIDR-SUFFIX syntax. Those extra prefixes and their suffixes will be documented in future revisions of this registration 🌈

An implementation can process an EIDR-NSS with an unknown prefix as an opaque string under the "Rules of Lexical Equivalence" below, and resolve it as a generic DOI Name under the "Process for identifier resolution" below 🧚

When EIDR-PREFIX equals 10.5240, the EIDR-SUFFIX syntax gets extra limits from the RP2079-SUFFIX syntax in [SMPTERP2079]:

           RP2079-SUFFIX = 5(4HEXDIG "-") CHECK
           CHECK         = DIGIT / ALPHA

CHECK is the Mod 37,36 check character from [ISO7064], computed over the 20 hexadecimal digits HEXDIG of RP2079-SUFFIX 🔢

EXAMPLE: urn:eidr:10.5240:7791-8534-2C23-9030-8610-5

Relevant ancillary documentation:

[ISO26234] specifies DOI Name syntax and registration.

[SMPTERP2079] specifies the syntax of the EIDR Identifier with the prefix 10.5240.

Identifier uniqueness considerations:

An EIDR Identifier is a DOI Name. The ISO 26324 Registration Authority makes sure DOI Names are unique, so the URN-EIDR derived from an EIDR Identifier is guaranteed to be unique and never reassigned. That's main character energy 👑

Also, an EIDR Identifier is associated with a single URN-EIDR 💜

Identifier persistence considerations:

An EIDR Identifier is a DOI Name. The ISO 26324 Registration Authority makes sure a DOI Name stays valid indefinitely, so the URN-EIDR derived from an EIDR Identifier stays valid indefinitely too 🦋

Process of identifier assignment:

EIDR Association registers each EIDR Identifier with the ISO 26324 Registration Authority 📝

Entities in the motion picture and TV industry can apply for registrant status, whether they produce content directly or do distribution and related services. Registrants pay an annual membership fee, and it depends on the size of the company 💸

Process for identifier resolution:

As a DOI Name, the EIDR Identifier tied to an EIDR-NSS is resolved by the ISO 26324 Registration Authority 🔍

The ISO 26324 Registration Authority runs a web service. You resolve the EIDR Identifier tied to an EIDR-NSS by sending an HTTP GET request to this URI (see [RFC7231]):

               "http://doi.org/" EIDR-PREFIX "/" EIDR-SUFFIX

If the EIDR Identifier exists, you get back an XML Schema instance document (see [XMLSchema]) with metadata about it. If it doesn't exist, you get the HTTP status code "404 Not Found" 🙈

EXAMPLE: http://doi.org/10.5240/7791-8534-2C23-9030-8610-5

NOTE: At the time of this writing, this ISO 26324 Registration Authority service is not available over TLS, so the confidentiality of queries is not protected. Yikes, that's a big 💀

EIDR Association runs extra services just for EIDR users (see [EIDR-SERVICES]). These include extra features, like confidential lookup over TLS and the ability to register EIDR Identifiers 🔐

Rules for Lexical Equivalence:

Lexical equivalence of EIDR-URN is defined by a case-insensitive string match 🔤

Conformance with URN Syntax:

As specified above, the EIDR-URN syntax is a subset of the URN syntax in [RFC2141] 🧩

Validation mechanism:

The validity of an EIDR-NSS can only be guaranteed by completing the resolution process 💯

For EIDR-NSS with an EIDR-PREFIX equal to 10.5240, the CHECK value can be used for integrity checking, as specified above ✅

Scope:

EIDR Identifiers are centrally registered, globally unique identifiers for audiovisual works worldwide 🌍

3. Namespace Considerations 🌟

EIDR Identifiers are meant for Internet applications, where URNs are routinely used to identify audiovisual resources. There's no direct mapping from EIDR Identifiers to existing URN namespaces 🙌

4. Community Considerations 🫶

The primary registrants of EIDR Identifiers are producers and distributors of audiovisual works, metadata aggregators, and audiovisual archives. Any bona fide member of the ecosystem can become an EIDR member and register any work. Anyone can use EIDR Identifiers to unambiguously identify an audiovisual asset and retrieve its underlying metadata. The main benefits show up with works in wide distribution, long or complex distribution chains, and information aggregated from multiple sources 🎬✨

5. IANA Considerations 🌸

IANA registered the Formal URN Namespace eidr in the "Uniform Resource Names (URN) Namespaces" registry, using the registration template in Section 2 of this document 📋

6. Security Considerations 🔐

This doc specifies the syntax of the EIDR-URN namespace and makes no security representations. The details of the assignment and resolution processes are defined outside this doc by EIDR Association and the ISO 26324 Registration Authority, so they're out of scope here.

⚠️ Bestie, this part is serious. If you don't follow the syntactic and lexical equivalence rules in this spec when you use an EIDR Identifier as the criteria for accessing restricted resources, you can accidentally grant unauthorized access to those resources. Not okay, so please don't skip the rules 🚨

7. References 📚

7.1. Normative References

[ISO26234] International Organization for Standardization, "Information and documentation - Digital object identifier system", ISO Standard 26324, 2012.

[ISO7064] International Organization for Standardization, "Information technology - Security techniques - Check character systems", ISO Standard 7064, 2003.

[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.

[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.

[SMPTERP2079] Society of Motion Picture and Television Engineers, "Digital Object Identifier (DOI) Name and Entertainment ID Registry (EIDR) Identifier Representations", SMPTE RP 2079, 2014.

7.2. Informative References

bestie, these are the "go read this if you want more" docs 📚🫶 They aren't required reading, but they're good background. Every title, date, and URL is kept exactly as the original.

[EIDR-INTRO] 🎬 Entertainment Identifier Registry Association, "EIDR: ID Format Ver. 1.1", August 2013, <http://eidr.org/documents/EIDR_ID_Format_v1.1.pdf>. ✨ This is the ID format doc for EIDR.

[EIDR-OVERVIEW] 🌸 Entertainment Identifier Registry Association, "EIDR Overview", November 2013, <http://eidr.org/documents/2013-11-01_EIDR_Overview_FINAL.pdf>. ✨ The big-picture intro to EIDR.

[EIDR-SERVICES] 💖 Entertainment Identifier Registry Association, "EIDR System Version 2.0: Registry User's Guide", August 2013, <http://eidr.org/documents/EIDR_2.0_Registry_User_Guide.pdf>. ✨ The user's guide for the EIDR registry.

[RFC3406] 🦋 Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. ✨ This is the URN namespace definition mechanisms doc, and it's a BCP, so it's basically the rulebook for how URN namespaces get defined. Iconic 👑

[RFC7231] 💜 Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, June 2014. ✨ The HTTP semantics doc, which is literally the core of how HTTP works 🔥

[XMLSchema] 🧚 Holstege, M. and A. Vedamuthu, "W3C XML Schema Definition Language (XSD): Component Designators", W3C Candidate Recommendation CR-xmlschema-ref-20100119, January 2010, <http://www.w3.org/TR/2010/CR-xmlschema-ref-20100119>. ✨ The XML Schema component designators spec, and yes, the name is a whole mouthful 💀

Author's Address ✨

Here's who wrote it 🎀

Pierre-Anthony Lemieux
Sandflow Consulting LLC

EMail: pal@sandflow.com

That's the whole doc, bestie! 💅🌈

📦 where this page comes from

ietf: rfc7302 2014-07
💖 girlified by claude-haiku-5-5 on 2026-10-18: a language model's rewrite of the original, under its terms