RFC 4010: Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document specifies the conventions for using the SEED encryption algorithm for encryption with the Cryptographic Message Syntax (CMS). SEED is added to the set of optional symmetric encryption algorithms in CMS by providing two classes of unique object identifiers (OIDs). One OID class defines the content encryption algorithms and the other defines the key encryption algorithms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4010
- Published
- February 2005
- Authors
- J. Park; S. Lee; J. Kim; J. Lee
- Status
- PROPOSED STANDARD
- 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 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 5114Additional Diffie-Hellman Groups for Use with IETF StandardsCurrent
January 2008
- RFC 6109La Posta Elettronica Certificata - Italian Certified Electronic MailCurrent
April 2011
- RFC 6211Cryptographic Message Syntax (CMS) Algorithm Identifier Protection AttributeCurrent
April 2011
- RFC 4013SASLprep: Stringprep Profile for User Names and PasswordsObsoleted
March 2005
- RFC 4025A Method for Storing IPsec Keying Material in DNSCurrent
March 2005
- RFC 4043Internet X.509 Public Key Infrastructure Permanent IdentifierCurrent
May 2005
- RFC 4046Multicast Security (MSEC) Group Key Management ArchitectureCurrent
May 2005
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?