Security Area B. Leiba Internet-Draft Huawei Technologies Intended status: Standards Track November 12, 2013 Expires: May 14, 2014 Creation of a registry for smime-type parameter values draft-leiba-smime-type-registry-02 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 those values. This document creates that registry, registers the current values, and specifies the policies for registration of new values. 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." This Internet-Draft will expire on May 14, 2014. 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 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 Leiba Expires May 14, 2014 [Page 1] Internet-Draft Registry for smime-type values November 2013 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Normative References . . . . . . . . . . . . . . . . . . . 3 4.2. Informative References . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction 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. Enhanced Security Services for S/MIME [RFC2634] and Securing X.400 Content with S/MIME [RFC3854] also add smime-type values. 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 that registry, registers the current values that are defined in the three previous documents, and specifies the policies for registration of new values. 2. IANA Considerations This document requests two IANA actions. IANA is asked to change the reference field for the media type "application/pkcs7-mime" to "[RFC5751], [RFC-leiba-smime-type- registry]", replacing the latter with the RFC number for this RFC. This replaces the references to RFC5273 and RFC7030 with this document, as those references are no longer needed. IANA is asked to create a new sub-registry under the Multipurpose Internet Mail Extensions (MIME) and Media Types top-level registry. The new registry is "Parameter values for the smime-type parameter", the reference for the registry is "[RFC-leiba-smime-type-registry], [RFC5751]", and the initial values for the registry are as follows: +----------------------+-----------------------------------+ | 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 | +----------------------+-----------------------------------+ Leiba Expires May 14, 2014 [Page 2] Internet-Draft Registry for smime-type values November 2013 New values can be registered using the RFC 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. 3. Security Considerations This document is purely administrative, and presents no security issues. 4. References 4.1. Normative References [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification", RFC 5751, January 2010. 4.2. Informative References [RFC2634] Hoffman, P., "Enhanced Security Services for S/MIME", RFC 2634, June 1999. [RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification", RFC 3851, July 2004. [RFC3854] Hoffman, P., Bonatti, C. and A. Eggen, "Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)", RFC 3854, July 2004. [RFC5273] Schaad, J. and M. Myers, "Certificate Management over CMS (CMC): Transport Protocols", RFC 5273, June 2008. [RFC7030] Pritikin, M., Yee, P. and D. Harkins, "Enrollment over Secure Transport", RFC 7030, October 2013. Author's Address Barry Leiba Huawei Technologies Phone: +1 646 827 0648 Email: barryleiba@computer.org URI: http://internetmessagingtechnology.org/ Leiba Expires May 14, 2014 [Page 3]