Receipt Request Processing Questions
"Jim Schaad" <jimsch@nwlink.com> Sat, 07 June 2003 20:18 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 QAA20716 for <smime-archive@lists.ietf.org>; Sat, 7 Jun 2003 16:18:51 -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 h57JoQAF023401 for <ietf-smime-bks@above.proper.com>; Sat, 7 Jun 2003 12:50:26 -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 h57JoQX2023400 for ietf-smime-bks; Sat, 7 Jun 2003 12:50:26 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.174]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h57JoPAF023395 for <ietf-smime@imc.org>; Sat, 7 Jun 2003 12:50:25 -0700 (PDT) (envelope-from jimsch@nwlink.com)
Received: from ROMANS (ip237.c132.blk1.bel.nwlink.com [209.20.132.237]) by smtp4.pacifier.net (Postfix) with ESMTP id D474F6A83B for <ietf-smime@imc.org>; Sat, 7 Jun 2003 12:29:17 -0700 (PDT)
Reply-To: jimsch@exmsft.com
From: Jim Schaad <jimsch@nwlink.com>
To: Ietf-Smime <ietf-smime@imc.org>
Subject: Receipt Request Processing Questions
Date: Sat, 07 Jun 2003 12:49:59 -0700
Message-ID: <003901c32d2d$fb071730$1700a8c0@augustcellars.local>
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
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
The following do not appear to be well address in the present ESS document. 1. For the message S1(S2(M)) - If S2 validates and contains a receipt request but S1 fails to validate. Should the receipt be generated? 2. For the message S1(S2(M)) - If S2 validates and contains a receipt request, S1 contains an MLExpansionHistory attribute, but cannot be validate due to either a) missing certificate or b) unknown signing algorithm. Should a) the receipt be generated and b) the MLExpansionHistory attribute be obeyed? 3. The following is a "new" case S1(E1(?)) - S1 contains a receipt request, E1 cannot be decrypted due to the lack of a lock box for the receipient. Should a receipt be generated? Jim
- Receipt Request Processing Questions Jim Schaad
- Re: Receipt Request Processing Questions Sean P. Turner