Jim,
I agree with your comments except that I have the following comment:
You wrote:
2. Section 5.1 Since we are now octet encoding the eContent field, I
don't see any reason to say that for "external signatures" that the
content type must be id-data. Recommend we delete this sentence
EncapsulatedContentInfo eContentType is not an optional field, so there must
be an OID populated in the field. When signedData is used to support the
"external signatures" feature, there needs to be an OID in the eContentType
field that indicates that the eContent field is absent. Recommend that Russ
should define an id-absent-content OID.
================================
John Pawling
jsp(_at_)jgvandyke(_dot_)com
J.G. Van Dyke & Associates, Inc.
================================