<?xml version='1.0' encoding='UTF-8'?>
<rfc ipr='trust200902' docName='draft-pal-eidr-urn-00'>
	<front>
		<title  abbrev='EIDR URN Namespace Definition'>Entertainment ID Registry (EIDR) URN Namespace Definition</title>
		<author initials='P.-A.' surname='Lemieux' fullname='Pierre-Anthony Lemieux'>
			<organization>Sandflow Consulting LLC</organization>
			<address>
				<email>pal@sandflow.com</email>
			</address>
		</author>
		<date month='February' year='2014' />

		<area>General</area>
		<workgroup>Network Working Group</workgroup>
		<keyword>RFC</keyword>
		<keyword>Request for Comments</keyword>
		<keyword>I-D</keyword>
		<keyword>Internet-Draft</keyword>
		<keyword>EIDR</keyword>
		<keyword>Entertainment Identifier Registry</keyword>
		<keyword>URN</keyword>
		<abstract>
			<t>Entertainment ID Registry (EIDR) Identifiers are used for the global unique identification of motion picture and television content. This document defines formal Uniform Resource Name (URN) Namespace Identifier (NID) for EIDR Identifiers.</t>
		</abstract>
	</front>
	<middle>
		<section anchor='intro' title='Introduction'>
			<t>This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) for EIDR Identifiers.</t>
						<t>EIDR Identifiers are centrally registered, globally unique identifiers for audiovisual works and their variants, primarily film and television. A unique set of metadata parameters describing the associated work is bound to the EIDR Identifier at time of registration -- see <xref target='EIDR-OVERVIEW'/> and <xref target='EIDR-INTRO'/> for background information.</t>

		</section>
		<section title='URN Namespace Definition Template'>
			<t>The following template is provided in accordance with <xref target='RFC3406'/>.</t>
			<t>Namespace ID:
				<list>
					<t>EIDR</t>
				</list>		
			</t>

			<t>Registration Information:
				<list>
					<t>Version 1</t>
					<t>2014-02-04</t>
				</list>
			</t>

			<t>Declared registrant of the namespace:
				<list>
					<t>Name:<list>
							<t>Entertainment ID Registry</t>
						</list>
					</t>
					<t>Address:<list>
							<t>1515 Cordilleras Road.<vspace/>Redwood City, CA 94062<vspace/>USA</t>
						</list>
					</t>
					<t>Contact:<list>
							<t>Richard Kroon<vspace/>E-mail: rkroon@eidr.org</t>
						</list>
					</t>
				</list>
			</t>
			<t>Declaration of syntactic structure:
				<list>
					<t>The URN representation of an EIDR Identifier conforms to the following syntax (expressed using <xref target='RFC2234'/>):
						<figure>
							<artwork>
						<![CDATA[
		URN-EIDR = "URN:EIDR:" EIDR-NSS
		EIDR-NSS = DOI-PREFIX ":" DOI-SUFFIX]]>
							</artwork>
						</figure>
						
						where DOI-PREFIX and DOI-SUFFIX are DOI Name prefix and suffix, respectively, translated into canonical NSS format according to <xref target='RFC2141'/>. DOI Name syntax is specified in <xref target='ISO26234'/>.</t>
