IETF Logo Mail Archive

Re: [Endymail] Hashes of key as addresses

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 04 September 2014 13:58 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EABC01A88CD for <endymail@ietfa.amsl.com>; Thu, 4 Sep 2014 06:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.668] autolearn=ham
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 jBkfbpTIZGwh for <endymail@ietfa.amsl.com>; Thu, 4 Sep 2014 06:58:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2013C1A88D7 for <endymail@ietf.org>; Thu, 4 Sep 2014 06:58:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 737BDBE0F; Thu, 4 Sep 2014 14:58:14 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaFTOfOkhLjJ; Thu, 4 Sep 2014 14:58:13 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.42.16.156]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 17EAEBE0E; Thu, 4 Sep 2014 14:58:13 +0100 (IST)
Message-ID: <54086FF3.5020305@cs.tcd.ie>
Date: Thu, 04 Sep 2014 14:58:11 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: =?UTF-8?B?TWljaGFlbCBLasO2cmxpbmc=?= <michael@kjorling.se>, endymail@ietf.org
References: <CAMm+LwimhUi5uZAgm9erYtMJ9-o6+x__344TwKH4-Pa_-mckfg@mail.gmail.com> <20140829091133.GA25723@yeono.kjorling.se> <CAMm+LwhSYm7e4WevDKqewGuOk=O_Zd7dKa1ctfvBzyF3jz4jtg@mail.gmail.com> <20140904132955.GN603@yeono.kjorling.se>
In-Reply-To: <20140904132955.GN603@yeono.kjorling.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/OVDJ47NcTZkrKWKlxJiEpNvKq0w
Subject: Re: [Endymail] Hashes of key as addresses
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 13:58:26 -0000

Hiya,

In the hope of heading off a rathole discussion (about who
has what devices with what capabilities)...

On 04/09/14 14:29, Michael Kjörling wrote:
>> > One way that works very well is to use QR codes in an in-person
>> > meeting. Web of Trust never worked the way PhilZ wanted. But we didn't
>> > carry supercomputers with cameras (aka smartphones) then.

> Far from everyone does, even today. [1] Should the protocol be
> designed to essentially require such?

We're nowhere near the point where what's "required" is being
discussed really. I doubt PHB meant that QR codes ought be the
one and only way of doing anything. And even if he did, (which
I know he doesn't:-) that wouldn't matter so much now, and its
ok to regard 'em just an example of what might work in some
cases.

That kind of "what to make mandatory to implement" discussion
would be needed later for sure, but we're not there yet.

Cheers,
S.

v2.8.7 | Report a Bug | By Email