RFC 3185: Reuse of CMS Content Encryption Keys
In plain English — editorial summary, not part of the RFC
This document describes a way to include a key identifier in a CMS (Cryptographic Message Syntax) enveloped data structure, so that the content encryption key can be re-used for further enveloped data packets. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3185
- Published
- October 2001
- Authors
- S. Farrell; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3211Password-based Encryption for CMSObsoleted
December 2001
- RFC 2876Use of the KEA and SKIPJACK Algorithms in CMSCurrent
July 2000
- RFC 3218Preventing the Million Message Attack on Cryptographic Message SyntaxCurrent
January 2002
- RFC 2797Certificate Management Messages over CMSObsoleted
April 2000
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 3126Electronic Signature Formats for long term electronic signaturesObsoleted
September 2001
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?