<t>
NOTE: The canonical string representation of an EIDR Identifier uses "/" instead of ":" as the delimiter between DOI-PREFIX and DOI-SUFFIX. ":" is used here since "/" is a reserved character.</t>

					<t>When DOI-PREFIX is equal to "10.5240", the syntax of DOI-SUFFIX is further constrained according to <xref target='SMPTERP2079'/> as follows:<figure>
							<artwork>
								<![CDATA[
		DOI-SUFFIX   = EIDR-SUFFIX
		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 ]]>
							</artwork>
						</figure>
							where CHECK is the Mod 37,36 check character as specified in <xref target='ISO7064'/>, computed over the 20 hexadecimal digits HEXDIG of EIDR-SUFFIX.</t>

					<t>EXAMPLE: URN:EIDR:10.5240:68DD-341E-03EE-4BB8-1761-Q</t>
					
					<t>NOTE: Other values DOI-PREFIX might be used for EIDR Identifiers in the future.</t>
				</list>
			</t>	
			<t>Relevant ancillary documentation:
				<list>
					<t>
						<xref target='ISO26234' /> specifies DOI Name syntax and registration.</t>
					<t>
						<xref target='SMPTERP2079' /> specifies a specific kind of EIDR Identifier.</t>
				</list>
			</t>
			<t>Identifier uniqueness considerations:

				<list>
					<t>An EIDR Identifier is a DOI Name. As such, the uniqueness of the combination of DOI-PREFIX and DOI-SUFFIX, and thus EIDR-NSS, is guaranteed by the ISO 26324 Registration Authority. A DOI Name is never reassigned.</t>
				</list>
			</t>
			<t>Identifier persistence considerations:

				<list>
					<t>As a DOI Name, the persistence of EIDR-NSS is guaranteed by the ISO 26324 Registration Authority. A DOI Name remains valid indefinitely.</t>
				</list>
			</t>

			<t>Process of identifier assignment:

				<list>
					<t>EIDR-NSS values are assigned by the EIDR organization, which registers the underlying DOI Name with the ISO 26324 Registration Authority.</t>

					<t>Entities involved in the motion picture and television industry, either directly in the production of content or in its distribution and related services, are eligible to apply for registrant status. Registrants pay an annual membership fee that depends on the size of the company.</t>
				</list>
			</t>

			<t>Process for identifier resolution:

				<list>
					<t>As a DOI Name, the resolution of EIDR-NSS is handled by the ISO 26324 Registration Authority.</t>

					<t>The ISO 26324 Registration Authority operates a web service that allows an EIDR-NSS to be resolved by issuing an HTTP GET request to the following URI:
						<figure>
							<artwork>
			"http://doi.org/" DOI-PREFIX "/" DOI-SUFFIX
							</artwork>
						</figure>

		EXAMPLE: http://doi.org/10.5240/68DD-341E-03EE-4BB8-1761-Q</t>
				</list>
			</t>

			<t>Rules for Lexical Equivalence:

				<list>
					<t>Two EIDR-NSS are equivalent if and only if they are equal. EIDR-NSS are case-insensitive.</t>
				</list>
			</t>
			<t>Conformance with URN Syntax:

				<list>
					<t>As specified above, each component of NSS-EIDR, namely DOI-PREFIX and DOI-SUFFIX, is translated to conform to the URN syntax.</t>
				</list>
			</t>
			<t>Validation mechanism:

				<list>
					<t>The validity of an EIDR-NSS can only be guaranteed by completing the resolution process.</t>

					<t>For EIDR-NSS with an DOI-PREFIX equal to "10.5240", the CHECK value can be used for integrity checking, as specified above.</t>
				</list>
			</t>
			<t>Scope:

				<list>
					<t>EIDR Identifiers are centrally registered, globally unique identifiers for use with audiovisual works worldwide.</t>
				</list>
			</t>

		</section>
		<section title='Namespace Considerations'>
			<t>	

EIDR Identifiers are intended for use in Internet applications, where URNs are routinely used to identify audiovisual resources. There is no direct mapping from EIDR Identifiers to existing URN namepsaces. 

			</t>
		</section>
		<section title='Community Considerations'>
			<t>	

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. EIDR identifiers can be used by anyone to unambiguously identify an audiovisual asset and retrieve underlying metadata.  The primary benefits of its use are associated with works in wide distribution, management of long or complex distribution chains, and aggregation of information from multiple sources.

			</t>
		</section>
		<section title='IANA Considerations'>
			<t>	

