idnits 2.17.1 draft-adid-urn-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(ii) Publication Limitation clause. If this document is intended for submission to the IESG for publication, this constitutes an error. 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 : ---------------------------------------------------------------------------- ** There are 4 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 3 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 12, 2016) is 2928 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC3406' is mentioned on line 90, but not defined ** Obsolete undefined reference: RFC 3406 (Obsoleted by RFC 8141) == Unused Reference: 'RFC2141' is defined on line 203, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 205, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force (IETF) J. Wold 2 Internet Draft Advertising Digital Identification 3 Intended status: Informational April 12, 2016 4 Expires: September 2016 6 Advertising Digital Identification (Ad-ID) URN Namespace Definition 7 draft-adid-urn-00.txt 9 Status of this Memo 11 This Internet-Draft is submitted in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 This Internet-Draft is submitted in full conformance with the 15 provisions of BCP 78 and BCP 79. This document may not be modified, 16 and derivative works of it may not be created, and it may not be 17 published except as an Internet-Draft. 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. This document may not be modified, 21 and derivative works of it may not be created, except to publish it 22 as an RFC and to translate it into languages other than English. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html 40 This Internet-Draft will expire on October 12, 2016. 42 Copyright Notice 44 Copyright (c) 2016 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. 54 Abstract 56 Advertising Digital Identification (Ad-ID) Identifiers are used 57 identifying Advertising Assets across all media platforms (over the 58 air, on-line, over the top, mobile, place based). This document 59 defines the formal Uniform Resource Name (URN) Namespace Identifier 60 (NID) for Ad-ID Identifiers. 62 Table of Contents 64 1. Introduction...................................................2 65 2. Completed URN Namespace Definition Template....................2 66 3. Community Considerations.......................................5 67 4. Security Considerations........................................6 68 5. IANA Considerations............................................6 69 6. References.....................................................6 70 6.1. Normative References......................................6 71 6.2. Informative References....................................6 73 1. Introduction 75 This document defines the formal Uniform Resource Name (URN) 76 Namespace Identifier (NID) for Ad-ID Identifiers. 78 Ad-ID is the industry standard for identifying advertising assets 79 across all media platforms. Ad-ID's data model includes the 80 registration of advertising assets using standardized descriptive 81 metadata about ads including advertiser, product, commercial title 82 and other essential data. Ad-ID Identifiers are unique codes for 83 each advertising asset digitally, and applies that code to all 84 media. 86 [Ad-ID-INTRO] provides additional background information. 88 2. Completed URN Namespace Definition Template 90 The namespace definition according to the template in [RFC3406] is 91 as follows: 93 Namespace ID: 95 adid 97 Registration Information: 99 Version 1 101 2016-03-22 103 Declared registrant of the namespace: 105 Name: 107 Advertising Digital Identification, LLC 109 Address: 111 Advertising Digital Identification, LLC 112 11020 David Taylor Drive, Suite 305 113 Charlotte, NC 28262-1103 114 USA 116 Contact: 118 URL: http://www.ad-id.org/contact 119 Email: cs@ad-id.org 121 Declaration of syntactic structure: 123 The identifier structure is as follows: 125 An Ad-ID Identifier consists of a unique eleven character string 126 or a unique twelve character string (video codes only). 128 This string is divided into three parts: 130 1. A four-character alphanumeric Company Prefix, not starting 131 with "0". 132 2. A seven-character alphanumeric code. 133 3. An optional one-character Video Format Identifier. 135 Video Format: 136 H - High Definition 137 D - Three-Dimensional 139 The URN representation URN-ADID of an Ad-ID Identifier 140 conforms to the syntax specified below using ABNF 141 (as specified in IETF RFC 5234): 143 URN-ADID = "urn:adid:" full_adid_identifier 144 full_adid_identifier = adid_prefix adid_code [adid_suffix] 145 adid_prefix = (ALPHA / %x31-39) 3*alphanum 146 ; first character not zero 147 adid_code = 7*alphanum 148 adid_suffix = "H" / "D" 149 alphanum = ALPHA / DIGIT 151 Examples: 153 Standard Definition (SD): urn:adid:ABCD0001000 154 High Definition (HD): urn:adid:ABCD0001000H 155 Three-dimensional (3D): urn:adid:ABCD00010003 157 Relevant ancillary documentation: 159 [SMPTERP2092-1] specifies Advertising Digital Identifier (Ad-ID) 160 Representations. 162 Identifier uniqueness considerations: 164 The Registrar (Advertising Digital Identification, LLC) is 165 responsible for managing the assignment of the Ad-ID Identifier and 166 shall ensure the uniqueness by checking the identifier against the 167 list of existing ids. 169 Ad-ID assigns the identifier, adid, in such a way that the 170 uniqueness of the 'adid' will be maintained. Furthermore, an Ad- 171 ID Identifier is associated with a single URN-ADID. 173 Identifier persistence considerations: 175 The assignment process guarantees that 'adids' are not reassigned 176 or reused and the binding between the id and its resource is 177 permanent. 179 primary benefits of its use are greater transparency and 180 accountability in the advertising marketplace, help eliminate costly 181 errors associated with the inconsistent use of advertising asset 182 identifiers throughout the advertising supply chain, and enable more 183 granular audience measurement across multiple platforms. 185 4. Security Considerations 187 This document specifies the syntax of the Ad-ID-URN namespace and 188 makes no security representations. Note however that failure to 189 conform to the syntactic and lexical equivalence rules specified when 190 using an Ad-ID Identifier as a criterion for accessing restricted 191 resources can result in granting unauthorized access. 193 5. IANA Considerations 195 This document defines a URN NID registration that is to be entered 196 into the IANA registry of URN NIDs. It specifically requests the 197 Ad-ID NID. 199 6. References 201 6.1. Normative References 203 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 205 [RFC2234] Crocker, D. and Overall, P.(Editors), "Augmented BNF for 206 Syntax Specifications: ABNF", RFC 2234, Internet Mail 207 Consortium and Demon Internet Ltd., November 1997. 209 [SMPTERP2092-1] Society of Motion Picture and Television Engineers, 210 "Advertising Digital Identifier (Ad-ID) Representations", 211 SMPTE RP 2092-1:2015. 213 6.2. Informative References 215 [Ad-ID-INTRO] 216 Ad-ID Identifiers are 11 characters except for High Definition (HD) 217 or Three-Dimensional (3D) codes, which have an H or D in the 12th 218 character. 220 Ad-ID may have Complimentary Definition Codes (CDC's), which are 221 matching SD, HD and/or 3D codes where only the 12th character of the 222 code varies. This only applies to Video codes. 224 Advertising Digital Identification, . 226 Authors' Addresses 228 Jarrett Wold 229 Advertising Digital Identification (Ad-ID) 230 708 3rd Ave 231 New York, NY 10017 233 Email: jwold@ad-id.org