RFC 6031: Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6031
- Published
- December 2010
- Authors
- S. Turner; R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 29
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6030Portable Symmetric Key Container (PSKC)Current
October 2010
- RFC 6027IPsec Cluster Problem StatementCurrent
October 2010
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6012Datagram Transport Layer Security (DTLS) Transport Mapping for SyslogUpdated
October 2010
- RFC 6054Using Counter Modes with Encapsulating Security Payload (ESP) and Authentication Header (AH) to Protect Group TrafficCurrent
November 2010
- RFC 6063Dynamic Symmetric Key Provisioning Protocol (DSKPP)Current
December 2010
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
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?