| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:50:50 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=A6vdaiI5os01SOO.THAxVYhbg3IvYIenPLDXVtmm8_U-1760097050-1.0.1.1-T9XjNoLt.gP9Uc2D3ZfMx4FQIAvXc3ejzXxxClNzWZvREOgCmfYwOoM5QxQPwjYO2.NoMFsgIGXfEjw81GemJggRzefCoKZJUQhbkxxswPc; path=/; expires=Fri, 10-Oct-25 12:20:50 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5e6fd0c533e92-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