Internet Engineering Task Force (IETF) Category: Informational March 2017 ISSN:

Similar documents
Internet Engineering Task Force (IETF) Obsoletes: 7302 September 2016 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8069 Category: Informational February 2017 ISSN:

Internet Engineering Task Force (IETF) Category: Informational March 2016 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6061 Category: Informational January 2011 ISSN:

Internet Engineering Task Force (IETF) BCP: 183 May 2013 Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Category: Informational. June A Uniform Resource Name (URN) Namespace for CableLabs

Network Working Group. Category: Informational October 2005

Internet Engineering Task Force (IETF) Category: Informational April 2012 ISSN:

National Computerization Agency Category: Informational July 2004

Internet Engineering Task Force (IETF) Request for Comments: 6694 August 2012 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8464 September 2018 Category: Informational ISSN:

Internet Engineering Task Force (IETF) October This document establishes an IETF URN Sub-namespace for use with OAuth-related specifications.

Clarifications for When to Use the name-addr Production in SIP Messages

Network Working Group Request for Comments: 3937 Category: Informational October 2004

Network Working Group. Category: Informational April A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)

Internet Engineering Task Force (IETF) Request for Comments: 8440 Category: Standards Track ISSN: August 2018

Internet Engineering Task Force (IETF) Updates: 5451 March 2012 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8142 Category: Standards Track April 2017 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track January 2019 ISSN:

Network Working Group Request for Comments: 3085 Category: Informational IPTC D. Rivers-Moore Rivcom March 2001

Ad-ID Format. Ad-ID Format. April 1, Version 1.0. Page 1

Internet Engineering Task Force (IETF) Category: Informational. May IEEE Information Element for the IETF

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track. Cisco May 2012

Internet Engineering Task Force (IETF) Updates: 5322 March 2013 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: ISSN: November 2013

Internet Engineering Task Force (IETF) Category: Standards Track September 2018 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7725 Category: Standards Track February 2016 ISSN:

P. Saint-Andre, Ed. Obsoletes: 2141 (if approved) Intended status: Standards Track July 12, 2013 Expires: January 13, 2014

Internet Engineering Task Force (IETF) BroadSoft August Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261

EPFL S. Willmott UPC September 2003

Internet Engineering Task Force (IETF) Request for Comments: 8055 Category: Standards Track. January 2017

Internet Engineering Task Force (IETF) Category: Standards Track. M. Nottingham, Ed. Akamai April 2013

Request for Comments: 7254 Category: Informational. Eircom P. Gosden GSM Association May 2014

Internet Engineering Task Force (IETF) Request for Comments: 6711 Category: Informational August 2012 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: Q. Wu, Ed. R. Huang Huawei November 2014

Internet Engineering Task Force (IETF) Request for Comments: ISSN: March 2017

Internet Engineering Task Force (IETF) Request for Comments: ISSN: Y. Umaoka IBM December 2010

Internet Engineering Task Force (IETF) Category: Standards Track. Cisco Systems, Inc. J. Scudder Juniper Networks September 2016

Internet Engineering Task Force (IETF) Request for Comments: 8437 Updates: 3501 August 2018 Category: Standards Track ISSN:

Prefer Header for HTTP

Internet Engineering Task Force (IETF) Category: Standards Track. Enterprise Architects February 2012

Internet Engineering Task Force (IETF) Request for Comments: 5987 Category: Standards Track August 2010 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8035 Updates: 5761 November 2016 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7660 Category: Standards Track. October 2015

Internet Engineering Task Force (IETF) Category: Standards Track. March 2017

Internet Engineering Task Force (IETF) Request for Comments: 5736 Category: Informational. ICANN January 2010

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track ISSN: September 2015

Internet Engineering Task Force (IETF) Category: Standards Track. M. Petit-Huguenin Impedance Mismatch November 2013

Internet Engineering Task Force (IETF) Category: Standards Track March 2011 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track. J. Halpern Ericsson E. Levy-Abegnoli, Ed. Cisco February 2017

Request for Comments: 7259 Category: Informational May 2014 ISSN:

Internet Engineering Task Force (IETF) Juniper Networks K. Watsen Watsen Networks R. Wilton Cisco Systems March 2019

Internet Engineering Task Force (IETF) Category: Standards Track April 2013 ISSN: Formally Deprecating Some ICMPv4 Message Types

Request for Comments: 7912 Category: Informational June 2016 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7237 Category: Informational June 2014 ISSN:

Internet Engineering Task Force (IETF) Cisco Systems, Inc. April 2015

Internet Engineering Task Force (IETF) Request for Comments: 6522 STD: 73 January 2012 Obsoletes: 3462 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Updates: 6376 January 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Obsoletes: 2831 July 2011 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: AT&T Laboratories. Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8050 Category: Standards Track ISSN: May 2017

