This document came to my attention in my role as an expert reviewer on the S/MIME content types registry. As it my normal procedure I read through the document for anything that jumped out and I found one issue that I wanted to highlight.
In section 5.4 there is a note about encoding this content type with PKCS7 vs CMS. The problem is that this content cannot be encoded in PCKS#7 because it does not define an ASN.1 structure for the content. There is no correct way to encode a PKCS#7 message unless the content is an ASN.1 structure. For id-data this was done by defining it as OCTET STRING. In addition, even if one assigns the content type of OCTET STRING to this content type when signing using PKCS #7 and no ASN.1 type for CMS (which is what happens for id-data), the result is that there is absolutely no difference between the resulting object if you encode by PKCS #7 or CMS. This paragraph should be removed and it should talk about something else instead. Jim
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
