Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 26 June 2012 11:26 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3DA21F860B for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KcjGGmmubuwy for <ietf@ietfa.amsl.com>; Tue, 26 Jun 2012 04:26:48 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 510CB21F8609 for <ietf@ietf.org>; Tue, 26 Jun 2012 04:26:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BA83D1715B2; Tue, 26 Jun 2012 12:26:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1340710007; bh=Cx6KDQGAJspu5E Vk9QZe9KSjyBCzoijSRggLeKXsECg=; b=QxEqzFrXTXHBt5hWsg8sCGH1TUPPJe FFzRCFIJvN5zcaf2SlBFGywNkDWuSV3/o3GAAE6bG7jxGL9JXnXnNrCWepPb/k2H nIjL2gyC1EbEJnCLHpOzVcdtP6r+1jrO7ltClpnNhZ3wxPmLjkZl0XtQVL8DsWEq K48gFBUIiTJia53jAnUGAUA7MlxY4/aEgJLRt8sbJ2PekmqIuLLhPjXmoVfJvOIV /kUOl4hK8EghMq5CYAwqn9cJ03Ud79mNaQwEUuyOUigg6YuCjTjDP05WGMh1ajsb FFfnkAy33FD4zVvxX4IrbSJToWIm1JiBNGRItgscIA2PytiaPxzkkw+Q==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 6ysaPInghEu8; Tue, 26 Jun 2012 12:26:47 +0100 (IST)
Received: from [IPv6:2001:770:10:203:8cee:98bb:ac1:26b] (unknown [IPv6:2001:770:10:203:8cee:98bb:ac1:26b]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 9301F17151B; Tue, 26 Jun 2012 12:26:45 +0100 (IST)
Message-ID: <4FE99C75.9010309@cs.tcd.ie>
Date: Tue, 26 Jun 2012 12:26:45 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie> <4FE998E9.9010809@it.aoyama.ac.jp>
In-Reply-To: <4FE998E9.9010809@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 11:26:49 -0000

Hi again Martin,

On 06/26/2012 12:11 PM, "Martin J. Dürst" wrote:
> So the question is really, what's the use case, and what's just a
> consequence of that use case. If confirmation of already available
> resources (e.g. like a fingerprint) is the (main?) use case, and the
> greater weight on "speakability" just a design consequence, then it
> makes sense to have two separate things.

Yes, confirmation is the main current use-case for nih as I understand
it and have said previously. (Of course the resource might not yet
be present, so "already available" isn't quite right, but that's a
nit.)

Have we beaten this to death sufficiently now? I hope so;-)

If you want to suggest a sentence that says that, feel free.

Stephen.