idnits 2.17.1 draft-pal-eidr-urn-2016-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC7302, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 2, 2016) is 2824 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 2818 (Obsoleted by RFC 9110) -- Obsolete informational reference (is this intentional?): RFC 3406 (Obsoleted by RFC 8141) -- Obsolete informational reference (is this intentional?): RFC 7231 (Obsoleted by RFC 9110) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 5 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 Obsoletes: 7302 (if approved) August 2, 2016 5 Intended status: Informational 6 Expires: February 3, 2017 8 Entertainment Identifier Registry (EIDR) URN Namespace Definition 9 draft-pal-eidr-urn-2016-03 11 Abstract 13 Entertainment Identifier Registry (EIDR) Identifiers are used for the 14 globally unique identification of motion picture and television 15 content. This document defines the formal Uniform Resource Name 16 (URN) Namespace Identifier (NID) for EIDR Identifiers. 18 This document obsoletes Request For Comments (RFC) 7302 -- see 19 Appendix A for a summary of changes. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on February 3, 2017. 38 Copyright Notice 40 Copyright (c) 2016 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 This document defines the formal Uniform Resource Name (URN) 56 Namespace Identifier (NID) for EIDR Identifiers. 58 EIDR Identifiers are centrally registered, globally unique 59 identifiers for audiovisual works and their variants, primarily film 60 and television. A unique set of metadata parameters describing the 61 associated work is bound to the EIDR Identifier at the time of 62 registration. 64 EIDR Identifiers are a special kind of DOI Names allocated by EIDR 65 Association specifically for audiovisual works. The Digital Object 66 Identifier (DOI) system provides an infrastructure for persistent 67 unique identification of objects of any type and is specified in 68 [ISO26234]. A DOI name is the identifier that is permanently 69 assigned to an object. The use of DOI Names ensures persistence, 70 global uniqueness, and an open resolution infrastructure. 72 As a DOI Name, an EIDR Identifier has two components: a prefix 73 assigned exclusively to EIDR Association by the DOI Registration 74 Authority and a suffix defined by EIDR Association. Currently, EIDR 75 Identifiers use the prefix "10.5240", but additional prefixes might 76 be introduced in the future. 78 The following is an example of an EIDR Identifier in its canonical 79 representation: 81 10.5240/7791-8534-2C23-9030-8610-5 83 where "10.5240" is the prefix and "7791-8534-2C23-9030-8610-5" is the 84 suffix. The canonical URN representation of the same EIDR Identifier 85 is: 87 urn:eidr:10.5240:7791-8534-2C23-9030-8610-5 89 Note that ":" is used as separator between prefix and suffix since 90 "/" is a URN reserved character. 92 [EIDR-OVERVIEW] and [EIDR-INTRO] provide additional background 93 information. 95 2. Completed URN Namespace Definition Template 97 The namespace definition according to the template in [RFC3406] is as 98 follows: 100 Namespace ID: 102 eidr 104 Registration Information: 106 Version 1 108 2014-03-03 110 Declared registrant of the namespace: 112 Name: 114 Entertainment Identifier Registry Association 116 Address: 118 c/o Alliances Management 119 544 Hillside Road 120 Redwood City, CA 94062 121 USA 123 Contact: 125 URL: http://eidr.org/contact/ 126 Email: info@eidr.org 128 Declaration of syntactic structure: 130 An EIDR Identifier is a special kind of DOI Name (see [ISO26234]) 131 and, as such, consists of two components: a prefix denoted EIDR- 132 PREFIX and a suffix denoted EIDR-SUFFIX. The URN representation 133 URN-EIDR of an EIDR Identifier conforms to the syntax (expressed 134 using [RFC5234]): 136 URN-EIDR = "urn:eidr:" EIDR-NSS 137 EIDR-NSS = EIDR-PREFIX ":" EIDR-SUFFIX 138 EIDR-PREFIX = 1*EIDR-CHARS 139 EIDR-SUFFIX = 1*EIDR-CHARS 140 EIDR-CHARS = ALPHA / DIGIT / "-" / "." / "_" 142 The only value of EIDR-PREFIX currently in use is "10.5240". 143 Additional prefix values conforming to the EIDR-PREFIX syntax 144 might be introduced by EIDR Association in the future. In all 145 cases, each of these additional prefix values will be associated 146 with suffix values that conform to a subset of the EIDR-SUFFIX 147 syntax. These additional prefixes and their corresponding 148 suffixes will be documented in future revisions to this 149 registration. 151 An implementation can process an EIDR-NSS with an unknown prefix 152 as an opaque string per the "Rules of Lexical Equivalence" below, 153 and resolve it as a generic DOI Name per the "Process for 154 identifier resolution" below. 156 When EIDR-PREFIX is equal to "10.5240", the syntax of EIDR-SUFFIX 157 is further constrained according to the to RP2079-SUFFIX syntax 158 specified in [SMPTERP2079]: 160 RP2079-SUFFIX = 5(4HEXDIG "-") CHECK 161 CHECK = DIGIT / ALPHA 163 where CHECK is the Mod 37,36 check character as specified in 164 [ISO7064], computed over the 20 hexadecimal digits HEXDIG of 165 RP2079-SUFFIX. 167 EXAMPLE: urn:eidr:10.5240:7791-8534-2C23-9030-8610-5 169 Relevant ancillary documentation: 171 [ISO26234] specifies DOI Name syntax and registration. 173 [SMPTERP2079] specifies the syntax of the EIDR Identifier with the 174 prefix "10.5240". 176 Identifier uniqueness considerations: 178 An EIDR Identifier is a DOI Name. The ISO 26324 Registration 179 Authority ensures that DOI Name uniqueness; therefore, the 180 URN-EIDR derived from an EIDR Identifier is guaranteed to be 181 unique and never reassigned. 183 Furthermore, an EIDR Identifier is associated with a single 184 URN-EIDR. 186 Identifier persistence considerations: 188 An EIDR Identifier is a DOI Name. The ISO 26324 Registration 189 Authority ensures that a DOI Name remains valid indefinitely; 190 therefore, the URN-EIDR derived from an EIDR Identifier remains 191 valid indefinitely. 193 Process of identifier assignment: 195 EIDR Association registers each EIDR Identifier with the ISO 26324 196 Registration Authority. 198 Entities involved in the motion picture and television industry, 199 either directly in the production of content or in its 200 distribution and related services, are eligible to apply for 201 registrant status. Registrants pay an annual membership fee that 202 depends on the size of the company. 204 Process for identifier resolution: 206 As a DOI Name, the resolution of the EIDR Identifier associated 207 with an EIDR-NSS is handled by the ISO 26324 Registration 208 Authority. 210 The ISO 26324 Registration Authority operates a web service that 211 allows the EIDR Identifier associated with an EIDR-NSS to be 212 resolved by issuing an HTTP GET request to the following URI (see 213 [RFC7231] and [RFC2818]): 215 "https://doi.org/" URN-EIDR 217 If the EIDR Identifier exists, then an XML Schema instance 218 document (see [XMLSchema]) containing metadata associated with the 219 EIDR Identifier is returned; otherwise, the HTTP status code "404 220 Not Found" is returned. 222 EXAMPLE: https://doi.org/ 223 urn:eidr:10.5240:7791-8534-2C23-9030-8610-5 225 NOTE: The web service uses the HTTP Accept header to determine the 226 format of the response. When using a web browser to access the 227 resource above, the query string "?locatt=type:Full" is appended 228 to the URI to explicitly request an XML response. 230 EIDR Association operates additional services specifically 231 tailored to EIDR users (see [EIDR-SERVICES] and [DOI-EIDR-PROXY]). 232 These services include additional features, e.g. the ability to 233 register EIDR Identifiers and web-based GUI tools. 235 Rules for Lexical Equivalence: 237 Lexical equivalence of URN-EIDR is defined by case-insensitive 238 string match. 240 NOTE: URN-EIDR includes the "urn:eidr:" string, as specified under 241 "Declaration of syntactic structure". 243 Conformance with URN Syntax: 245 As specified above, the syntax of URN-EIDR is a subset of the URN 246 syntax specified in [RFC2141]. 248 Validation mechanism: 250 The validity of an EIDR-NSS can only be guaranteed by completing 251 the resolution process. 253 For EIDR-NSS with an EIDR-PREFIX equal to "10.5240", the CHECK 254 value can be used for integrity checking, as specified above. 256 Scope: 258 EIDR Identifiers are centrally registered, globally unique 259 identifiers for use with audiovisual works worldwide. 261 3. Namespace Considerations 263 EIDR Identifiers are intended for use in Internet applications, where 264 URNs are routinely used to identify audiovisual resources. There is 265 no direct mapping from EIDR Identifiers to existing URN namespaces. 267 4. Community Considerations 269 The primary registrants of EIDR Identifiers are producers and 270 distributors of audiovisual works, metadata aggregators, and 271 audiovisual archives. Any bona fide member of the ecosystem can 272 become an EIDR member and register any work. EIDR Identifiers can be 273 used by anyone to unambiguously identify an audiovisual asset and 274 retrieve underlying metadata. The primary benefits of their use are 275 associated with works in wide distribution, management of long or 276 complex distribution chains, and aggregation of information from 277 multiple sources. 279 5. IANA Considerations 281 IANA has registered the Formal URN Namespace 'eidr' in the "Uniform 282 Resource Names (URN) Namespaces" registry, using the registration 283 template in Section 2 of this document. 285 6. Security Considerations 287 This document specifies the syntax of the URN-EIDR namespace and 288 makes no security representations. Furthermore, the details of 289 assignment and resolution processes are defined external to this 290 document by EIDR Association and the ISO 26324 Registration 291 Authority, and thus are outside the scope of this document. Note, 292 however, that failure to conform to the syntactic and lexical 293 equivalence rules in this specification when using an EIDR Identifier 294 as a criteria for accessing restricted resources can result in 295 granting unauthorized access to these resources. 297 7. References 299 7.1. Normative References 301 [ISO26234] 302 International Organization for Standardization, 303 "Information and documentation - Digital object identifier 304 system", ISO Standard 26324, 2012. 306 [ISO7064] International Organization for Standardization, 307 "Information technology - Security techniques - Check 308 character systems", ISO Standard 7064, 2003. 310 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 311 May 1997, . 313 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 314 Specifications: ABNF", STD 68, RFC 5234, 315 DOI 10.17487/RFC5234, January 2008, 316 . 318 [SMPTERP2079] 319 Society of Motion Picture and Television Engineers, 320 "Digital Object Identifier (DOI) Name and Entertainment ID 321 Registry (EIDR) Identifier Representations", SMPTE RP 322 2079, 2014. 324 7.2. Informative References 326 [EIDR-INTRO] 327 Entertainment Identifier Registry Association, "EIDR: ID 328 Format Ver. 1.1", August 2013, 329 . 331 [EIDR-OVERVIEW] 332 Entertainment Identifier Registry Association, "EIDR 333 Overview", November 2013, . 336 [EIDR-SERVICES] 337 Entertainment Identifier Registry Association, "EIDR 338 System Version 2.0: Registry User's Guide", August 2013, 339 . 342 [DOI-EIDR-PROXY] 343 Entertainment Identifier Registry Association, "EIDR and 344 the DOI Proxy", May 2015, 345 . 347 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 348 DOI 10.17487/RFC2818, May 2000, 349 . 351 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 352 "Uniform Resource Names (URN) Namespace Definition 353 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, 354 October 2002, . 356 [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer 357 Protocol (HTTP/1.1): Semantics and Content", RFC 7231, 358 DOI 10.17487/RFC7231, June 2014, 359 . 361 [XMLSchema] 362 Holstege, M. and A. Vedamuthu, "W3C XML Schema Definition 363 Language (XSD): Component Designators", W3C Candidate 364 Recommendation CR-xmlschema-ref-20100119, January 2010, 365 . 367 [rfcdiff] "Rfcdiff Tool", . 369 Appendix A. Summary of changes (informative) 371 A.1. Introduction 373 This Appendix summarizes changes across revisions of this 374 specification. This summary is informative and not intended to be 375 exhaustive. Readers seeking a definitive list of changes are instead 376 encouraged to use tools such as [rfcdiff]. 378 A.2. Changes from RFC 7302 380 o "Process for identifier resolution" paragraph. The syntax for the 381 URI supplied to the web service is modified to use (a) the 'https' 382 scheme and (b) the URN-EIDR representation of the EIDR Identifier. 384 Author's Address 386 Pierre-Anthony Lemieux 387 Sandflow Consulting LLC 389 Email: pal@sandflow.com