CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 06:56:45 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=X1CUmiHYkwLIy6lK.vjKPYG0N4ZAw_dTj68naC1k8ng-1760079405-1.0.1.1-KTYJlgkCipsqifcO0x_BVMT7fh9WhwRr5WpeyftjLZH4_3f.YEA7SpxddYhiYDSinBGXru65MbV8ALlRVnygke7QLrTHahL0ev.BEUQFI7E; path=/; expires=Fri, 10-Oct-25 07:26:45 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c438372f3f1712-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 4073 » RFC Editor
Search RFCs
RFC 4073
Protecting Multiple Contents with the Cryptographic Message Syntax (CMS), May 2005
- File formats:
- Status:
- PROPOSED STANDARD
- Author:
- R. Housley
- Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4073
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4073
Abstract
This document describes a convention for using the Cryptographic Message Syntax (CMS) to protect a content collection. If desired, attributes can be associated with the 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