| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 17:02:03 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: 95f295df6d8fc16d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5652 » RFC Editor
Search RFCs
- File formats:
- Status:
- INTERNET STANDARD (changed from DRAFT STANDARD)
- Obsoletes:
- RFC 3852
- Updated by:
- RFC 8933, RFC 9629
- Author:
- R. Housley
- Stream:
- IETF
- Source:
- smime (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5652
Discuss this RFC: Send questions or comments to the mailing list smime@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5652
Abstract
This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS-TRACK]
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