CurrentPROPOSED STANDARDIETF stream

RFC 5083: Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type

In plain English — editorial summary, not part of the RFC

This document describes an additional content type for the Cryptographic Message Syntax (CMS). The authenticated-enveloped-data content type is intended for use with authenticated encryption modes. All of the various key management techniques that are supported in the CMS enveloped-data content type are also supported by the CMS authenticated-enveloped-data content type. [STANDARDS-TRACK]

Document record

Document ID
RFC5083
Published
November 2007
Authors
R. Housley
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
10
Also known as
Updates:
RFC 3852

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5083-cryptographic-message-syntax-cms-authenticated-enveloped-data-content-type