RFC 3278: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5753.
Current version: 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 ANSI X9.62 standard, developed by the ANSI X9F1 working group, the IEEE 1363 standard, and the SEC 1 standard. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3278
- Published
- May 2002
- Authors
- S. Blake-Wilson; D. Brown; P. Lambert
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 16
- Also known as
- —
- Obsoleted by:
- RFC 5753
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 3379Delegated Path Validation and Delegated Path Discovery Protocol RequirementsCurrent
September 2002
- RFC 3156MIME Security with OpenPGPCurrent
August 2001
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted
June 2003
- RFC 3566The AES-XCBC-MAC-96 Algorithm and Its Use With IPsecCurrent
September 2003
- RFC 3586IP Security Policy (IPSP) RequirementsCurrent
August 2003
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
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?