Yves:
Sect 6.2: should not the RecipientInfo CHOICE elements be tagged? All the
elements of the CHOICE are SEQUENCE type with a common first element:
version. Would not this make the decoding ambiguous? I am not sure that
the version value is sufficient to remove the ambiguity if a compiler is
used to create decoding routines. I would like to check that myself but I
do not have an ASN.1 development environment.
The ktri alternative cannot be tagged and maintain backward compatability with
PKCS#7 v1.5. Therefore, I propose:
RecipientInfo ::= CHOICE {
ktri KeyTransRecipientInfo,
kari [1] KeyAgreeRecipientInfo,
mlri [2] MailListRecipientInfo }
Sect 6.2.1, version field description: I think that EntityIdentifier now
replaces RecipientIdentifier and rKeyId is replaced by SubjectKeyIdentifier.
You are correct.
Russ