Re: Advice on NID for media fingerprint

worley@ariadne.com (Dale R. Worley) Mon, 06 June 2016 19:49 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 C602812D50E for <urn-nid@ietfa.amsl.com>; Mon, 6 Jun 2016 12:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.766
X-Spam-Level:
X-Spam-Status: No, score=0.766 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 886OFa7tFfH6 for <urn-nid@ietfa.amsl.com>; Mon, 6 Jun 2016 12:49:37 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 B184A12D105 for <urn-nid@apps.ietf.org>; Mon, 6 Jun 2016 12:49:37 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by comcast with SMTP id A0WHbqsGCp1BeA0WmbxaEp; Mon, 06 Jun 2016 19:49:36 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1465242576; bh=oDAgnqu8fK4AN4P+8iXPP5kq+Ag6ZKrvoP9+6iGWHJs=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=CSeim5A1twmGkXyg4pf6PrE3tVEdAVHolX1SC5AxrEBexpBvqqC3D3HDM107OIzDP pOTGPdrKNNlYt9mwz1kGw69fu+cg+rFUjRRqEgkhjhDfnSasGHh34zcCRGfs4yvx2m C9AUYRKR7nH0PmNHnYnkdGA2fqm0tyTTHQpzerkHZWFO40ZEYUEBe9EKcwqf6F9syz yShGl4EJX25vCA2fhmBMFFxoZeSqDXLSJU0SKraMNxrcE0j/hFCVsDbZ8qztT1khVg jNvCSK3CmL3g+V0q/Aixgq8nb1Fn6OmwZvbPlEDnez6jLtIqm4y4evi8SJkKe1VxmE 2TK++t6s56Hqg==
Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-ch2-12v.sys.comcast.net with comcast id 3Xpb1t00G1nMCLR01XpcKN; Mon, 06 Jun 2016 19:49:36 +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 u56JnZOm024210; Mon, 6 Jun 2016 15:49:35 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u56JnYdK024207; Mon, 6 Jun 2016 15:49:34 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Jonas Oberg <jonas@fsfe.org>
Subject: Re: Advice on NID for media fingerprint
In-Reply-To: <20160503182125.GA30415@silk> (jonas@fsfe.org)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 06 Jun 2016 15:49:34 -0400
Message-ID: <871t4aayi9.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn-nid/thkd5jvKPNjUgz7g8Oepmb2JTSc>
Resent-From: <alias-bounces@ietf.org>
Resent-To: @apps.ietf.org
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, 06 Jun 2016 19:49:38 -0000

I was searching and discovered that if you search for "urn sha-1 hash"
you get a considerable number of references to URI schemes and URN
namespaces that have been proposed that use cryptographic hashes to
identify objects.  Some of them have a history of usage.

https://www.google.com/search?q=urn+sha-1+hash&ie=utf-8&oe=utf-8

A particularly amusing one starts thus:

http://www.nuke24.net/docs/2015/HashURNs.html

    Existing standards for hash-based URN schemes

    TL;DR: Before inventing a new URI scheme, see if there's already one
    in use that does what you need.	

Dale