IETF Logo Mail Archive

Re: Advice on NID for media fingerprint

Sean Leonard <dev+ietf@seantek.com> Tue, 03 May 2016 00:22 UTC

Return-Path: <dev+ietf@seantek.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 6A89012D6B5 for <urn-nid@ietfa.amsl.com>; Mon, 2 May 2016 17:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=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 BA-7tnwluBq7 for <urn-nid@ietfa.amsl.com>; Mon, 2 May 2016 17:22:56 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32EF12D6AB for <urn-nid@apps.ietf.org>; Mon, 2 May 2016 17:22:55 -0700 (PDT)
Received: from [10.0.206.76] (unknown [107.14.56.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id AA22622E253; Mon, 2 May 2016 20:22:54 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Advice on NID for media fingerprint
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <878u014ltl.fsf@hobgoblin.ariadne.com>
Date: Mon, 02 May 2016 17:23:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <30D4F8E2-A3DD-4E95-88CD-5475443A7E3C@seantek.com>
References: <878u014ltl.fsf@hobgoblin.ariadne.com>
To: Jonas Oberg <jonas@fsfe.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/_TSwKK4bINTkzW-EJCZOC_TnxTA>
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, 03 May 2016 00:22:57 -0000

Yep. Ditto.

With URNs, resources/things named by the URN can’t collide. The namespace is supposed to guarantee that collisions (i.e., reassignment or multiple-assignment) does not occur.

So URN is inappropriate.

You could register a URI scheme, which has a lower barrier to entry (in some respects). However, it’s not even clear that you need these identifiers to fit in a URI protocol slot. If you don’t need to shoehorn the identifier into a URI protocol slot, don’t bother.

Best regards,

Sean

> On Apr 25, 2016, at 10:53 AM, Dale R. Worley <worley@ariadne.com> wrote:
> 
> Certainly the idea is interesting, but I'm not sure it qualifies as a
> system of "names" -- in a sample of 100,000 images, 1% of the images had
> the same blockhash as one or more other images.  (There are something
> like 30 million images in Wikipedia, which would imply over 300,000
> collisions.)
> 
> Dale
>

v2.23.0 | Report a Bug | By Email