Re: [saag] IETF 93 Agenda Request - Key Discovery

Viktor Dukhovni <ietf-dane@dukhovni.org> Wed, 22 July 2015 20:28 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB4921A1B39 for <saag@ietfa.amsl.com>; Wed, 22 Jul 2015 13:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 1IeF5Yog64dJ for <saag@ietfa.amsl.com>; Wed, 22 Jul 2015 13:28:25 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1632D1A1B64 for <saag@ietf.org>; Wed, 22 Jul 2015 13:28:23 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 65D81284B55; Wed, 22 Jul 2015 20:28:21 +0000 (UTC)
Date: Wed, 22 Jul 2015 20:28:21 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: saag@ietf.org
Message-ID: <20150722202821.GL4347@mournblade.imrryr.org>
References: <55A7F601.9040902@cisco.com> <20150721222308.GU28047@mournblade.imrryr.org> <55AF43B7.60502@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <55AF43B7.60502@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/uotHQkFVyhIASS0J1L1nbIHxRsw>
Subject: Re: [saag] IETF 93 Agenda Request - Key Discovery
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: saag@ietf.org
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2015 20:28:26 -0000

On Wed, Jul 22, 2015 at 09:18:15AM +0200, ? Matt Miller wrote:

> However, do not confuse RFC 7565 "acct:" URIs for email addresses.
> Yes, they look a lot like an email address, as a "xmpp:" or "sip:" URI
> can look a lot like an email address.  The "acct:" URI is for a
> generic account identifier; it could be a placeholder to email, IM,
> VoIP, filesharing, etc.
> 
> My draft is intended for more than email.

A major difficulty is that email addresses and "accounts", are not
necessarily in one to one correspondence or even "few to one"
correspondence.  

How is one to know which "acct" URI is applicable to finding the
keys for a particular email recipient?  I probably should not even
be able to easily find out the login account behind a particular
email address.

Is the proposal intended to support key discovery for first contact?
If so how is the sender (of an email say), going to the find the
associated account to query?

Or is the sender expected to have previously received an "acct"
URI out-of-band and is only using it to maintain key freshness?

It still seems like this proposal is not a natural fit for email.
Perhaps it is better applicable to other protocols...

-- 
	Viktor.