This document defines a URN NID registration that is to be entered into the IANA registry of URN NIDs. It specifically requests the	"EIDR" NID.</t>
		</section>
		<section title='Security Considerations'>
			<t>This document only specifies the syntax of the EIDR-URN namespace, and is therefore security-neutral. The details assignment and resolution processes are defined external to this document by the EIDR organization and the ISO 26324 Registration Authority, and thus outside the scope of this document.</t>
		</section>
	</middle>
	<back>
		<references title='Normative References'>
			<reference anchor="RFC2141">
				<front>
					<title>URN Syntax</title>
					<author fullname="Ryan Moats" surname="Moats" initials="R.">
						<organization>AT&amp;T</organization>
						<address>
							<postal>
								<street>15621 Drexel Circle</street>
								<street>Omaha</street>
								<street>NE 68135-2358</street>
								<country>USA</country>
							</postal>
							<phone>+1 402 894-9456</phone>
							<email>jayhawk@ds.internic.net</email>
						</address>
					</author>
					<date month="May" year="1997"/>
				</front>
				<seriesInfo value="2141" name="RFC"/>
				<format target="http://www.rfc-editor.org/rfc/rfc2141.txt" octets="14077" type="TXT"/>
				<format target="http://xml.resource.org/public/rfc/xml/rfc2141.xml" octets="17687" type="XML"/>
			</reference>

			<reference anchor='RFC2234'>

				<front>
					<title abbrev='ABNF for Syntax Specifications'>Augmented BNF for Syntax Specifications: ABNF</title>
					<author initials='D.' surname='Crocker' fullname='David H. Crocker' role='editor'>
						<organization>Internet Mail Consortium</organization>
						<address>
							<postal>
								<street>675 Spruce Dr.</street>
								<city>Sunnyvale</city>
								<region>CA</region>
								<code>94086</code>
								<country>US</country>
							</postal>
							<phone>+1 408 246 8253</phone>
							<facsimile>+1 408 249 6205</facsimile>
							<email>dcrocker@imc.org</email>
						</address>
					</author>
					<author initials='P.' surname='Overell' fullname='Paul Overell'>
						<organization>Demon Internet Ltd.</organization>
						<address>
							<postal>
								<street>Dorking Business Park</street>
								<street>Dorking</street>
								<city>Surrey</city>
								<region>England</region>
								<code>RH4 1HN</code>
								<country>UK</country>
							</postal>
							<email>paulo@turnpike.com</email>
						</address>
					</author>
					<date year='1997' month='November' />
					<keyword>ABNF</keyword>
					<keyword>Augmented</keyword>
					<keyword>Backus-Naur</keyword>
					<keyword>Form</keyword>
					<keyword>electronic</keyword>
					<keyword>mail</keyword>
				</front>

				<seriesInfo name='RFC' value='2234' />
				<format type='TXT' octets='24265' target='http://www.rfc-editor.org/rfc/rfc2234.txt' />
				<format type='HTML' octets='42947' target='http://xml.resource.org/public/rfc/html/rfc2234.html' />
				<format type='XML' octets='24417' target='http://xml.resource.org/public/rfc/xml/rfc2234.xml' />
			</reference>


			<reference anchor="ISO26234">
				<front>
					<title>Information and documentation - Digital object identifier system</title>
					<author>
						<organization>International Organization for Standardization</organization>
					</author>
					<date year="2012"/>
				</front>
				<seriesInfo name="ISO" value="Standard 26324"/>
			</reference>

			<reference anchor="ISO7064">
				<front>
					<title>Information technology - Security techniques - Check character systems</title>
					<author>
						<organization>International Organization for Standardization</organization>
					</author>
					<date year="2003"/>
				</front>
				<seriesInfo name="ISO" value="Standard 7064"/>
			</reference>

			<reference anchor="SMPTERP2079">
				<front>
					<title>Digital Object Identifier (DOI) Name and Entertainment ID Registry (EIDR) Identifier Representations</title>
					<author>
						<organization>Society of Motion Picture and Television Engineers</organization>
					</author>
					<date year="2014"/>
				</front>
				<seriesInfo name="SMPTE" value="RP 2079"/>
			</reference>
		</references>
		<references title='Informative References'>

			<reference anchor='RFC3406'>

				<front>
					<title>Uniform Resource Names (URN) Namespace Definition Mechanisms</title>
					<author initials='L.' surname='Daigle' fullname='L. Daigle'>
						<organization />
					</author>
					<author initials='D.' surname='van Gulik' fullname='D. van Gulik'>
						<organization />
					</author>
					<author initials='R.' surname='Iannella' fullname='R. Iannella'>
						<organization />
					</author>
					<author initials='P.' surname='Faltstrom' fullname='P. Faltstrom'>
						<organization />
					</author>
					<date year='2002' month='October' />
					<abstract>
						<t>This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces".  The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405.  The whole rests on the concept of individual "namespaces" within the URN structure.  Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed in RFC 2288.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
					</abstract>
				</front>

				<seriesInfo name='BCP' value='66' />
				<seriesInfo name='RFC' value='3406' />
				<format type='TXT' octets='43707' target='http://www.rfc-editor.org/rfc/rfc3406.txt' />
			</reference>
<reference anchor="EIDR-OVERVIEW" target="http://eidr.org/documents/2013-11-01_EIDR_Overview_FINAL.pdf" >
				<front>
					<title>EIDR Overview</title>
					<author>
						<organization>Entertainment ID Registry</organization>
					</author>
					<date month="November" year="2013"/>
				</front>
			</reference>
			<reference anchor="EIDR-INTRO" target="http://eidr.org/documents/EIDR_ID_Format_v1.1.pdf">
				<front>
					<title>EIDR: ID Format Ver. 1.1</title>
					<author>
						<organization>Entertainment ID Registry</organization>
					</author>
					<date month="August" year="2013"/>
				</front>
			</reference>
		</references>


	</back>
</rfc>
