Algorithms for Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types
draft-turner-ct-keypackage-receipt-n-error-algs-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-04-18
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        Sean Turner
Internet Draft                                                      IECA
Intended Status: Standards Track                          April 18, 2013
Expires: October 20, 2013                                               

           Algorithms for Cryptographic Message Syntax (CMS)
              Key Package Receipt and Error Content Types
         draft-turner-ct-keypackage-receipt-n-error-algs-00.txt

Abstract

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

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2013 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
 

Turner                  Expires October 20, 2013                [Page 1]
Internet-DraftAlgs for CMS Key Package Rcpt Content Types April 18, 2013

   described in the Simplified BSD License.

1. Introduction

   This document describes the conventions for using several
   cryptographic algorithms with the Cryptographic Message Syntax (CMS)
   key package receipt and error content types [ID.housley-keypackage-
   receipt-n-error].  Specifically, it includes conventions necessary to
   implement SignedData [RFC5652], EnvelopedData [RFC5652],
   EncryptedData [RFC5652], and AuthEnvelopedData [RFC6083].

   This document does not define any new algorithms; instead, it refers
   to previously defined algorithms.  In fact, the algorithm
   requirements in this document are the same as those in
   [RFC5959][RFC6162], [RFC6033][RFC6161], and [RFC6160] with the
   following exceptions: the content-encryption algorithm is AES in CBC
   mode as opposed to AES Key Wrap with MLI and the key-wrap algorithm
   is AES Key Wrap as opposed to AES Key Wrap with Message Length
   Indicator (MLI). The rationale for the difference is that the receipt
   and error content types are not keys therefore AES Key Wrap with MLI
   is not appropriate for the content-encryption algorithm and if an
   implementation isn't using AES Key Wrap with MLI as the content-
   encryption algorithm then there's no need to keep the key-wrap
   algorithm the same as he content encryption algorithm.

   NOTE: [ID.housley-keypackage-receipt-n-error] only requires that the
   key package receipt be signed.

1.1  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "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
 

Turner                  Expires October 20, 2013                [Page 2]
Internet-DraftAlgs for CMS Key Package Rcpt Content Types April 18, 2013

   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
Show full document text