RFC 2876: Use of the KEA and SKIPJACK Algorithms in CMS
In plain English — editorial summary, not part of the RFC
This document describes the conventions for using the Key Exchange Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction with the Cryptographic Message Syntax [CMS] enveloped-data and encrypted- data content types. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2876
- Published
- July 2000
- Authors
- J. Pawling
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 3211Password-based Encryption for CMSObsoleted
December 2001
- RFC 3218Preventing the Million Message Attack on Cryptographic Message SyntaxCurrent
January 2002
- RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated
February 1997
- RFC 2085HMAC-MD5 IP Authentication with Replay PreventionCurrent
February 1997
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 2875Diffie-Hellman Proof-of-Possession AlgorithmsObsoleted
July 2000
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?