RFC 5753: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document describes how to use Elliptic Curve Cryptography (ECC) public key algorithms in the Cryptographic Message Syntax (CMS). The ECC algorithms support the creation of digital signatures and the exchange of keys to encrypt or authenticate content. The definition of the algorithm processing is based on the NIST FIPS 186-3 for digital signature, NIST SP800-56A and SEC1 for key agreement, RFC 3370 and RFC 3565 for key wrap and content encryption, NIST FIPS 180-3 for message digest, SEC1 for key derivation, and RFC 2104 and RFC 4231 for message authentication code standards. This document obsoletes RFC 3278. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5753
- Published
- January 2010
- Authors
- S. Turner; D. Brown
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 61
- Also known as
- —
- Obsoletes:
- RFC 3278
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 5408Identity-Based Encryption Architecture and Supporting Data StructuresCurrent
January 2009
- RFC 5246The Transport Layer Security (TLS) Protocol Version 1.2Obsoleted
August 2008
- RFC 6806Kerberos Principal Name Canonicalization and Cross-Realm ReferralsCurrent
November 2012
- RFC 6819OAuth 2.0 Threat Model and Security ConsiderationsUpdated
January 2013
- RFC 4505Anonymous Simple Authentication and Security Layer (SASL) MechanismCurrent
June 2006
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?