Comments on draft-adid-urn-00

worley@alum.mit.edu (Dale R. Worley) Tue, 15 March 2016 02:44 UTC

Return-Path: <worley@alum.mit.edu>
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 2943A12D7AD for <urn-nid@ietfa.amsl.com>; Mon, 14 Mar 2016 19:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 Biaolv1__Lfi for <urn-nid@ietfa.amsl.com>; Mon, 14 Mar 2016 19:44:14 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70B5B12D7E6 for <urn-nid@apps.ietf.org>; Mon, 14 Mar 2016 19:44:14 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-08v.sys.comcast.net with comcast id W2k91s00229Cfhx012kDmQ; Tue, 15 Mar 2016 02:44:13 +0000
Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-ch2-03v.sys.comcast.net with comcast id W2kC1s00E1nMCLR012kCEd; Tue, 15 Mar 2016 02:44:13 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u2F2iCVs026922; Mon, 14 Mar 2016 22:44:12 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u2F2iBwo026919; Mon, 14 Mar 2016 22:44:11 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@alum.mit.edu (Dale R. Worley)
To: Jarrett Wold <jwold@ad-id.org>
Subject: Comments on draft-adid-urn-00
In-Reply-To: <22a133140ac0f17928f11266f44d5e38@mail.gmail.com> (jwold@ad-id.org)
Date: Mon, 14 Mar 2016 22:44:11 -0400
Message-ID: <87twk8cves.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1458009853; bh=e+0Cof9ANlwTZbTKaUoWN1dm+OeX9hoEI+mZu8NtoTU=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=QoC45gqH1UAbhfOgvSv1nWm7oc1oxMN8XFrROakNK5kDk116jTTvkUWQ63d5ItRh0 ixKyeOA+dEiWaThdNWzB0e7eKJ3hOlugW9GbajTRgPZADGDLE61YK48q6zzv9x6wYD Tmd+pksfZfuPbXqHaZh+ItlP0IQn/JMquoqD3Hwk8MgzxflW7DAaNwimDpFwTemZlU ePMlaDEahbqfWvg26TKCxQwP7FIEJuNPO+QzJefad0/ps/sVIkMfWgKTnqrKHbkOTZ 7Y3yPaJHXlq4SZr9ShzDY44yI7tv3fJNdCvmfVH/I41Cx11vcwe/WwlWKhOz5c+G1v Dw8w93EKe3K9Q==
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/s_fkPIS5FrxtBNvqYiKTvuwsBzA>
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: Tue, 15 Mar 2016 02:44:16 -0000

Here are a bunch of comments on draft-adid-urn-00.  Overall the concept
seems fine, but the document needs cleaning up.

The title contains "Adverting".  Have you run the draft through a
spelling checker?

      The following is an example of an Ad-ID Identifier in its
      canonical representation:

             ABCD0001000

      The canonical URN representation of the same Ad-ID Identifier is:

         urn:adid:ABCD0001000
         urn:adid:ABCD0001000H


      The 32-bit unique representation of the Ad-ID is:

         urn:adid:cuid:36faeaba

This example is difficult to follow.  The first item is
straightforward, as it is an 11 character string.  But the next item
isn't clear:  by definition, a "canonical" representation is one
representation chosen from among many.  You can say that both

         urn:adid:ABCD0001000
         urn:adid:ABCD0001000H

are URN representations of the Ad-ID identifier, but only one of them
can be canonical.  Also, it would be helpful if you explained why both
URNs correspond to ABCD0001000, or at least provide a reference to
some description which will explain it.

But, reading http://www.ad-id.org/how-it-works/ad-id-structure, it
seems that ABCD0001000H is not the *same* Ad-ID as ABCD0001000, but
rather the Ad-ID for the corresponding High Definition version of the
asset.  You need to clarify this so that the example is not
misleading.

It is not clear how the further "32-bit unique representation"
corresponds to the preceding three representations.  It's reasonably
clear what "32-bit" means as the URN contains a sequence of 8 hex
digits, but it's completely unclear what is "unique" about it.

Remember, this is the introduction, which should be readable by people
who don't already understand the technology, including people who
don't already understand Ad-IDs in all their forms.

There's some general trouble about the indentation of text.  For
instance, it seems that "The identifier structure is as follows:"
should be 4 spaces to the left, "Non alphanumeric ("special")
characters and spaces are not valid within an Ad-ID." should have a
blank like above it and be moved 3 spaces to the left, and "A
Canonical Full Ad-ID ..." should be moved 1 space to the left.

This text has some redundancy that should be removed:

          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 Ad-ID Identifier
          conforms to the syntax (expressed using ABNF (as specified in
          [RFC5234]):

The production

          adid_prefix = (ALPHA / %x30-39) 4*alphanum
               ; first character not zero

is incorrect on two counts:  As written, the first character can be
zero (which ix %x30).  The strings generated are 5 characters.  What
you want is

          adid_prefix = (ALPHA / %x31-39) 3*alphanum
               ; first character not zero

The instances of ALPHA and DIGIT might be intended to be "alpha" and
"digit".  Or do you mean to reference the productions ALPHA and DIGIT
in RFC 5234?  If so, you should eliminate the productions for "alpha"
and "digit" in the draft.

The BNF does not show how the "urn:adid:cuid" URNs are generated.  As
the BNF now stands, those examples are invalid.

      Ad-ID URNs are resolved via URN resolvers run under Ad-ID's
      responsibility.

It would be helpful here to provide a pointer to the documentation for
the resolvers.

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

Ditto.

Dale