RE: Signed Receipts and Mail Lists

Russ Housley <housley@vigilsec.com> Wed, 20 August 2003 01:44 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 VAA20533 for <smime-archive@lists.ietf.org>; Tue, 19 Aug 2003 21:44:15 -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 h7K192qt043674 for <ietf-smime-bks@above.proper.com>; Tue, 19 Aug 2003 18:09:02 -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 h7K192i9043672 for ietf-smime-bks; Tue, 19 Aug 2003 18:09:02 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [207.228.252.5]) by above.proper.com (8.12.9/8.12.8) with SMTP id h7K190qt043665 for <ietf-smime@imc.org>; Tue, 19 Aug 2003 18:09:01 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 3722 invoked by uid 0); 20 Aug 2003 01:09:01 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (12.167.144.138) by woodstock.binhost.com with SMTP; 20 Aug 2003 01:09:01 -0000
Message-Id: <5.2.0.9.2.20030819150730.03a4c5e8@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 19 Aug 2003 15:08:39 -0400
To: "g.lunt" <Graeme.Lunt@nexor.co.uk>
From: Russ Housley <housley@vigilsec.com>
Subject: RE: Signed Receipts and Mail Lists
Cc: ietf-smime@imc.org
In-Reply-To: <009001c3552a$723d8e50$d2353fc1@nexor.co.uk>
References: <5.2.0.9.2.20030722224635.0414f4d8@mail.binhost.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

Graeme:

> > When we designed the MLA mechanism, we assumed that each mail
> > list would have a separate key pair and certificate.  I do not
> > think that this is an unreasonable assumption.  Today, Web servers
> > that support more than one site have a certificate for each of the
> > sites.
>
>I had reached this conclusion on further reading of 2634. Whilst being
>able to use a single certificate (and ACs for example) for hundreds of
>lists would be useful, it is not a major concern at the moment.
>
>My main issue was to have a mechanism to indicate on whose behalf of
>whom a signed receipt was generated (e.g. in the case of an "All"
>request from  a ML).
>Either a specific field in the Receipt structure, or just an extension
>mechanism (which may be more generally useful).

I do not know if an update to RFC 2634 is planned.  I do not see it on the 
S/MIME WG charter.

Russ