idnits 2.17.1 draft-pal-eidr-urn-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 28, 2014) is 3622 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 3406 (Obsoleted by RFC 8141) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Lemieux 3 Internet-Draft Sandflow Consulting LLC 4 Intended status: Informational May 28, 2014 5 Expires: November 29, 2014 7 Entertainment Identifier Registry (EIDR) URN Namespace Definition 8 draft-pal-eidr-urn-03 10 Abstract 12 Entertainment Identifier Registry (EIDR) Identifiers are used for the 13 globally unique identification of motion picture and television 14 content. This document defines the formal Uniform Resource Name 15 (URN) Namespace Identifier (NID) for EIDR Identifiers. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on November 29, 2014. 34 Copyright Notice 36 Copyright (c) 2014 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 1. Introduction 51 This document defines the formal Uniform Resource Name (URN) 52 Namespace Identifier (NID) for EIDR Identifiers. 54 EIDR Identifiers are centrally registered, globally unique 55 identifiers for audiovisual works and their variants, primarily film 56 and television. A unique set of metadata parameters describing the 57 associated work is bound to the EIDR Identifier at the time of 58 registration. 60 EIDR Identifiers are a special kind of DOI Names allocated by EIDR 61 Association specifically for audiovisual works. The Digital Object 62 Identifier (DOI) system provides an infrastructure for persistent 63 unique identification of objects of any type, and is specified in 64 [ISO26234]. A DOI name is the identifier that is permanently 65 assigned to an object. The use of DOI Names ensures persistence, 66 global uniqueness and an open resolution infrastructure. 68 As a DOI Name, an EIDR Identifier has two components: a prefix 69 assigned exclusively to EIDR Association by the DOI Registration 70 Authority and a suffix defined by EIDR Association. Currently, EIDR 71 Identifiers use the prefix "10.5240", but additional prefixes might 72 be introduced in the future. 74 The following is an example of an EIDR Identifier in its canonical 75 representation: 77 10.5240/7791-8534-2C23-9030-8610-5 79 where "10.5240" is the prefix and "7791-8534-2C23-9030-8610-5" is the 80 suffix. The canonical URN representation of the same EIDR Identifier 81 is: 83 urn:eidr:10.5240:7791-8534-2C23-9030-8610-5 85 Note that ":" is used as separator between prefix and suffix since 86 "/" is a URN reserved character. 88 [EIDR-OVERVIEW] and [EIDR-INTRO] provide additional background 89 information. 91 2. Completed URN Namespace Definition Template 93 The namespace definition according to the template in [RFC3406] is as 94 follows: 96 Namespace ID: 98 EIDR 100 Registration Information: 102 Version 1 104 2014-03-03 106 Declared registrant of the namespace: 108 Name: 110 Entertainment Identifier Registry Association 112 Address: 114 c/o Alliances Management 115 544 Hillside Road 116 Redwood City, CA 94062 117 USA 119 Contact: 121 URL: http://eidr.org/contact/ 122 E-mail: info@eidr.org 124 Declaration of syntactic structure: 126 An EIDR Identifier is a special kind of DOI Name (see [ISO26234]) 127 and, as such, consists of two components: a prefix denoted EIDR- 128 PREFIX and a suffix denoted EIDR-SUFFIX. The URN representation 129 URN-EIDR of an EIDR Identifier conforms to the syntax (expressed 130 using [RFC5234]): 132 URN-EIDR = "urn:eidr:" EIDR-NSS 133 EIDR-NSS = EIDR-PREFIX ":" EIDR-SUFFIX 134 EIDR-PREFIX = 1*EIDR-CHARS 135 EIDR-SUFFIX = 1*EIDR-CHARS 136 EIDR-CHARS = ALPHA / DIGIT / "-" / "." / "_" 138 The only value of EIDR-PREFIX currently in use is "10.5240". 139 Additional prefix values conforming to the EIDR-PREFIX syntax 140 might be introduced by EIDR Association in the future. Each of 141 these additional prefix values will in all cases be associated 142 with suffix values that conform to a subset of the EIDR-SUFFIX 143 syntax. These additional prefixes and their corresponding 144 suffixes will be documented in future revisions to this 145 registration. 147 An implementation can process an EIDR-NSS with an unknown prefix 148 as an opaque string per the Section "rules of lexical 149 equivalence", and resolve it as a generic DOI Name per the 150 Section "process for identifier resolution". 152 When EIDR-PREFIX is equal to "10.5240", the syntax of EIDR-SUFFIX 153 is further constrained according to the to RP2079-SUFFIX syntax 154 specified in [SMPTERP2079]: 156 RP2079-SUFFIX = 5(4HEXDIG "-") CHECK 157 CHECK = DIGIT / ALPHA 159 where CHECK is the Mod 37,36 check character as specified in 160 [ISO7064], computed over the 20 hexadecimal digits HEXDIG of 161 RP2079-SUFFIX. 163 EXAMPLE: urn:eidr:10.5240:7791-8534-2C23-9030-8610-5 165 Relevant ancillary documentation: 167 [ISO26234] specifies DOI Name syntax and registration. 169 [SMPTERP2079] specifies the syntax of EIDR Identifier with the 170 prefix "10.5240". 172 Identifier uniqueness considerations: 174 An EIDR Identifier is a DOI Name. The ISO 26324 Registration 175 Authority ensures that DOI Name uniqueness, therefore the URN-EIDR 176 derived from an EIDR Identifier is guaranteed unique and never 177 reassigned. 179 Furthermore, an EIDR Identifier is associated with a single URN- 180 EIDR. 182 Identifier persistence considerations: 184 An EIDR Identifier is a DOI Name. The ISO 26324 Registration 185 Authority ensures that a DOI Name remains valid indefinitely, 186 therefore the URN-EIDR derived from an EIDR Identifier remains 187 valid indefinitely. 189 Process of identifier assignment: 191 The EIDR Association registers each EIDR Identifier with the ISO 192 26324 Registration Authority. 194 Entities involved in the motion picture and television industry, 195 either directly in the production of content or in its 196 distribution and related services, are eligible to apply for 197 registrant status. Registrants pay an annual membership fee that 198 depends on the size of the company. 200 Process for identifier resolution: 202 As a DOI Name, the resolution of the EIDR Identifier associated 203 with an EIDR-NSS is handled by the ISO 26324 Registration 204 Authority. 206 The ISO 26324 Registration Authority operates a web service that 207 allows the EIDR Identifier associated with an EIDR-NSS to be 208 resolved by issuing an HTTP GET request to the following URI (see 209 [RFC2616]): 211 "http://doi.org/" EIDR-PREFIX "/" EIDR-SUFFIX 213 If the EIDR Identifier exists, then an XML Schema instance 214 document (see [XMLSchema]) containing metadata associated with the 215 EIDR Identifier is returned, otherwise the HTTP status code "404 216 Not Found" is returned. 218 EXAMPLE: http://doi.org/10.5240/7791-8534-2C23-9030-8610-5 220 NOTE: At the time of this writing, this service of the ISO 26324 221 Registration Authority is not available over TLS, and hence the 222 confidentiality of queries is not protected. 224 The EIDR Association operates additional services specifically 225 tailored to EIDR users (see [EIDR-SERVICES]). These services 226 include additional features, e.g. confidential lookup using TLS 227 and the ability to register EIDR Identifiers. 229 Rules for Lexical Equivalence: 231 Lexical equivalence of EIDR-URN is defined by case-insensitive 232 string match. 234 Conformance with URN Syntax: 236 As specified above, the syntax of EIDR-URN is a subset of the URN 237 syntax specified in [RFC2141]. 239 Validation mechanism: 241 The validity of an EIDR-NSS can only be guaranteed by completing 242 the resolution process. 244 For EIDR-NSS with an EIDR-PREFIX equal to "10.5240", the CHECK 245 value can be used for integrity checking, as specified above. 247 Scope: 249 EIDR Identifiers are centrally registered, globally unique 250 identifiers for use with audiovisual works worldwide. 252 3. Namespace Considerations 254 EIDR Identifiers are intended for use in Internet applications, where 255 URNs are routinely used to identify audiovisual resources. There is 256 no direct mapping from EIDR Identifiers to existing URN namepsaces. 258 4. Community Considerations 260 The primary registrants of EIDR Identifiers are producers and 261 distributors of audiovisual works, metadata aggregators, and 262 audiovisual archives. Any bona fide member of the ecosystem can 263 become an EIDR member and register any work. EIDR identifiers can be 264 used by anyone to unambiguously identify an audiovisual asset and 265 retrieve underlying metadata. The primary benefits of its use are 266 associated with works in wide distribution, management of long or 267 complex distribution chains, and aggregation of information from 268 multiple sources. 270 5. IANA Considerations 272 This document defines a URN NID registration that is to be entered 273 into the IANA registry of URN NIDs. It specifically requests the 274 EIDR NID. 276 6. Security Considerations 278 This document specifies the syntax of the EIDR-URN namespace and 279 makes no security representations. Furthermore, the details of 280 assignment and resolution processes are defined external to this 281 document by the EIDR Association and the ISO 26324 Registration 282 Authority, and thus outside the scope of this document. Note however 283 that failure to conform to the syntactic and lexical equivalence 284 rules specified in this specification when using an EIDR Identifier 285 as a criteria for accessing restricted resources can result in 286 granting unauthorized access to these resources. 288 7. References 290 7.1. Normative References 292 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 294 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 295 Specifications: ABNF", STD 68, RFC 5234, January 2008. 297 [ISO26234] 298 International Organization for Standardization, 299 "Information and documentation - Digital object identifier 300 system", ISO Standard 26324, 2012. 302 [ISO7064] International Organization for Standardization, 303 "Information technology - Security techniques - Check 304 character systems", ISO Standard 7064, 2003. 306 [SMPTERP2079] 307 Society of Motion Picture and Television Engineers, 308 "Digital Object Identifier (DOI) Name and Entertainment ID 309 Registry (EIDR) Identifier Representations", SMPTE RP 310 2079, 2014. 312 7.2. Informative References 314 [XMLSchema] 315 Holstege, M. and A. Vedamuthu, "W3C XML Schema Definition 316 Language (XSD): Component Designators", World Wide Web 317 Consortium CR CR-xmlschema-ref-20100119, January 2010, 318 . 320 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 321 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 322 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 324 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 325 "Uniform Resource Names (URN) Namespace Definition 326 Mechanisms", BCP 66, RFC 3406, October 2002. 328 [EIDR-OVERVIEW] 329 Entertainment Identifier Registry Association, "EIDR 330 Overview", November 2013, . 333 [EIDR-INTRO] 334 Entertainment Identifier Registry Association, "EIDR: ID 335 Format Ver. 1.1", August 2013, 336 . 338 [EIDR-SERVICES] 339 Entertainment Identifier Registry Association, "EIDR 340 System Version 2.0: Registry User's Guide", August 2013, 341 . 344 Author's Address 346 Pierre-Anthony Lemieux 347 Sandflow Consulting LLC 349 Email: pal@sandflow.com