RE: dissemination of public encryption certificates

jpierre@netscape.com (Julien Pierre) Fri, 15 August 2003 03:28 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 XAA05337 for <smime-archive@lists.ietf.org>; Thu, 14 Aug 2003 23:28:40 -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 h7F34Eqt032388 for <ietf-smime-bks@above.proper.com>; Thu, 14 Aug 2003 20:04:14 -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 h7F34Duo032387 for ietf-smime-bks; Thu, 14 Aug 2003 20:04:13 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from netscape.com (r2d2.aoltw.net [64.236.137.26]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7F34Dqt032381 for <ietf-smime@imc.org>; Thu, 14 Aug 2003 20:04:13 -0700 (PDT) (envelope-from jpierre@netscape.com)
Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47]) by netscape.com (8.10.0/8.10.0) with ESMTP id h7F343309055 for <ietf-smime@imc.org>; Thu, 14 Aug 2003 20:04:03 -0700 (PDT)
Received: from kitty.nscp.aoltw.net ([10.169.25.23]) by judge.mcom.com (Netscape Messaging Server 4.15) with ESMTP id HJN4ID00.F07; Thu, 14 Aug 2003 20:03:49 -0700
Date: Thu, 14 Aug 2003 20:05:04 -0700
From: jpierre@netscape.com
Subject: RE: dissemination of public encryption certificates
To: Blake Ramsdell <blake@brutesquadlabs.com>
cc: 'Hallam-Baker Phillip' <pbaker@verisign.com>, helm@fionn.es.net, 'Steve Hole' <steve.hole@messagingdirect.com>, ietf-smime@imc.org
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAALRejScPK20Ko+u6fl2DoHQEAAAAA@brutesquadlabs.com>
Message-ID: <3F3C4DE0.8020204@netscape.com>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAALRejScPK20Ko+u6fl2DoHQEAAAAA@brutesquadlabs.com>
X-Mailer: AOL Communicator (20030811Trnk.1 Win)
Organization: Netscape
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms010704000904080802040505"
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>

Blake,

Blake Ramsdell wrote on 08/14/2003, 14:42:
 >
 > 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).

Yes. I believe this is relevant to the SMIME mailing list, even though 
the choice and design of that protocol may not affect the SMIME message 
format itself, as these are major deployment issues.

It would be highly desirable for one protocol to be designated for the 
purpose of solving these problems, as opposed to having a plethora of 
different solutions and having various client programs use different 
approaches, which would get us back to square one.

-- 
I am the dog in dogfood