I just thought of a problem with my proposal. If an S/MIME v3 agent needs
to send a degenerate signedData to a S/MIME v2 legacy agent, then the
inclusion of the id-absent-content OID may cause problems. Therefore, I
won't pursue this proposal.
- John Pawling
At 04:44 PM 2/24/98 -0500, John Pawling wrote:
CMS, Sec 5.1, last para states: "In the degenerate case where there are no
signers, the EncapsulatedContentInfo value being "signed" is irrelevant. In
this case, the content type within the EncapsulatedContentInfo value being
"signed" should be data (as defined in section 4), and the content field of
the EncapsulatedContentInfo value should be omitted."
Recommend that this should be changed to: "In the degenerate case where
there are no signers, the EncapsulatedContentInfo value being "signed" is
irrelevant. In this case, the EncapsulatedContentInfo eContentType MUST be
set to id-absent-content and the eContent field of the
EncapsulatedContentInfo value MUST be omitted."
Recommend that Russ should define an id-absent-content OID.
J.G. Van Dyke & Associates, Inc.