Internet-Draft M. Roberts Intended status: Informational Clearcast Expires: 14 October 2020 14 April 2020 Clearcast Identifier URN Namespace definition draft-clearcast-edu-clearcasturn-00 Abstract Clearcast Clock Identifiers are used for the unique identification of television advertisement content. This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) for Clearcast Identifiers. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 14 October 2020. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Introduction This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) for Clearcast Identifiers. Clearcast identifiers are centrally registered, globally unique identifiers for video advertising works and their variants. A unique set of metadata parameters describing the associated work is bound to the Clearcast identifier at the time of registration. Clearcast identifiers are a file identifier name (Clock ID) allocated by Clearcast for advertising standards. The following are examples of Clearcast Identifiers for both short and long form clock IDs in their canonical representation: QQQ/AAAA123/030 (short form) QQQ/AAAA12/1800 (long form) The canonical URN representation of the short Clearcast Identifier is: urn:clearcast:QQQ_AAAA123_030 Note that "_" is used as separator within the Clearcast Identifier since "/" is a URN reserved character. [CLEARCAST-CLOCK] and [CLEARCAST-CLEARANCE] will provide additional background information for Clock ID. 2. Completed URN Namespace Definition Template Declaration of syntactic structure: A Clearcast Identifier is a special kind of ID consisting of four components: Agency Code Product, client or Agency Internal Agency Number Duration URN-Clearcast = "urn:clearcast:" Clearcast-NSS = CLOCK ID Clearcast-AGENCY CODE = QQQ Clearcast-PRODUCT, CLIENT OR AGENCY = AAAA Clearcast-DURATION = 030 OR 1800 Clearcast-CHARS = DIGIT*3/ALPHA*4DIGIT*3/DIGIT*3 OR Clearcast-CHARS = DIGIT*3/ALPHA*4DIGIT*2/DIGIT*4 Clearcast operates a web service that requires authentication and allows the Clearcast Identifier associated to be resolved by issuing an HTTP GET request to the following URI (see[RFC7231]): EXAMPLE: "http://id.Clearcast.co.uk/" If the Clearcast Identifier exists, then an XML Schema instance document (see [XMLSchema]) containing metadata associated with the Clearcast Identifier is returned; otherwise, the HTTP status code "404 Not Found" is returned. EXAMPLE: "http://id.Clearcast.co.uk/QQQ_AAAA123_030" NOTE: At the time of this writing, this service of the ISO 26324 Registration Authority is not available over TLS, and hence the confidentiality of queries is not protected. Clearcast operates additional services specifically tailored to Clearcast users (see [Clearcast Services]). These services include additional features e.g., Copy clearance, subtitling and flash testing. Rules for Lexical Equivalence: Lexical equivalence of clearcast-URN is defined by case-insensitive string match. Conformance with URN Syntax: As specified above, the syntax of Clearcast-URN is a subset of the URN syntax specified in [RFC8141]. Validation mechanism: The validity of a clearcast-NSS can only be guaranteed by completing the resolution process. Scope: Clearcast Identifiers are registered using Copy Central, globally unique identifiers for use with advertising worldwide. 3. Namespace Considerations Clearcast Identifiers are intended for use in Internet applications, where URNs are routinely used to identify television advertising content. There is no direct mapping from Clearcast Identifiers to existing URN namespaces. 4. Community Considerations The primary registrants of Clearcast Identifiers are Advertising Agencies, Brands, Media Agencies, Post Production and Production companies, metadata aggregators and media companies. Clearcast Identifiers can be used by anyone to unambiguously identify an advertising asset and retrieve underlying metadata or connect directly to an API. The primary benefits of their use are for the Advertising Industry to identify information, metadata and connect with API?s. This can be in the form of TV, Online, and other forms of advertising distribution chains and sources. 5. IANA Considerations IANA has registered the Formal URN Namespace 'clearcast' in the "Uniform Resource Names (URN) Namespaces" registry, using the registration template in Section 2 of this document. 6. Security Considerations This document specifies the syntax of the Clearcast-URN namespace which is implemented via an authenticated API and makes no security representations. Furthermore, the details of assignment and resolution processes are defined external to this document by Clearcast and thus are outside the scope of this document. Note, however, that once authenticated, failure to conform to the criteria for accessing restricted resources can result in gaining unauthorized access to these resources. 7. References 7.1. Normative References [RFC8141] Moats, R., "URN Syntax", RFC8141, May 1997. 8. 8.1. Informative References [CLEARCAST-CLOCK] Clearcast Knowledge Base, ?Ad Clock Numbers? https://kb.clearcast.co.uk/wiki/32/what-is-a-clock-number [CLEARCAST-CLEARANCE] Clearcast Knowledge Base, ?Ad Clearance Process? https://kb.clearcast.co.uk/wiki/23/clearance-process [RFC8141] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 8141, October 2002. [RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, June 2014. [XMLSchema] Holstege, M. and A. Vedamuthu, "W3C XML Schema Definition Language (XSD): Component Designators", W3C Candidate Recommendation CR-xmlschema-ref-20100119, January 2010, . Author's Address Martin Roberts Clearcast Email: martin.roberts@Clearcast.co.uk Expiration Date: October 2020