All,
Darren wrote:
I agree it does meet the requirement, as would redefining Attribute
as Attribute ::= SEQUENCE {
type ...snip...
critical BOOLEAN DEFAULT FALSE,
values ...snip... }
This would also be backwards compatible, and closer to X.509's
way of expressing criticality ;-)
This solution does not maximize backwards compatibility because if the
attribute is critical, then the Attribute critical field would be present
(and TRUE). This would break the S/MIME v2 agents because they are not
designed to process the critical field. I like Phill's "list of OIDs"
solution proposed in Dave K's earlier message.
Darren wrote:
The reliance on MIME encodings that a meant, was the fact that data
has to be MIME encoded before it is protected using S/MIME, not that
the form that gets finally sent out is dependant in MIME - or am I
reading the specs incorrectly?
You are reading the S/MIME v3 Message Spec and ESS spec correctly. Note
that specs could be written for another application environment (such as
X.400) that could use the CMS objects without MIME encapsulation (but that
is the topic for a work group other than the S/MIME WG).
================================
John Pawling
jsp(_at_)jgvandyke(_dot_)com
J.G. Van Dyke & Associates, Inc.
================================