| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 04:47:16 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f69ee89d7bd3d4-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8933 » RFC Editor
Search RFCs
RFC 8933
Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier Protection, October 2020
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 5652
- Author:
- R. Housley
- Stream:
- IETF
- Source:
- lamps (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8933
Discuss this RFC: Send questions or comments to the mailing list spasm@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8933
Abstract
This document updates the Cryptographic Message Syntax (CMS) specified in RFC 5652 to ensure that algorithm identifiers in signed-data and authenticated-data content types are adequately protected.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us