DER encoding in RFC 3161
Koichi Sugimoto <[email protected]>
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <PS1PR03MB48921EE23E93434559DF1ECE9D730@PS1PR03MB4892.apcprd03.prod.outlook.com> |
Hello PKIX members, RFC 3161 specifies "The eContent SHALL be the DER-encoded value of TSTInfo." in "2.4.2. Response Format" Why RFC 3161 does not require DER-encoded value for full time-stamp token (CMS data)? On the other hand, following protocol encoding seems to require all DER-encoded for entire time-stamp message. 3.1. Time-Stamp Protocol Using E-mail 3.2. File Based Protocol 3.3. Socket Based Protocol 3.4. Time-Stamp Protocol via HTTP This seems time-stamp token requires DER-encoded indirectly. Regards, Koichi Sugimoto. _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix
smime.p7s
(application/pkcs7-signature, 5.5 KB) - not displayed