Algorithms for Cryptographic Message Syntax (CMS) Protection of Symmetric Key Package Content Types
RFC 6160

Document Type RFC - Proposed Standard (April 2011; No errata)
Was draft-turner-cms-symmetrickeypackage-algs (individual in sec area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 6160 (Proposed Standard)
Telechat date
Responsible AD Tim Polk
Send notices to turners@ieca.com, draft-turner-cms-symmetrickeypackage-algs@ietf.org
Internet Engineering Task Force (IETF)                         S. Turner
Request for Comments: 6160                                          IECA
Category: Standards Track                                     April 2011
ISSN: 2070-1721

      Algorithms for Cryptographic Message Syntax (CMS) Protection
                 of Symmetric Key Package Content Types

Abstract

   This document describes the conventions for using several
   cryptographic algorithms with the Cryptographic Message Syntax (CMS)
   to protect the symmetric key package content type.  Specifically, it
   includes conventions necessary to implement SignedData,
   EnvelopedData, EncryptedData, and AuthEnvelopedData.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6160.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Turner                       Standards Track                    [Page 1]
RFC 6160          Algorithms for Symmetric Key Packages       April 2011

1.  Introduction

   This document describes the conventions for using several
   cryptographic algorithms with the Cryptographic Message Syntax (CMS)
   [RFC5652] to protect the symmetric key package content type defined
   in [RFC6031].  Specifically, it includes conventions necessary to
   implement the following CMS content types: SignedData [RFC5652],
   EnvelopedData [RFC5652], EncryptedData [RFC5652], and
   AuthEnvelopedData [RFC5083].  Familiarity with [RFC5083], [RFC5652],
   [RFC5753], and [RFC6031] is assumed.

   This document does not define any new algorithms; instead, it refers
   to previously defined algorithms.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  SignedData

   If an implementation supports SignedData, then it MUST support the
   signature scheme RSA [RFC3370] and SHOULD support the signature
   schemes RSA Probabilistic Signature Scheme (RSASSA-PSS) [RFC4056] and
   Digital Signature Algorithm (DSA) [RFC3370].  Additionally,
   implementations MUST support the hash function SHA-256 [RFC5754] in
   concert with these signature schemes, and they SHOULD support the
   hash function SHA-1 [RFC3370].  If an implementation supports
   SignedData, then it MAY support Elliptic Curve Digital Signature
   Algorithm (ECDSA) [RFC6090][RFC5753].

3.  EnvelopedData

   If an implementation supports EnvelopedData, then it MUST implement
   key transport, and it MAY implement key agreement.

   When key transport is used, RSA encryption [RFC3370] MUST be
   supported, and RSA Encryption Scheme - Optimal Asymmetric Encryption
   Padding (RSAES-OAEP) [RFC3560] SHOULD be supported.

   When key agreement is used, Diffie-Hellman (DH) ephemeral-static
   [RFC3370] MUST be supported.  When key agreement is used, Elliptic
   Curve Diffie-Hellman (ECDH) [RFC6090][RFC5753] MAY be supported.

Turner                       Standards Track                    [Page 2]
RFC 6160          Algorithms for Symmetric Key Packages       April 2011

   Regardless of the key management technique choice, implementations
   MUST support AES-128 Key Wrap with Padding [RFC5649] as the content-
   encryption algorithm.  Implementations SHOULD support AES-256 Key
   Wrap with Padding [RFC5649] as the content-encryption algorithm.

   When key agreement is used, the same key-wrap algorithm MUST be used
Show full document text