Internet Engineering Task Force (IETF) Request for Comments: Category: Standards Track May 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 8186 Category: Standards Track. June 2017

Internet Engineering Task Force (IETF) Request for Comments: 7319 BCP: 191 July 2014 Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7504 June 2015 Updates: 1846, 5321 Category: Standards Track ISSN:

Network Working Group Request for Comments: 5138 Category: Informational February 2008

Internet Engineering Task Force (IETF) Obsoletes: 6485 Category: Standards Track August 2016 ISSN:

Internet Engineering Task Force (IETF) Category: Informational. August IANA Registration for the Cryptographic Algorithm Object Identifier Range

Internet Engineering Task Force (IETF) Category: Standards Track March 2015 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6379 Obsoletes: 4869 Category: Informational October 2011 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 7973 Category: Informational ISSN: November 2016

Internet Engineering Task Force (IETF) Request for Comments: 6441 BCP: 171 November 2011 Category: Best Current Practice ISSN:

Internet Engineering Task Force (IETF) Request for Comments: ISSN: October 2011

Internet Engineering Task Force (IETF) P. Jones Cisco Systems November Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

Internet Engineering Task Force (IETF) Request for Comments: 5917 Category: Informational June 2010 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: November 2015

Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status.

Internet Engineering Task Force (IETF) Request for Comments: 8508 Category: Standards Track January 2019 ISSN:

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: January 2011

DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes

Internet Engineering Task Force (IETF) Updates: 5280 May 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Huawei Technologies Co., Ltd.

Internet Engineering Task Force (IETF) Request for Comments: Obsoletes: 1652 Category: Standards Track

Request for Comments: February 2006

Internet Engineering Task Force (IETF) Request for Comments: 8262 Updates: 5368, 5621, 6442 Category: Standards Track October 2017 ISSN:

Internet Engineering Task Force (IETF) April 2012

Internet Engineering Task Force (IETF) Request for Comments: ISSN: March 2016

Internet Engineering Task Force (IETF) May 2011

Internet Engineering Task Force (IETF) Category: Standards Track October 2014 ISSN:

Request for Comments: 3405 BCP: 65 October 2002 Category: Best Current Practice

Internet Engineering Task Force (IETF) Request for Comments: ISSN: January 2013

Internet Engineering Task Force (IETF) Category: Informational ISSN: February 2012

Internet Engineering Task Force (IETF) Request for Comments: 7537 Updates: 4379, L. Andersson S. Aldrin Huawei Technologies May 2015

Internet Engineering Task Force (IETF) Request for Comments: Category: Best Current Practice ISSN: March 2017

Network Working Group. R. Iannella DSTC Pty Ltd P. Faltstrom Tele2/Swipnet June 1999

Internet Engineering Task Force (IETF) Request for Comments: 8465 September 2018 Category: Informational ISSN:

Internet Engineering Task Force (IETF) Request for Comments: Category: Informational. R. White. D. McPherson Verisign, Inc.

Internet Engineering Task Force (IETF) Request for Comments: August 2011

Internet Engineering Task Force (IETF) Request for Comments: 6470 Category: Standards Track February 2012 ISSN:

Internet Engineering Task Force (IETF) Updates: 5614 October 2013 Category: Experimental ISSN:

Transcription:

Internet Engineering Task Force (IETF) J. Wold Request for Comments: 8107 Advertising Digital Identification Category: Informational March 2017 ISSN: 2070-1721 Abstract Advertising Digital Identifier (Ad-ID) URN Namespace Definition Advertising Digital Identifiers (Ad-IDs) are used to identify advertising assets across all media platforms. This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) "adid" for Ad-IDs. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8107. Copyright Notice Copyright (c) 2017 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 (http://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. Wold Informational [Page 1]

Table of Contents 1. Introduction...2 2. URN Namespace Definition Template...2 3. Namespace Considerations...5 4. Community Considerations...5 5. Security Considerations...5 6. IANA Considerations...5 7. Normative References...6 Appendix A. Additional Background Information...7 Author s Address...7 1. Introduction This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) for Ad-IDs. Ad-ID is the industry standard for identifying advertising assets across all media platforms (e.g., over the air, online, over the top, mobile, and place based). Ad-IDs are unique codes for each creative advertising asset. Those unique codes are applied to all media. Ad-IDs are an eleven-character ASCII string except for High Definition (HD) or Three-Dimensional (3D) codes, which have an H or D as the 12th character. Ad-ID also provides descriptive metadata about the advertisement. The metadata includes the advertiser, brand, product, commercial title, product categorization, and other essential data about the advertisement. The metadata can be retrieved using the unique code. See Appendix A for additional background information. 2. URN Namespace Definition Template Using the template in [RFC3406], the namespace definition is as follows: Namespace ID: adid Registration Information: Version 1 2016-03-22 Wold Informational [Page 2]

