rfc-6161

Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type

S. Turner

date2011-04 streamIETF wgnon working group statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc6161 doi10.17487/RFC6161

This document describes the conventions for using several Elliptic Curve cryptographic algorithms with the Cryptographic Message Syntax (CMS) encrypted key package content type. Specifically, it includes conventions necessary to implement Elliptic Curve Diffie-Hellman (ECDH) with EnvelopedData and Elliptic Curve Digital Signature Algorithm (ECDSA) with SignedData. This document extends RFC 6033. [STANDARDS-TRACK]

updates

rfc-6033 — Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type

Extracted elements (6)

design-rationale §1

This document does not define any new algorithms; instead, it refers to previously defined algorithms. It amends RFC 6033 by adding elliptic curve algorithm conventions that were absent from that document.

crypto

interoperability-note §4

The easiest way to implement SignedData and EnvelopedData is with public key certificates per RFC 5280 and RFC 5480. Implementations using ECDSA or ECDH should use these certificate profiles.

crypto, pkix

normative-requirement §3 MAY

If an implementation encapsulates EncryptedKeyPackage with SignedData, then it MAY support the signature scheme ECDSA.

crypto

normative-requirement §4 MUST

If an implementation supports ECDSA or ECDH, then it MUST support keys on the P-256 curve.

crypto, pkix

normative-requirement §2 MAY

When key agreement is used, standard (as opposed to cofactor) ECDH MAY be supported for EnvelopedData.

crypto

security-consideration §5

The security considerations from RFC 5280, RFC 5480, RFC 5652, RFC 5753, RFC 6033, and RFC 6090 all apply to this document. No additional security analysis is provided beyond those references.

crypto, security, pkix