RE: dissemination of public encryption certificates

"Blake Ramsdell" <blake@brutesquadlabs.com> Thu, 14 August 2003 22:06 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28488 for <smime-archive@lists.ietf.org>; Thu, 14 Aug 2003 18:06:19 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7ELgsqt020520 for <ietf-smime-bks@above.proper.com>; Thu, 14 Aug 2003 14:42:54 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h7ELgsIU020519 for ietf-smime-bks; Thu, 14 Aug 2003 14:42:54 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from brutesquadlabs.com (gtec136-m.isomedia.com [207.115.67.136] (may be forged)) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7ELgrqt020513 for <ietf-smime@imc.org>; Thu, 14 Aug 2003 14:42:53 -0700 (PDT) (envelope-from blake@brutesquadlabs.com)
Received: from DEXTER ([192.168.0.5]) by brutesquadlabs.com with ESMTP ; Thu, 14 Aug 2003 14:42:49 -0700
From: Blake Ramsdell <blake@brutesquadlabs.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, helm@fionn.es.net
Cc: 'Steve Hole' <steve.hole@messagingdirect.com>, 'Julien Pierre' <jpierre@netscape.com>, ietf-smime@imc.org
Subject: RE: dissemination of public encryption certificates
Date: Thu, 14 Aug 2003 14:42:48 -0700
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAALRejScPK20Ko+u6fl2DoHQEAAAAA@brutesquadlabs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E01113026@mou1wnexm02.verisign.com>
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: owner-ietf-smime@mail.imc.org 
> [mailto:owner-ietf-smime@mail.imc.org] On Behalf Of 
> Hallam-Baker, Phillip
> Sent: Thursday, August 14, 2003 11:17 AM
> To: 'helm@fionn.es.net'; Hallam-Baker, Phillip
> Cc: 'Steve Hole'; Julien Pierre; ietf-smime@imc.org
> Subject: RE: dissemination of public encryption certificates 
> 
> XKMS does not answer that question because I can't think of a 
> situation
> where is would be of interest. The certificate is simply a 
> data object that
> is created to establish the trustworthiness of a key. 
> Applications don't ask
> 'what is this good for?', they ask 'how do I do this task?'.

Well, I'm not sure I agree.  There are two major questions that
constantly need answers in the mind of an S/MIME client.  These are
pretty close to what Michael said in his message:

1. Given a particular email address, give me That Which Is Necessary and
Sufficient to send encrypted mail to that email address.

2. Given a particular certificate, is it suitable for signing mail that
came from a particular email address.  Michael said "what is it good
for", which I think is too broad a question.

If we're considering protocols that attempt to answer these types of
questions, those are the two questions that need to be answered by that
protocol (for interpersonal messaging with S/MIME, that is).

Blake