Re: Receipt Request Attribute
jsp@jgvandyke.com (John Pawling) Wed, 12 May 1999 16:53 UTC
Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02692 for <smime-archive@odin.ietf.org>; Wed, 12 May 1999 12:53:59 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id IAA14342 for ietf-smime-bks; Wed, 12 May 1999 08:50:19 -0700 (PDT)
Received: from apollo.jgvandyke.com (apollo.jgvandyke.com [158.189.10.100]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id IAA14338 for <ietf-smime@imc.org>; Wed, 12 May 1999 08:50:18 -0700 (PDT)
Received: from ajsn101.jgvandyke.com (ajsn101.jgvandyke.com [158.189.2.101]) by apollo.jgvandyke.com (8.8.8/8.8.8) with SMTP id LAA06963; Wed, 12 May 1999 11:59:46 -0400 (EDT)
Received: by ajsn101.jgvandyke.com (SMI-8.6/SMI-SVR4) id LAA26409; Wed, 12 May 1999 11:56:30 -0400
From: jsp@jgvandyke.com
Message-Id: <199905121556.LAA26409@ajsn101.jgvandyke.com>
Subject: Re: Receipt Request Attribute
To: jimsch@EXCHANGE.MICROSOFT.com, ietf-smime@imc.org
Date: Wed, 12 May 1999 11:56:29 -0400
Cc: jsp@ajsn101.jgvandyke.com
In-Reply-To: <2FBF98FC7852CF11912A0000000000010ECB5F31@DINO> from "Jim Schaad" at May 10, 99 12:49:32 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
All, I respectfully disagree with Jim's reply to Tom's message. First, ESS Section 1.3.4, Placement of Attributes, states: "The only attributes that are allowed in a counterSignature attribute are counterSignature, messageDigest, signingTime, and signingCertificates." This means that receiptRequest attributes are not allowed to be carried in a counterSignature attribute. Second, IMHO, it does not make sense to request a signedReceipt for a counterSignature. A signedReceipt is intended to prove that a recipient received and was able to verify the signature of the message sent by the signer. What would a signedReceipt prove for a counterSignature since the thing that is signed is not a message, it is the originator's signature of the original message??? I do not believe that we should change ESS to allow receiptRequests to be included in counterSignature attributes. - John Pawling > > Tom, > > My opinion on this would be: > > 1. A CounterSignature can contain a receipt request. > 2. The receipt request on the original SignedData and the receipt receipt > on the CounterSignature can be different. The requirement is that all > receipt requests in a SignerInfo sequence be the same and a CounterSigner > has a different SignerInfo sequence > > jim > > > -----Original Message----- > From: Tom Kung [mailto:Tom.Kung@entrust.com] > Sent: Monday, May 10, 1999 11:48 AM > To: 'ietf-smime@imc.org' > Subject: Receipt Request Attribute > > > Gooday, > > I would appreciate clarification on the following with respect to the > Receipt Request attribute: > > 1. May a CounterSignature contain a receipt request? > > 2. If so, MUST all receipt requests in a SignedData be identical? The > spec specifies that all Receipt Requests be identical. Is it the intent > that CounterSignatures containing a receipt request MUST also be identical > with other receipt requests if it exists? I don't see why each > countersignature can not have a different receipt request. > > > thanx,tom. >
- Receipt Request Attribute Tom Kung
- RE: Receipt Request Attribute Jim Schaad (Exchange)
- Re: Receipt Request Attribute John Pawling
- RE: Receipt Request Attribute Jim Schaad (Exchange)