Internet Engineering Task Force (IETF) S. Turner
Request for Comments: 6033 IECA
Category: Standards Track December 2010
ISSN: 2070-1721
Internet Engineering Task Force (IETF) S. Turner
Request for Comments: 6033 IECA
Category: Standards Track December 2010
ISSN: 2070-1721
Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type
加密消息语法（CMS）加密密钥包内容类型的算法
Abstract
摘要
This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS) encrypted key package content type. Specifically, it includes conventions necessary to implement EnvelopedData, EncryptedData, and AuthEnvelopedData.
本文档描述了使用加密消息语法（CMS）加密密钥包内容类型的几种加密算法的约定。具体来说，它包括实现EnvelopedData、EncryptedData和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.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
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/rfc6033.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6033.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS) encrypted key package content type [RFC6032]. Specifically, it includes conventions necessary to implement the following CMS content types: EnvelopedData [RFC5652], EncryptedData [RFC5652], and AuthEnvelopedData [RFC5083].
本文档描述了使用加密消息语法（CMS）加密密钥包内容类型[RFC6032]的几种加密算法的约定。具体而言，它包括实现以下CMS内容类型所需的约定：EnvelopedData[RFC5652]、EncryptedData[RFC5652]和AuthEnvelopedData[RFC5083]。
This document does not define any new algorithms; instead, it refers to previously defined algorithms.
本文件未定义任何新算法；相反，它指的是以前定义的算法。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
EnvelopedData [RFC5652] supports a number of key management techniques. Implementations that claim conformance to this document MUST support the key transport mechanisms and SHOULD support the key agreement mechanisms as defined below. Other techniques MAY be supported.
EnvelopedData[RFC5652]支持多种密钥管理技术。声明符合本文档的实现必须支持关键传输机制，并应支持以下定义的关键协议机制。可以支持其他技术。
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.
使用密钥传输时，必须支持RSA加密[RFC3370]，并且应支持RSA加密方案-最佳非对称加密填充（RSAES-OAEP）[RFC3560]。
When key agreement is used, Ephemeral-Static Diffie-Hellman (DH) [RFC3370] MUST be supported.
使用密钥协议时，必须支持瞬时静态Diffie-Hellman（DH）[RFC3370]。
Since the content type is used to carry a cryptographic key and its attributes, an algorithm that is traditionally used to encrypt one key with another is employed. 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.
由于内容类型用于携带加密密钥及其属性，因此采用了传统上用于用一个密钥加密另一个密钥的算法。无论选择何种密钥管理技术，实现都必须支持AES-128密钥封装和填充[RFC5649]作为内容加密算法。实现应支持使用填充[RFC5649]作为内容加密算法的AES-256密钥换行。
When key agreement is used, a key wrap algorithm is also specified to wrap the content-encryption key. If the content-encryption algorithm is AES-128 Key Wrap with Padding, then the key wrap algorithm MUST be AES-128 Key Wrap with Padding [RFC5649]. If the content-encryption algorithm is AES-256 Key Wrap with Padding, then the key wrap algorithm MUST be AES-256 Key Wrap with Padding [RFC5649].
使用密钥协议时，还指定密钥包装算法来包装内容加密密钥。如果内容加密算法是带填充的AES-128密钥包裹，则密钥包裹算法必须是带填充的AES-128密钥包裹[RFC5649]。如果内容加密算法是带填充的AES-256密钥包裹，则密钥包裹算法必须是带填充的AES-256密钥包裹[RFC5649]。
EncryptedData [RFC5652] requires that keys be managed by other means; therefore, the only algorithm specified is the content-encryption algorithm. Since the content type is used to carry a cryptographic key and its attributes, an algorithm that is traditionally used to encrypt one key with another is employed. Implementations MUST support AES-128 Key Wrap with Padding [RFC5649]. Implementations SHOULD support AES-256 Key Wrap with Padding [RFC5649].
EncryptedData[RFC5652]要求通过其他方式管理密钥；因此，指定的唯一算法是内容加密算法。由于内容类型用于携带加密密钥及其属性，因此采用了传统上用于用一个密钥加密另一个密钥的算法。实现必须支持带填充的AES-128密钥换行[RFC5649]。实现应支持带填充的AES-256密钥换行[RFC5649]。
AuthEnvelopedData [RFC5083], like EnvelopedData, supports a number of key management techniques. The key management requirements for AuthEnvelopedData are the same as for EnvelopedData. The difference is the content-encryption algorithm. Implementations MUST support 128-bit AES-Galois/Counter Mode (AES-GCM) [RFC5084] and SHOULD support 256-bit AES-GCM [RFC5084]. Implementations MAY also support AES-Counter with CBC-MAC (AES-CCM) [RFC5084].
AuthEnvelopedData[RFC5083]与EnvelopedData一样，支持多种密钥管理技术。AuthEnvelopedData的关键管理要求与EnvelopedData相同。区别在于内容加密算法。实现必须支持128位AES伽罗瓦/计数器模式（AES-GCM）[RFC5084]，并应支持256位AES-GCM[RFC5084]。实现还可以支持带有CBC-MAC（AES-CCM）[RFC5084]的AES计数器。
Implementations of SignedData [RFC5652] MUST support the signature scheme RSA [RFC3370] [RFC5754] and SHOULD support the signature schemes RSA Probabilistic Signature Scheme (RSASSA-PSS) [RFC4056] and Digital Signature Algorithm (DSA) [RFC3370] [RFC5754]. Additionally, implementations MUST support in concert with these signature schemes the hash function SHA-256 [RFC5754] and it SHOULD support the hash function SHA-1 [RFC3370].
SignedData[RFC5652]的实现必须支持签名方案RSA[RFC3370][RFC5754]，并应支持签名方案RSA概率签名方案（RSASSA-PSS）[RFC4056]和数字签名算法（DSA）[RFC3370][RFC5754]。此外，实现必须与这些签名方案一起支持哈希函数SHA-256[RFC5754]，并且它应该支持哈希函数SHA-1[RFC3370]。
The easiest way to implement SignedData, EnvelopedData, and AuthEnvelopedData is with public key certificates [RFC5280]. If an implementation supports RSA, RSAES-OAEP, DH, RSASSA-PSS, or DSA, then it MUST support key lengths from 1024 bits to 2048 bits, inclusive.
实现SignedData、EnvelopedData和AuthEnvelopedData的最简单方法是使用公钥证书[RFC5280]。如果实现支持RSA、RSAES-OAEP、DH、RSASSA-PSS或DSA，则它必须支持1024位到2048位（包括1024位）的密钥长度。
The security considerations from [RFC3370], [RFC3560], [RFC4056], [RFC5083], [RFC5084], [RFC5649], [RFC5652], [RFC5754], and [RFC6032] apply.
[RFC3370]、[RFC3560]、[RFC4056]、[RFC5083]、[RFC5084]、[RFC5649]、[RFC5652]、[RFC5754]和[RFC6032]中的安全注意事项适用。
The choice of content-encryption algorithms for this document was based on [RFC5649]: "In the design of some high assurance cryptographic modules, it is desirable to segregate cryptographic keying material from other data. The use of a specific cryptographic mechanism solely for the protection of cryptographic keying material
本文件内容加密算法的选择基于[RFC5649]：“在一些高保证加密模块的设计中，需要将加密密钥材料与其他数据分离。使用特定加密机制仅用于保护加密密钥材料
can assist in this goal". Unfortunately, there is no AES-GCM or AES-CCM mode that provides the same properties. If an AES-GCM and AES-CCM mode that provides the same properties is defined, then this document will be updated to adopt that algorithm.
不幸的是，没有提供相同属性的AES-GCM或AES-CCM模式。如果定义了提供相同属性的AES-GCM和AES-CCM模式，则将更新本文档以采用该算法。
[SP800-57] provides comparable bits of security for some algorithms and key sizes. [SP800-57] also provides time frames during which certain numbers of bits of security are appropriate, and some environments may find these time frames useful.
[SP800-57]为某些算法和密钥大小提供了可比的安全性。[SP800-57]还提供了一定数量的安全位适当的时间框架，一些环境可能会发现这些时间框架很有用。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3370] Housley, R., "Cryptographic Message Syntax (CMS) Algorithms", RFC 3370, August 2002.
[RFC3370]Housley，R.，“加密消息语法（CMS）算法”，RFC3370，2002年8月。
[RFC3560] Housley, R., "Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)", RFC 3560, July 2003.
[RFC3560]Housley，R.，“在加密消息语法（CMS）中使用RSAES-OAEP密钥传输算法”，RFC 3560，2003年7月。
[RFC4056] Schaad, J., "Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)", RFC 4056, June 2005.
[RFC4056]Schaad，J.，“在加密消息语法（CMS）中使用RSASSA-PSS签名算法”，RFC 4056，2005年6月。
[RFC5083] Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, November 2007.
[RFC5083]Housley，R.，“加密消息语法（CMS）认证的信封数据内容类型”，RFC 5083，2007年11月。
[RFC5084] Housley, R., "Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)", RFC 5084, November 2007.
[RFC5084]Housley，R.，“在加密消息语法（CMS）中使用AES-CCM和AES-GCM认证加密”，RFC 5084，2007年11月。
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, May 2008.
[RFC5280]Cooper，D.，Santesson，S.，Farrell，S.，Boeyen，S.，Housley，R.，和W.Polk，“Internet X.509公钥基础设施证书和证书撤销列表（CRL）配置文件”，RFC 52802008年5月。
[RFC5649] Housley, R. and M. Dworkin, "Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm", RFC 5649, September 2009.
[RFC5649]Housley，R.和M.Dworkin，“带填充算法的高级加密标准（AES）密钥封装”，RFC 5649，2009年9月。
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, September 2009.
[RFC5652]Housley，R.，“加密消息语法（CMS）”，STD 70，RFC 56522009年9月。
[RFC5754] Turner, S., "Using SHA2 Algorithms with Cryptographic Message Syntax", RFC 5754, January 2010.
[RFC5754]Turner，S.，“将SHA2算法与加密消息语法结合使用”，RFC 5754，2010年1月。
[RFC6032] Turner, S. and R. Housley, "Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type", RFC 6032, December 2010.
[RFC6032]Turner，S.和R.Housley，“加密消息语法（CMS）加密密钥包内容类型”，RFC 60322010年12月。
[SP800-57] National Institute of Standards and Technology (NIST), Special Publication 800-57: Recommendation for Key Management - Part 1 (Revised), March 2007.
[SP800-57]国家标准与技术研究所（NIST），特别出版物800-57：关键管理建议-第1部分（修订版），2007年3月。
Author's Address
作者地址
Sean Turner IECA, Inc. 3057 Nutley Street, Suite 106 Fairfax, VA 22031 USA
Sean Turner IECA，Inc.美国弗吉尼亚州费尔法克斯市努特利街3057号106室，邮编22031
EMail: turners@ieca.com
EMail: turners@ieca.com