URN namespaces Submission for Ad-ID (www.ad-id.org)

Jarrett Wold <jwold@ad-id.org> Fri, 29 January 2016 16:12 UTC

Return-Path: <jwold@ad-id.org>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071B41B3100 for <urn-nid@ietfa.amsl.com>; Fri, 29 Jan 2016 08:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.332
X-Spam-Level: *
X-Spam-Status: No, score=1.332 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wnxMLqTTkXe for <urn-nid@ietfa.amsl.com>; Fri, 29 Jan 2016 08:12:02 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55E371B30FF for <urn-nid@apps.ietf.org>; Fri, 29 Jan 2016 08:12:02 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id l66so61012884wml.0 for <urn-nid@apps.ietf.org>; Fri, 29 Jan 2016 08:12:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ad-id.org; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=aQrgbBir+EzJVFAQKzVY/Cfi/ty1vYW0r0WMXsEs2ds=; b=GBmNbIQyAIunN+Gke8bPv6oS9KCFCgR9I1N+6AzSOqu5QV5jrXwL0Uk20xpQGdLkDH 5DItssQ26MUnEtv1M9Qni9QKbhOUQe4p0q8PmbdWpZyuC9Bqady07748G+/EjV2F/5LM 6f6PpOtDXHvdVrmEcCzxfupU7EJBESJV1+kws=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=aQrgbBir+EzJVFAQKzVY/Cfi/ty1vYW0r0WMXsEs2ds=; b=Nq65qGMBwCygwwlmjIen6xZ9ahZU/y408QT48FTW9JhbxS/9fxZ1F9lmuqwpG+ZYVr Ex0ubTlzL/XE6Mhnk9z+8/w32zCQx+kLrk9+FZqOAS3GOAuUkz+tVW1j6yeCGUXiYT/e kIb+G3AHZ2UjsgFupuMm6XUMd44A15YJ8+mw4cE9YQ+Cc9ss6Ra/jK5OpWx7kTofQlFl FAN8pnrxQ+RjHyqBmtjAq7ax/Trktnke6Dz3WA/t5QBduBvpBid/D7s/mgRxReNZ3FKI iqI5MfBx8CoB4hPZ3pgyufAcv9SL0bFYutQSz0jfc1jD69PfjFl5401IeyCZIJEk+pg4 4Ufw==
X-Gm-Message-State: AG10YOTwrgjtT9Q4fgvrmht8eEndG0crxUXAZsQUk32HDcFSyheo369b/9Fo9irRDArYJhDQ7ojLCdQ0w2mC0WvQ
X-Received: by 10.194.216.100 with SMTP id op4mr9150103wjc.85.1454083920514; Fri, 29 Jan 2016 08:12:00 -0800 (PST)
From: Jarrett Wold <jwold@ad-id.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdFar6TfbX8pV9DMQyWaIGT6zl2pNQ==
Date: Fri, 29 Jan 2016 11:12:01 -0500
Message-ID: <798adff9c52a63eaed9f2325ae8f20bc@mail.gmail.com>
Subject: URN namespaces Submission for Ad-ID (www.ad-id.org)
To: urn-nid@apps.ietf.org
Content-Type: multipart/alternative; boundary=089e014935f48e6ab7052a7b4b36
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/c630xUJMRHscI049YSVCfsfBsI0>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 16:13:13 -0000

I am submitting a request for an URN Namespace for Advertising Digital
(Ad-ID).



Thank You



*Jarrett Wold *| *Ad-ID LLC*
Director of Technology & Platforms
646-708-8131

jwold@ad-id.org



BEGIN TEMPLATE

   The namespace definition according to the template in [RFC3406
<https://tools.ietf.org/html/rfc3406>] is as

   follows:



   Namespace ID:



      adid



   Registration Information:



      Version 1



      2015-12-21



   Declared registrant of the namespace:



      Name:



         Advertising Digital Identification, LLC



      Address:



         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 as follows:



An Ad-ID Identifier consists of an eleven or twelve character string.

This string is divided into three parts:

1.  a four-character alphanumeric (non-leading zero) Company Prefix

2.  a seven-character alphanumeric Unique Code

3.  a one-character Video Format Identifier.

Non alphanumeric (“special”) characters and spaces are not valid within the
structure of an Ad-ID.

A Canonical Full Ad-ID Identifier shall conform to the syntax specified
below using ABNF (as specified in IETF RFC 5234): The URN representation
URN-ADID of an ADID Identifier conforms to the syntax (expressed using ABNF
(as specified in [RFC5234 <https://tools.ietf.org/html/rfc5234>]):



FULL_ADID_IDENTIFIER = FULL_ADID_PREFIX1 FULL_ADID_PREFIX2 FULL_ADID_CODE
{FULL_ADID_SUFFIX}

FULL_ADID_PREFIX1 = 1*ALPHANUM = %x41-5A; A-Z / %x31-39; 1-9

FULL_ADID_PREFIX2 = 3*ALPHANUM = %x41-5A; A-Z / %x30-39; 0-9

FULL_ADID_CODE = 7*ALPHANUM

FULL_ADID_SUFFIX = “H” / “D”

DIGIT = %x30-39; 0-9

ALPHA = %x41-5A; A-Z

ALPHANUM = ALPHA / DIGIT



The following is an example of the string representation of an ADID as   a URN:



      urn:adid:ABCD0001000

      urn:adid:ABCD0001000H





32-BIT unique representation of the FULL_ADID_CODE;



The short version (compact unique identifier) of the identifier is as follows:





      urn:adid:cuid:<CUID>

      Example: urn:adid:cuid:36faeaba



where CUID is a 32-BIT unique representation of the full Ad-ID code as
defined above.





   Relevant ancillary documentation:



      [SMPTERP2092-1] specifies the representation of Ad-ID.





   Identifier uniqueness considerations:



The ADID Registrar is responsible for managing the assignment of the
ADID and shall ensure the uniqueness of all ADID URNs by checking such
names against the list of existing ids.



ADID assigns the identifier, adid, in such a way

      that the uniqueness of the 'adid' will be maintained.





      Furthermore, an ADID Identifier is associated with a single

      URN-ADID.





   Identifier persistence considerations:



The assignment process guarantees that ‘adids’ are not reassigned or
reused and the binding between the id and its resource is permanent.



      By reference this URN namespace inherits those rules







   Process of identifier assignment:



ADIDs are generated by Ad-ID’s proprietary registration          procedures.







   Process for identifier resolution:



ADID URNs are resolved via URN resolvers run under ADID     responsibility.















   Rules for Lexical Equivalence:



      Lexical equivalence of ADID-URN is defined by case-insensitive

      string match.



   Conformance with URN Syntax:



      As specified above, the syntax of ADID-URN is a subset of the URN

      syntax specified in [RFC2141 <https://tools.ietf.org/html/rfc2141>].



   Validation mechanism:



      The validity of an ADID-URN can be checked using AD-ID’s web services.





   Scope:



      ADID Identifiers are centrally registered, globally unique

      identifiers for use with advertising assets worldwide.