| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:52:12 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
set-cookie: __cf_bm=lT.gkwU5k03gO4TVb0L8LEDQD7bzQK2kzVr9L0OGEYs-1760097132-1.0.1.1-8XamnNI_pLc.ek7ZpSSulOvdpSWJScgTV6fW06kAgE7fho8aoHMaV2IpkvGK2RUSF0BA2TgCkgpw8ChkxVWATZCh_HkR8HPpVDXCGGA3Xxs; path=/; expires=Fri, 10-Oct-25 12:22:12 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5e8ff79c58cf1-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6031 » RFC Editor
Search RFCs
RFC 6031
Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type, December 2010
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6031
Discuss this RFC: Send questions or comments to the mailing list keyprov@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6031
Abstract
This document defines the symmetric key format content type. It is transport independent. The Cryptographic Message Syntax (CMS) can be used to digitally sign, digest, authenticate, or encrypt this content type. [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