ietf-smime
[Top] [All Lists]

RE: Comments to MSG-02

1998-03-16 12:59:40
Jim,

I agree.

- John


At 10:23 AM 3/16/98 -0800, Jim Schaad (Exchange) wrote:

-----Original Message-----
From: jsp(_at_)jgvandyke(_dot_)com [mailto:jsp(_at_)jgvandyke(_dot_)com]
Sent: Monday, March 16, 1998 10:03 AM
To: ietf-smime(_at_)imc(_dot_)org
Subject: RE: Comments to MSG-02


Jim,

I agree with Jim's comments and have the following further comment:

13) Sec 3.2, 2nd para: Please make the following change: 

OLD: "The contentInfo field of the carried CMS object always contains a
MIME
entity that is prepared as described in section 3.1. The contentInfo field
must never be empty."

NEW: "The carried CMS object always contains a MIME entity that is prepared
as described in section 3.1.  Also, see Section 2.4.1 for instructions on
including the id-data OID and MIME entity in the CMS objects."

[Jim Schaad:  This is no longer as true of a statement.  Unless we are
prepared to say that we are going to use a different mime type for items
such as SignedData/Receipts.  I don't know that this should change or just
be a gotta to future implementors.]

[JSP: How about this: "The carried CMS object always contains a MIME entity
that is prepared as described in section 3.1 except in the case of a
signedData encapsulating a Receipt content type (i.e. signed receipt).  See
Section 2.4.1 for instructions on including the id-data OID and MIME entity
in CMS objects.  See [ESS] for instructions regarding signed receipts."

- John Pawling

[Jim Schaad: How about this:  "The carried CMS object always contains a MIME
entity that is prepared as described in section 3.1 if the eContentType is
id-data.  Other contents may be carried when the eContentType contains
different values.  See [ESS] for an example of this with signed receipts."



<Prev in Thread] Current Thread [Next in Thread>