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

Ted Hardie <ted.ietf@gmail.com> Sat, 12 March 2016 00:23 UTC

Return-Path: <ted.ietf@gmail.com>
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 A057E12DDE5 for <urn-nid@ietfa.amsl.com>; Fri, 11 Mar 2016 16:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.com
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 KcuzMKwBxiPZ for <urn-nid@ietfa.amsl.com>; Fri, 11 Mar 2016 16:22:59 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (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 F03A712DDE2 for <urn-nid@apps.ietf.org>; Fri, 11 Mar 2016 16:22:58 -0800 (PST)
Received: by mail-ob0-x230.google.com with SMTP id m7so128842273obh.3 for <urn-nid@apps.ietf.org>; Fri, 11 Mar 2016 16:22:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=orcJt93IxPKtryBu5M23eoU5BahgLVGXJy3/eNpcntA=; b=J7bUOOChYIiKcHVwEMggvyfx6urXPJz3m3nY38wVu4byyfIMEjobGsDZMsvn9XE3sN r6KjD4kCfgMmGRG+k5fGaBwpThvsTWwnvzwc6LMXH4s1fcGwXza4QwcHVGaHjG9Afr8E dH55Tw00Fe72SBoGTS9eoaU6VO+qUiHBjLZwU6fgqLvYYFM1uOLpVekcrBhpxuEeAywq WHyCH0cMe9PAlXh+p0iLTQjC/p7a5YnTtJ9uFChP5hLiNuZQEol0dKROW91Kw+ir6Ox4 LP8HJu2xpLyt2WqHKaIvZdeulv8wDr223UtwpMnB5gv4xLmUjJ2Iz9is3/TohxhcN+7H Z+4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=orcJt93IxPKtryBu5M23eoU5BahgLVGXJy3/eNpcntA=; b=F8lbRqQ84FLW3Pf0SW02ax6PjBKa+gSVSN7o9fxvOOQes1CYXPF2aSdOHSzorS0ZF8 KYZDBmt+6VCh/9KQubxLT+lbvcFQb/7Wh9KCXHA/evt3UNxmbYk0VmYC2eEL+O88eC5S xy9D/qC7ncB0x4jvcbkpf53WMD1kECNIycTVPHHKZNM2bk36/oW8CdBZZWTlnGqsNk4o ohwsJfTBuMtZgjyL5FL8wn3XVoNLqGj7BeVpRIZJquCpZPaAYlP8/JS1tUeP18AeJdEZ IUmlfk+dA/VRxQlmExjay51IXcGlbaAGDW1V0fVrK7HbEZOh5XLc9lILN487Yx5q4BLN dH9Q==
X-Gm-Message-State: AD7BkJLsDZx6s3ZgQebSynHkyCSC6l7A2S57BhdAQAFq0W9NOZJKGRDT8xsMIcVXCSlf/fqZ1zEmD6I5r1gSkQ==
X-Received: by 10.182.86.98 with SMTP id o2mr7427805obz.27.1457742178295; Fri, 11 Mar 2016 16:22:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.51.6 with HTTP; Fri, 11 Mar 2016 16:22:38 -0800 (PST)
In-Reply-To: <74e35829070e97d7a94fb509af439987@mail.gmail.com>
References: <22a133140ac0f17928f11266f44d5e38@mail.gmail.com> <CA+9kkMB0We8F7XE8LuU15N9dXEzNGp0qdmde5Y5swsni8aSH_Q@mail.gmail.com> <74e35829070e97d7a94fb509af439987@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 11 Mar 2016 16:22:38 -0800
Message-ID: <CA+9kkMDcNbKiDUY=TPgdoBCVt6YAX5JaLof3DpLduwpX9TyyWw@mail.gmail.com>
Subject: Re: URN namespaces Submission for Ad-ID (www.ad-id.org)
To: Jarrett Wold <jwold@ad-id.org>
Content-Type: multipart/alternative; boundary=089e0149d020b626a3052dcf0c3f
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/N8A59FhMcUHAuHX5uTjqgbjP6tQ>
Cc: "urn-nid@apps.ietf.org" <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: Sat, 12 Mar 2016 00:23:01 -0000

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?


>
>
> 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)


> 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.

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
>
>
>
>
>