| 1 |
<pre>Internet Engineering Task Force (IETF) J. Wold |
| 2 |
Request for Comments: 8107 Advertising Digital Identification |
| 3 |
Category: Informational March 2017 |
| 4 |
ISSN: 2070-1721 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">Advertising Digital Identifier (Ad-ID)</span> |
| 8 |
<span class="h1">URN Namespace Definition</span> |
| 9 |
|
| 10 |
Abstract |
| 11 |
|
| 12 |
Advertising Digital Identifiers (Ad-IDs) are used to identify |
| 13 |
advertising assets across all media platforms. This document defines |
| 14 |
the formal Uniform Resource Name (URN) Namespace Identifier (NID) |
| 15 |
"adid" for Ad-IDs. |
| 16 |
|
| 17 |
Status of This Memo |
| 18 |
|
| 19 |
This document is not an Internet Standards Track specification; it is |
| 20 |
published for informational purposes. |
| 21 |
|
| 22 |
This document is a product of the Internet Engineering Task Force |
| 23 |
(IETF). It represents the consensus of the IETF community. It has |
| 24 |
received public review and has been approved for publication by the |
| 25 |
Internet Engineering Steering Group (IESG). Not all documents |
| 26 |
approved by the IESG are a candidate for any level of Internet |
| 27 |
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 28 |
|
| 29 |
Information about the current status of this document, any errata, |
| 30 |
and how to provide feedback on it may be obtained at |
| 31 |
<a href="http://www.rfc-editor.org/info/rfc8107">http://www.rfc-editor.org/info/rfc8107</a>. |
| 32 |
|
| 33 |
Copyright Notice |
| 34 |
|
| 35 |
Copyright (c) 2017 IETF Trust and the persons identified as the |
| 36 |
document authors. All rights reserved. |
| 37 |
|
| 38 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 39 |
Provisions Relating to IETF Documents |
| 40 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 41 |
publication of this document. Please review these documents |
| 42 |
carefully, as they describe your rights and restrictions with respect |
| 43 |
to this document. Code Components extracted from this document must |
| 44 |
include Simplified BSD License text as described in Section 4.e of |
| 45 |
the Trust Legal Provisions and are provided without warranty as |
| 46 |
described in the Simplified BSD License. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Wold Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction...................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. URN Namespace Definition Template..............................<a href="#page-2">2</a> |
| 61 |
<a href="#section-3">3</a>. Namespace Considerations.......................................<a href="#page-5">5</a> |
| 62 |
<a href="#section-4">4</a>. Community Considerations.......................................<a href="#page-5">5</a> |
| 63 |
<a href="#section-5">5</a>. Security Considerations........................................<a href="#page-5">5</a> |
| 64 |
<a href="#section-6">6</a>. IANA Considerations............................................<a href="#page-5">5</a> |
| 65 |
<a href="#section-7">7</a>. Normative References...........................................<a href="#page-6">6</a> |
| 66 |
<a href="#appendix-A">Appendix A</a>. Additional Background Information.....................<a href="#page-7">7</a> |
| 67 |
Author's Address...................................................<a href="#page-7">7</a> |
| 68 |
|
| 69 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 70 |
|
| 71 |
This document defines the formal Uniform Resource Name (URN) |
| 72 |
Namespace Identifier (NID) for Ad-IDs. |
| 73 |
|
| 74 |
Ad-ID is the industry standard for identifying advertising assets |
| 75 |
across all media platforms (e.g., over the air, online, over the top, |
| 76 |
mobile, and place based). Ad-IDs are unique codes for each creative |
| 77 |
advertising asset. Those unique codes are applied to all media. |
| 78 |
|
| 79 |
Ad-IDs are an eleven-character ASCII string except for High |
| 80 |
Definition (HD) or Three-Dimensional (3D) codes, which have an H or D |
| 81 |
as the 12th character. |
| 82 |
|
| 83 |
Ad-ID also provides descriptive metadata about the advertisement. |
| 84 |
The metadata includes the advertiser, brand, product, commercial |
| 85 |
title, product categorization, and other essential data about the |
| 86 |
advertisement. The metadata can be retrieved using the unique code. |
| 87 |
|
| 88 |
See <a href="#appendix-A">Appendix A</a> for additional background information. |
| 89 |
|
| 90 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Namespace Definition Template</span> |
| 91 |
|
| 92 |
Using the template in [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>], the namespace definition is as |
| 93 |
follows: |
| 94 |
|
| 95 |
Namespace ID: |
| 96 |
|
| 97 |
adid |
| 98 |
|
| 99 |
Registration Information: |
| 100 |
|
| 101 |
Version 1 |
| 102 |
2016-03-22 |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Wold Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 111 |
|
| 112 |
|
| 113 |
Declared registrant of the namespace: |
| 114 |
|
| 115 |
Registering organization: |
| 116 |
Advertising Digital Identification, LLC |
| 117 |
11020 David Taylor Drive, Suite 305 |
| 118 |
Charlotte, NC 28262-1103 |
| 119 |
USA |
| 120 |
|
| 121 |
Contact: |
| 122 |
URL: <a href="http://www.ad-id.org/contact">http://www.ad-id.org/contact</a> |
| 123 |
Email: [email protected] |
| 124 |
|
| 125 |
Declaration of syntactic structure: |
| 126 |
|
| 127 |
The identifier structure is an Ad-ID that consists of a unique |
| 128 |
eleven-character string or a unique twelve-character string (video |
| 129 |
codes only). |
| 130 |
|
| 131 |
This string is divided into three parts: |
| 132 |
|
| 133 |
1. A four-character alphanumeric Company Prefix, not starting with |
| 134 |
"0" |
| 135 |
2. A seven-character alphanumeric code |
| 136 |
3. An optional one-character Video Format Identifier. |
| 137 |
H - High Definition |
| 138 |
D - Three-Dimensional |
| 139 |
|
| 140 |
The URN representation URN-ADID of an Ad-ID conforms to the |
| 141 |
following syntax (expressed using ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]): |
| 142 |
|
| 143 |
URN-ADID = "urn:adid:" full-adid-identifier |
| 144 |
full-adid-identifier = |
| 145 |
full-adid-prefix full-adid-code [full-adid-suffix] |
| 146 |
full-adid-prefix = (ALPHA / %x31-39) 3*alphanum |
| 147 |
full-adid-code = 7*alphanum |
| 148 |
full-adid-suffix = "H" / "D" |
| 149 |
alphanum = ALPHA / DIGIT |
| 150 |
|
| 151 |
Examples: |
| 152 |
|
| 153 |
Standard Definition: urn:adid:ABCD0001000 |
| 154 |
High Definition: urn:adid:ABCD0001000H |
| 155 |
|
| 156 |
Relevant ancillary documentation: |
| 157 |
|
| 158 |
[<a id="ref-SMPTERP2092-1">SMPTERP2092-1</a>] specifies Advertising Digital Identifier (Ad-ID) |
| 159 |
representations. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Wold Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 167 |
|
| 168 |
|
| 169 |
Identifier uniqueness considerations: |
| 170 |
|
| 171 |
The Registrar (Advertising Digital Identification, LLC) is |
| 172 |
responsible for managing the assignment of the Ad-ID and shall |
| 173 |
ensure its uniqueness by checking the identifier against the list |
| 174 |
of existing identifiers. In addition, each Ad-ID is associated |
| 175 |
with a its own unique URN-ADID. |
| 176 |
|
| 177 |
Ad-ID Registrar has assigned "adid" as a unique identifier. It is |
| 178 |
associated with a single URN-ADID. |
| 179 |
|
| 180 |
Identifier persistence considerations: |
| 181 |
|
| 182 |
The assignment process guarantees that 'adids' will not be |
| 183 |
reassigned or reused, and the binding between the identifier and |
| 184 |
its resource is permanent. |
| 185 |
|
| 186 |
These rules apply to this URN namespace. |
| 187 |
|
| 188 |
Process of identifier assignment: |
| 189 |
|
| 190 |
Ad-IDs are generated by the Ad-ID's proprietary registration |
| 191 |
procedures. |
| 192 |
|
| 193 |
Process for identifier resolution: |
| 194 |
|
| 195 |
Ad-ID URNs are resolved via URN resolvers that are maintained by |
| 196 |
the Ad-ID. |
| 197 |
|
| 198 |
Rules for Lexical Equivalence: |
| 199 |
|
| 200 |
Lexical equivalence of URN-ADID is defined by case-insensitive |
| 201 |
string match. |
| 202 |
|
| 203 |
Conformance with URN Syntax: |
| 204 |
|
| 205 |
As specified above, the syntax of URN-ADID is a subset of the URN |
| 206 |
syntax specified in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]. |
| 207 |
|
| 208 |
Validation mechanism: |
| 209 |
|
| 210 |
The validity of a URN-ADID can be checked using Ad-ID's web |
| 211 |
services. For more information on Ad-ID's web services, please |
| 212 |
refer to the following links: |
| 213 |
|
| 214 |
<a href="http://www.ad-id.org/user-support/faqs/faq-category/web-services">http://www.ad-id.org/user-support/faqs/faq-category/web-services</a> |
| 215 |
<a href="http://www.ad-id.org/ad-id-web-services-api-guide">http://www.ad-id.org/ad-id-web-services-api-guide</a> |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Wold Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 223 |
|
| 224 |
|
| 225 |
Scope: |
| 226 |
|
| 227 |
Ad-IDs are centrally registered, globally unique identifiers of |
| 228 |
advertising assets that are used worldwide. |
| 229 |
|
| 230 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Namespace Considerations</span> |
| 231 |
|
| 232 |
Ad-IDs are intended for use in Internet applications, where URNs are |
| 233 |
routinely used to identify audiovisual resources. There is no direct |
| 234 |
mapping from Ad-IDs to existing URN namespaces. |
| 235 |
|
| 236 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Community Considerations</span> |
| 237 |
|
| 238 |
The primary registrants of Ad-IDs are advertisers and agencies. Ad- |
| 239 |
IDs can be used by anyone to unambiguously identify advertising |
| 240 |
assets and retrieve underlying metadata. The primary benefits of its |
| 241 |
use are providing greater transparency and accountability in the |
| 242 |
advertising marketplace, helping to eliminate costly errors |
| 243 |
associated with the inconsistent use of advertising-asset identifiers |
| 244 |
throughout the advertising supply chain, and enabling a more granular |
| 245 |
audience measurement across multiple platforms. |
| 246 |
|
| 247 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 248 |
|
| 249 |
This document specifies the syntax of the Ad-ID URN namespace and |
| 250 |
makes no security representations. However, note that failure to |
| 251 |
conform to the syntactic and lexical equivalence rules specified in |
| 252 |
[<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>] when using an Ad-ID as a criterion for accessing restricted |
| 253 |
resources can result in granting unauthorized access. |
| 254 |
|
| 255 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 256 |
|
| 257 |
This document defines "ad-id" in the "Formal URN Namespaces" |
| 258 |
registry. |
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Wold Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span> |
| 282 |
|
| 283 |
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141, |
| 284 |
May 1997, <<a href="http://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>. |
| 285 |
|
| 286 |
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, |
| 287 |
"Uniform Resource Names (URN) Namespace Definition |
| 288 |
Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, DOI 10.17487/RFC3406, |
| 289 |
October 2002, <<a href="http://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>. |
| 290 |
|
| 291 |
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for |
| 292 |
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, DOI |
| 293 |
10.17487/RFC5234, January 2008, |
| 294 |
<<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>>. |
| 295 |
|
| 296 |
[<a id="ref-SMPTERP2092-1">SMPTERP2092-1</a>] |
| 297 |
Society of Motion Picture and Television Engineers, |
| 298 |
"Advertising Digital Identifier (Ad-ID) Representations", |
| 299 |
SMPTE RP 2092-1, April 2015. |
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Wold Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8107">RFC 8107</a> Ad-ID URN Namespace Definition March 2017</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Additional Background Information</span> |
| 338 |
|
| 339 |
Ad-IDs are an eleven-character ASCII string except for High |
| 340 |
Definition (HD) or Three-Dimensional (3D) codes, which have an H or D |
| 341 |
as the 12th character. |
| 342 |
|
| 343 |
Ad-ID may have Complimentary Definition Codes (CDCs), which are |
| 344 |
matching SD, HD, and/or 3D codes where only the 12th character of the |
| 345 |
code varies. This only applies to video codes. |
| 346 |
|
| 347 |
For example, a video with a standard format and high-definition |
| 348 |
format would have a single code for each format. |
| 349 |
|
| 350 |
Standard: ABCD1234000 |
| 351 |
High Definition: ABCD1234000H |
| 352 |
|
| 353 |
More information: <a href="http://www.ad-id.org/how-it-works/ad-id-structure">http://www.ad-id.org/how-it-works/ad-id-structure</a> |
| 354 |
|
| 355 |
Advertising Digital Identification <<a href="http://www.ad-id.org/">http://www.ad-id.org/</a>> |
| 356 |
|
| 357 |
Author's Address |
| 358 |
|
| 359 |
Jarrett Wold |
| 360 |
Advertising Digital Identification (Ad-ID) |
| 361 |
708 Third Avenue |
| 362 |
New York, NY 10017 |
| 363 |
|
| 364 |
Email: [email protected] |
| 365 |
|
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Wold Informational [Page 7] |
| 389 |
</pre> |