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

Jarrett Wold <jwold@ad-id.org> Mon, 14 March 2016 14:28 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78F312DAA5 for <urn-nid@ietfa.amsl.com>; Mon, 14 Mar 2016 07:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ad-id.org
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 ks2mryPdi70y for <urn-nid@ietfa.amsl.com>; Mon, 14 Mar 2016 07:28:21 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (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 1F11A12D616 for <urn-nid@apps.ietf.org>; Mon, 14 Mar 2016 07:28:21 -0700 (PDT)
Received: by mail-pa0-x22b.google.com with SMTP id tt10so158627613pab.3 for <urn-nid@apps.ietf.org>; Mon, 14 Mar 2016 07:28:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ad-id.org; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=WbDpKPI9HKQT0lROGtTLdwl8s7wEs3nKyS4LVsDDYlQ=; b=MXo+F6p0Ig85Nlo38RAuyE4eBOw4QbB49ARAtrIgo7XwI4XeL6eh5YO5xzZiF/OfvS YnXhxvaZeaIcR7pUtbDWlXVZZ9h5jBwqUGjh0qSDTO5mcmxa6HTVfafVmZok8m6z7SNo ++Tkit8UaAF2nCIzXN/Iww7P85Xv5JEjaTR/I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=WbDpKPI9HKQT0lROGtTLdwl8s7wEs3nKyS4LVsDDYlQ=; b=GWXQiUaKT02TXtImjQ4K8EIrNywD2ANZFrjYxTS4oa7NzTgrAoKqOCIluZxOBGapn5 yrpsoH0Tb8DpoCRX8X3kaWhzot93RHgA6ZI2RW7QimJWjWKxS8U/3jZQM+scg0MIDGG0 8tKIzVF37gLSjK7vBVReZ+Vg/P4ZyHx+gRCnqFKf6EV/15Vfjwe+JjutogJq3A3QXL4z SSZlPWRruMWwU0lxeeWL62RolIcRELh+yee4ePT+WEBwnyb62JijeBT4c0mbl7XxHCkF ADqnHngp8uaExZpSPGDPpKyMp511qdRuQWMtgFxM1TQ+XUQf3uK6tlSR0Z4AiWVS8JKu X58g==
X-Gm-Message-State: AD7BkJIJkfXjPVxlek6t/NdCsMeHYN7HorLH3x6SB24RS2TOOhUHknzFdNj+fr0wOosv0xt2FdWk4y7tX/1toqH7
X-Received: by 10.67.6.72 with SMTP id cs8mr38101137pad.138.1457965700684; Mon, 14 Mar 2016 07:28:20 -0700 (PDT)
From: Jarrett Wold <jwold@ad-id.org>
References: <22a133140ac0f17928f11266f44d5e38@mail.gmail.com> <CA+9kkMB0We8F7XE8LuU15N9dXEzNGp0qdmde5Y5swsni8aSH_Q@mail.gmail.com> <74e35829070e97d7a94fb509af439987@mail.gmail.com> <CA+9kkMDcNbKiDUY=TPgdoBCVt6YAX5JaLof3DpLduwpX9TyyWw@mail.gmail.com>
In-Reply-To: <CA+9kkMDcNbKiDUY=TPgdoBCVt6YAX5JaLof3DpLduwpX9TyyWw@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHy1ibzGlVWBK90tvnpdbyrkqvKdQFBY3WpAl+3UJcBXDBsUJ7uYjpQ
Date: Mon, 14 Mar 2016 10:29:00 -0400
Message-ID: <3d4193cfc9ff301a86f9065c556cc759@mail.gmail.com>
Subject: RE: URN namespaces Submission for Ad-ID (www.ad-id.org)
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c21ef6af36e6052e03172f
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/f7ckYiq7D-WDmzQTo8MJmUjU_1s>
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 14 Mar 2016 14:28:24 -0000

Good Morning Ted –

Further clarifications:





*From:* Ted Hardie [mailto:ted.ietf@gmail.com]
*Sent:* Friday, March 11, 2016 7:23 PM
*To:* Jarrett Wold <jwold@ad-id.org>;
*Cc:* urn-nid@apps.ietf.org
*Subject:* Re: URN namespaces Submission for Ad-ID (www.ad-id.org)



Hi Jarrett,

Some further comments in-line.



On Fri, Mar 11, 2016 at 9:34 AM, Jarrett Wold <jwold@ad-id.org>; wrote:

Hi Ted –

Thanks for the feedback.  Please see my answers inline:



The document states that AD-Id assigns the identifiers and guarantees
uniqueness, but it also notes that the initial section of the identifier is
a company prefix.  Is the process of assignment distributed or centralizes?

A company Prefix created in Ad-ID also unique in our system.  These are
centralized in our system. Example: AAAA, ABCD, AB01, etc.

A company can choose to create a prefix or let the system select a prefix
at random.  If they choose to create a prefix, the system will determine if
it is available and issue it if it is.  Once the prefix is created, it’s
used to create the full Ad-ID codes.

Just to confirm my understanding, Ad-ID always creates the full code
(prefix + subcode), the process of producing the sub-code is not delegated
to the holder of the prefix.  Is that correct?



Ad-ID will system will always create the code.   We do offer several
different “code templates” for how the subcode is generated.  In each case,
we ensure the code is unique before the system generates the code.



Here is a link that defines the Ad-ID Structure and the multiple options we
offer.



http://www.ad-id.org/how-it-works/ad-id-structure



Example:  Company created two prefixes (ABCD & AB99).  Codes will be
generated under both prefixes based on what the user selects

*ABCD*

ABCD0001100

ABCD0002100



*AB99*

AB990001100

AB990002100



The document notes that an ad-id can be validated using ad-id's web
services.  Does or will that interface presenting the urn:adid form or the
urn:adid;cuid form?  If you present an ad-id, does it return the resource
or present metadata about the resource?

A user can use our web services and request by either an adid or the cuid.
Both resources are present in the XML returned (xml elements) as well as
descriptive metadata about the resource.

I see. Is there any method to dereference the resource by adid?  That is,
to return the ad on presentation of the adid? (Note that this is not
required, but if there were such a method, it would be a welcome addition
to the document)



I’m not quite sure what you mean by this.  Are you asking about other
methods to retrieve data by presence of an Ad-ID?  We are working on a few
company initiatives to have Ad-IDs embedded in digital slate (MXF) files
and XMP.  In these case, both the Ad-ID and MetaData would be present.



As a nit, it is more common for the abnf to split out the canonical string
"urn:" and the definition of the nid (in this case adid).

Im not quite clear on this.  Would you mind elaborating?

Thanks again.



It's just more common to say something like this:

 assigned-name = "urn" ":" NID ":" NSS

 Then follow up with the ABNF for the NID and name-space specific string.

I can make this update.

regards,

Ted Hardie



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

jwold@ad-id.org







*From:* Ted Hardie [mailto:ted.ietf@gmail.com]
*Sent:* Friday, March 11, 2016 11:54 AM
*To:* Jarrett Wold <jwold@ad-id.org>;
*Cc:* urn-nid@apps.ietf.org
*Subject:* Re: URN namespaces Submission for Ad-ID (www.ad-id.org)



Hi Jarrett,

I've done a quick review and I have a couple of questions.  The document
states that AD-Id assigns the identifiers and guarantees uniqueness, but it
also notes that the initial section of the identifier is a company prefix.
Is the process of assignment distributed or centralizes?

The document notes that an ad-id can be validated using ad-id's web
services.  Does or will that interface presenting the urn:adid form or the
urn:adid;cuid form?  If you present an ad-id, does it return the resource
or present metadata about the resource?

As a nit, it is more common for the abnf to split out the canonical string
"urn:" and the definition of the nid (in this case adid).

regards,

Ted Hardie



On Fri, Mar 11, 2016 at 6:32 AM, Jarrett Wold <jwold@ad-id.org>; wrote:

Hello –

I am resubmitting a request for an URN on behalf of Ad-ID as an Internet
Draft.



Thank You



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

jwold@ad-id.org