Internet Engineering Task Force (IETF)                          B. Leiba
Request for Comments: 7114                           Huawei Technologies
Category: Standards Track                                   January 2014
ISSN: 2070-1721
        
Internet Engineering Task Force (IETF)                          B. Leiba
Request for Comments: 7114                           Huawei Technologies
Category: Standards Track                                   January 2014
ISSN: 2070-1721

Creation of a Registry for smime-type Parameter Values

为smime类型参数值创建注册表

Abstract

摘要

Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the Content-Type parameter "smime-type". As the list of defined values for that parameter has increased, it has become clear that a registry is needed to document these values. This document creates the registry, registers the current values, and specifies the policies for registration of new values.

安全/多用途Internet邮件扩展（S/MIME）定义了内容类型参数“smime类型”。随着该参数定义值列表的增加，显然需要一个注册表来记录这些值。本文档创建注册表，注册当前值，并指定注册新值的策略。

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/rfc7114.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7114.

Copyright Notice

版权公告

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

版权所有（c）2014 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许可证中所述的无担保。

Table of Contents

目录 

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   4
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   4
1. Introduction
1. 介绍

Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the Content-Type "application/pkcs7-mime" and the parameter "smime-type", along with four valid values for the parameter [RFC3851]. Certificate Management over CMS (CMC) added two new parameter values [RFC5273]. [RFC5751] replaced RFC 3851 and registered the application/pkcs7-mime media type, but did not create a registry for the smime-type values.

安全/多用途Internet邮件扩展（S/MIME）定义了内容类型“application/pkcs7 MIME”和参数“smime Type”，以及参数[RFC3851]的四个有效值。CMS证书管理（CMC）添加了两个新参数值[RFC5273]。[RFC5751]替换了RFC 3851并注册了应用程序/pkcs7 mime媒体类型，但未为smime类型值创建注册表。

Enhanced Security Services for S/MIME [RFC2634] and Securing X.400 Content with S/MIME [RFC3854] also add smime-type values.

增强的S/MIME[RFC2634]安全服务和使用S/MIME[RFC3854]保护X.400内容的安全性也添加了smime类型值。

When Enrollment over Secure Transport [RFC7030] added another parameter value, it became clear that a registry for smime-type parameter values is necessary. Section 2 creates this registry, registers the current values that are defined in previously published documents, and specifies the policies for registration of new values.

当通过安全传输注册[RFC7030]添加另一个参数值时，很明显smime类型参数值的注册表是必要的。第2节创建此注册表，注册以前发布的文档中定义的当前值，并指定注册新值的策略。

2. IANA Considerations
2. IANA考虑

IANA has changed the reference field for the media type application/ pkcs7-mime to refer to [RFC5751] and this document. This document replaces the references to RFC 5273 and RFC 7030, which are no longer needed.

IANA已将媒体类型应用程序/pkcs7 mime的参考字段更改为参考[RFC5751]和本文档。本文件取代不再需要的对RFC 5273和RFC 7030的引用。

IANA has created a new sub-registry under the "MIME Media Type Sub-Parameter Registries" top-level registry. The new registry is "Parameter Values for the smime-type Parameter", and it references this document and [RFC5751]. The initial values for the registry are as follows:

IANA在“MIME媒体类型子参数注册表”顶级注册表下创建了一个新的子注册表。新的注册表是“smime类型参数的参数值”，它引用了本文档和[RFC5751]。注册表的初始值如下所示： 

      +----------------------+-----------------------------------+
      |  smime-type value    |  Reference                        |
      +----------------------+-----------------------------------+
      | certs-only           | [RFC5751], Section 3.2.2          |
      | CMC-Request          | [RFC5273], Section 3              |
      | CMC-Response         | [RFC5273], Section 3              |
      | compressed-data      | [RFC5751], Section 3.2.2          |
      | enveloped-data       | [RFC5751], Section 3.2.2          |
      | enveloped-x400       | [RFC3854], Section 3.3.1          |
      | server-generated-key | [RFC7030], Section 4.4.2          |
      | signed-data          | [RFC5751], Section 3.2.2          |
      | signed-receipt       | [RFC2634], Section 2.4, bullet 10 |
      | signed-x400          | [RFC3854], Section 3.2.1          |
      +----------------------+-----------------------------------+
        
      +----------------------+-----------------------------------+
      |  smime-type value    |  Reference                        |
      +----------------------+-----------------------------------+
      | certs-only           | [RFC5751], Section 3.2.2          |
      | CMC-Request          | [RFC5273], Section 3              |
      | CMC-Response         | [RFC5273], Section 3              |
      | compressed-data      | [RFC5751], Section 3.2.2          |
      | enveloped-data       | [RFC5751], Section 3.2.2          |
      | enveloped-x400       | [RFC3854], Section 3.3.1          |
      | server-generated-key | [RFC7030], Section 4.4.2          |
      | signed-data          | [RFC5751], Section 3.2.2          |
      | signed-receipt       | [RFC2634], Section 2.4, bullet 10 |
      | signed-x400          | [RFC3854], Section 3.2.1          |
      +----------------------+-----------------------------------+

New values can be registered using the Specification Required policy, as defined in [RFC5226]. The S/MIME Message Specification [RFC5751], Section 3.2.2, specifies guidelines for assigning new smime-type parameter values, and those guidelines apply to the assignment of values in this registry.

可以使用[RFC5226]中定义的规范要求策略注册新值。S/MIME消息规范[RFC5751]第3.2.2节规定了分配新smime类型参数值的准则，这些准则适用于此注册表中的值分配。

3. Security Considerations
3. 安全考虑

This document is purely administrative and presents no security issues.

本文档纯粹是管理性的，不存在任何安全问题。

4. References
4. 工具书类
4.1. Normative References
4.1. 规范性引用文件

[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.

[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。

[RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification", RFC 5751, January 2010.

[RFC5751]Ramsdell，B.和S.Turner，“安全/多用途Internet邮件扩展（S/MIME）版本3.2消息规范”，RFC 57512010年1月。

4.2. Informative References
4.2. 资料性引用

[RFC2634] Hoffman, P., "Enhanced Security Services for S/MIME", RFC 2634, June 1999.

[RFC2634]Hoffman，P.，“S/MIME的增强安全服务”，RFC 2634，1999年6月。

[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification", RFC 3851, July 2004.

[RFC3851]Ramsdell，B.，“安全/多用途Internet邮件扩展（S/MIME）版本3.1消息规范”，RFC 38512004年7月。

[RFC3854] Hoffman, P., Bonatti, C., and A. Eggen, "Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)", RFC 3854, July 2004.

[RFC3854]Hoffman，P.，Bonatti，C.，和A.Eggen，“使用安全/多用途Internet邮件扩展（S/MIME）保护X.400内容”，RFC 3854，2004年7月。

[RFC5273] Schaad, J. and M. Myers, "Certificate Management over CMS (CMC): Transport Protocols", RFC 5273, June 2008.

[RFC5273]Schaad，J.和M.Myers，“CMS上的证书管理（CMC）：传输协议”，RFC 5273，2008年6月。

[RFC7030] Pritikin, M., Yee, P., and D. Harkins, "Enrollment over Secure Transport", RFC 7030, October 2013.

[RFC7030]Pritikin，M.，Yee，P.，和D.Harkins，“通过安全传输注册”，RFC 7030，2013年10月。

Author's Address

作者地址

Barry Leiba Huawei Technologies

巴里·雷巴华为技术有限公司 

   Phone: +1 646 827 0648
   EMail: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/
        
   Phone: +1 646 827 0648
   EMail: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/