[art] reverse lookup of named instances

Melvin Carvalho <melvincarvalho@gmail.com> Sun, 05 March 2017 18:02 UTC

Return-Path: <melvincarvalho@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4211293E8 for <art@ietfa.amsl.com>; Sun, 5 Mar 2017 10:02:10 -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 5xfD26p_mqXM for <art@ietfa.amsl.com>; Sun, 5 Mar 2017 10:02:08 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 B28D51289C4 for <apps-discuss@ietf.org>; Sun, 5 Mar 2017 10:02:08 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id 90so100965652ios.1 for <apps-discuss@ietf.org>; Sun, 05 Mar 2017 10:02:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3noelF5yFj7WbXiRdCUKxZELlGJhfmVTGtmSlXGzDj4=; b=WgelHQNYEj0o4cIIdupBvJP2dnd9jGzB+QfsDtq24tvYvRCqkojmYjKO9au3P5Ekpr XWBbB3UGywKJTj52AU3HvVsqRz6QBbFFrko8j2+dsG0Z4Uo8dpI1qUTZkczS0jydoG0E 5ttCM2QVW/IAB1pAZ2NjjkCEeXEUKfwJCE9gdSROlZVmtVchpODcdCOjaSkrHbR4dT0D cA78pAYz4PzQ/09AU+AhxJN4mo3mvp3KUfb942eLvRC71WCcYYcPDqLUC/BDs48sF6ZH HSdT1JyqYju/gyAan5jkVgBMUM8BvjvJh+kT0JA7pKMhVpdxzjyoXu/7xd3JLx07FuMv RwhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3noelF5yFj7WbXiRdCUKxZELlGJhfmVTGtmSlXGzDj4=; b=f/GryEhI6Z/KRliiPe5ZSIWEjc8LHI3rh8XhuiRKThR2sTh1PhL4iATNzAIBld382Q sHowTpTtd1dzSS2cq5oAm7b3hZrK4/ZaIfhM2lFVnzSqlEn8ww95xG+emXhyOs6c8p30 fTCu4o5/DIxEvnNT7FR7CdgxKHdDUVyIB4nsCw3NXSFfCka5/OMlcS6zdk6i8T3fIGww 6m1UWU+JnT+yTbqdlqNEzxfvSL4zYIIvduCYa3eVU2UTa9+jGZbzHIngXc4XxIsfvkfU +yNllfa01g+j2HimBNN38uPWnnYD5DlseRDsFLTwA1fz00QYvWn3+THlxeg3lx+7uhYJ sV5A==
X-Gm-Message-State: AMke39ki+YMZDoH1QMyfqPWRIkm8MCyRMv7/VhgBdoG/16cF9gDKn9X4N5w++sYdsaGuxQIIV4BFyV8L8JAZPQ==
X-Received: by 10.107.142.88 with SMTP id q85mr11412234iod.56.1488736927965; Sun, 05 Mar 2017 10:02:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.46.162 with HTTP; Sun, 5 Mar 2017 10:02:07 -0800 (PST)
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Sun, 05 Mar 2017 19:02:07 +0100
Message-ID: <CAKaEYh+-u1ggz2r80EPDj-kwkSu1uff-xXU1xXy7ahhKQfuF0Q@mail.gmail.com>
To: Apps Discuss <apps-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05a2b6c16dd00549ff9399"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Wc5EKTsjXqRMaXs6H2BWOz6DG6Y>
X-Mailman-Approved-At: Mon, 13 Mar 2017 08:06:07 -0700
Subject: [art] reverse lookup of named instances
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Mar 2017 18:02:10 -0000

I've been looking lately at the excellent RFC 6920, Naming things with
hashes.

It allows you to systematically translate a hash into a URI, and as another
excellent feature, provides a standard for doing a "forward" lookup.

In particular, if you lookup, say

https://some-domain/.well-known/ni/sha-1/<hash>

It will return some information about that hash, which is really useful.
It could have a name, a description, the algorithm details, and hashtage
etc.

This leads to a question / problem.  Let's say I have a tag, and I want to
find a list of hashes that contain that tag.

Does anyone know of a systematic way to solve this problem?

I was thinking something like

https://some-domain/.well-known/lookup/<term>

Which would return a list of hashes.

Is this a solved problem, or does something need to be invented?

Thanks in advance