Declared registrant of the namespace: Registering organization: Advertising Digital Identification, LLC 11020 David Taylor Drive, Suite 305 Charlotte, NC 28262-1103 USA Contact: URL: http://www.ad-id.org/contact Email: cs@ad-id.org Declaration of syntactic structure: The identifier structure is an Ad-ID that consists of a unique eleven-character string or a unique twelve-character string (video codes only). This string is divided into three parts: 1. A four-character alphanumeric Company Prefix, not starting with "0" 2. A seven-character alphanumeric code 3. An optional one-character Video Format Identifier. H - High Definition D - Three-Dimensional The URN representation URN-ADID of an Ad-ID conforms to the following syntax (expressed using ABNF [RFC5234]): URN-ADID = "urn:adid:" full-adid-identifier full-adid-identifier = full-adid-prefix full-adid-code [full-adid-suffix] full-adid-prefix = (ALPHA / %x31-39) 3*alphanum full-adid-code = 7*alphanum full-adid-suffix = "H" / "D" alphanum = ALPHA / DIGIT Examples: Standard Definition: urn:adid:abcd0001000 High Definition: urn:adid:abcd0001000h Relevant ancillary documentation: [SMPTERP2092-1] specifies Advertising Digital Identifier (Ad-ID) representations. Wold Informational [Page 3]

Identifier uniqueness considerations: The Registrar (Advertising Digital Identification, LLC) is responsible for managing the assignment of the Ad-ID and shall ensure its uniqueness by checking the identifier against the list of existing identifiers. In addition, each Ad-ID is associated with a its own unique URN-ADID. Ad-ID Registrar has assigned "adid" as a unique identifier. It is associated with a single URN-ADID. Identifier persistence considerations: The assignment process guarantees that adids will not be reassigned or reused, and the binding between the identifier and its resource is permanent. These rules apply to this URN namespace. Process of identifier assignment: Ad-IDs are generated by the Ad-ID s proprietary registration procedures. Process for identifier resolution: Ad-ID URNs are resolved via URN resolvers that are maintained by the Ad-ID. Rules for Lexical Equivalence: Lexical equivalence of URN-ADID is defined by case-insensitive string match. Conformance with URN Syntax: As specified above, the syntax of URN-ADID is a subset of the URN syntax specified in [RFC2141]. Validation mechanism: The validity of a URN-ADID can be checked using Ad-ID s web services. For more information on Ad-ID s web services, please refer to the following links: http://www.ad-id.org/user-support/faqs/faq-category/web-services http://www.ad-id.org/ad-id-web-services-api-guide Wold Informational [Page 4]

Scope: Ad-IDs are centrally registered, globally unique identifiers of advertising assets that are used worldwide. 3. Namespace Considerations Ad-IDs are intended for use in Internet applications, where URNs are routinely used to identify audiovisual resources. There is no direct mapping from Ad-IDs to existing URN namespaces. 4. Community Considerations The primary registrants of Ad-IDs are advertisers and agencies. Ad- IDs can be used by anyone to unambiguously identify advertising assets and retrieve underlying metadata. The primary benefits of its use are providing greater transparency and accountability in the advertising marketplace, helping to eliminate costly errors associated with the inconsistent use of advertising-asset identifiers throughout the advertising supply chain, and enabling a more granular audience measurement across multiple platforms. 5. Security Considerations This document specifies the syntax of the Ad-ID URN namespace and makes no security representations. However, note that failure to conform to the syntactic and lexical equivalence rules specified in [RFC3406] when using an Ad-ID as a criterion for accessing restricted resources can result in granting unauthorized access. 6. IANA Considerations This document defines "ad-id" in the "Formal URN Namespaces" registry. Wold Informational [Page 5]

7. Normative References [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997, <http://www.rfc-editor.org/info/rfc2141>. [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002, <http://www.rfc-editor.org/info/rfc3406>. [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <http://www.rfc-editor.org/info/rfc5234>. [SMPTERP2092-1] Society of Motion Picture and Television Engineers, "Advertising Digital Identifier (Ad-ID) Representations", SMPTE RP 2092-1, April 2015. Wold Informational [Page 6]

Appendix A. Additional Background Information Ad-IDs are an eleven-character ASCII string except for High Definition (HD) or Three-Dimensional (3D) codes, which have an H or D as the 12th character. Ad-ID may have Complimentary Definition Codes (CDCs), which are matching SD, HD, and/or 3D codes where only the 12th character of the code varies. This only applies to video codes. For example, a video with a standard format and high-definition format would have a single code for each format. Standard: ABCD1234000 High Definition: ABCD1234000H More information: http://www.ad-id.org/how-it-works/ad-id-structure Advertising Digital Identification <http://www.ad-id.org/> Author s Address Jarrett Wold Advertising Digital Identification (Ad-ID) 708 Third Avenue New York, NY 10017 Email: jwold@ad-id.org Wold Informational [Page 7]