idnits 2.17.00 (12 Aug 2021) /tmp/idnits42599/draft-leiba-smime-type-registry-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 28, 2013) is 3187 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC-ietf-pkix-est' is mentioned on line 102, but not defined ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: draft-ietf-pkix-est has been published as RFC 7030 -- Obsolete informational reference (is this intentional?): RFC 3851 (Obsoleted by RFC 5751) -- Obsolete informational reference (is this intentional?): RFC 5751 (Obsoleted by RFC 8551) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Security Area B. Leiba 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track August 28, 2013 5 Expires: March 01, 2014 7 Creation of a registry for smime-type parameter values 8 draft-leiba-smime-type-registry-00 10 Abstract 12 Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the 13 Content-Type parameter "smime-type". As the list of defined values 14 for that parameter has increased, it has become clear that a registry 15 is needed to document those values. This document creates that 16 registry, registers the current values, and specifies the policies 17 for registration of new values. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 01, 2014. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 4.1. Normative References . . . . . . . . . . . . . . . . . . 3 58 4.2. Informative References . . . . . . . . . . . . . . . . . 3 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 61 1. Introduction 63 Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the 64 Content-Type "application/pkcs7-mime" and the parameter "smime-type", 65 along with four valid values for the parameter [RFC3851]. 66 Certificate Management over CMS (CMC) added two new parameter values 67 [RFC5273]. [RFC5751] replaced RFC 3851 and registered the 68 application/pkcs7-mime media type, but did not create a registry for 69 the smime-type values. 71 When Enrollment over Secure Transport [I-D.ietf-pkix-est] added 72 another parameter value, it became clear that a registry for smime- 73 type parameter values is necessary. Section 2 creates that registry, 74 registers the current values that are defined in the three previous 75 documents, and specifies the policies for registration of new values. 77 2. IANA Considerations 79 This document requests two IANA actions. 81 IANA is asked to change the reference field for the media type 82 "application/pkcs7-mime" to "[RFC5751], [RFC-leiba-smime-type- 83 registry]", replacing the latter with the RFC number for this RFC. 84 This replaces the references to RFC5273 and RFC-ietf-pkix-est with 85 this document, as those references are no longer needed. 87 IANA is asked to create a new sub-registry under the Multipurpose 88 Internet Mail Extensions (MIME) and Media Types top-level registry. 90 The new registry is "Parameter values for the smime-type parameter", 91 the reference for the registry is "[RFC-leiba-smime-type-registry], 92 [RFC5751]", and the initial values for the registry are as follows: 94 +----------------------+-----------------------------------+ 95 | smime-type value | Reference | 96 +----------------------+-----------------------------------+ 97 | certs-only | [RFC5751] Section 3.2.2 | 98 | CMC-Request | [RFC5273] Section 3 | 99 | CMC-Response | [RFC5273] Section 3 | 100 | compressed-data | [RFC5751] Section 3.2.2 | 101 | enveloped-data | [RFC5751] Section 3.2.2 | 102 | server-generated-key | [RFC-ietf-pkix-est] Section 4.4.2 | 103 | signed-data | [RFC5751] Section 3.2.2 | 104 +----------------------+-----------------------------------+ 106 [[RFC Editor: please replace RFC-ietf-pkix-est in the table above 107 with the RFC number assigned to draft-ietf-pkix-est. Note that it is 108 NOT the RFC number for this RFC!]] 110 New values can be registered using the RFC Required policy, as 111 defined in [RFC5226]. The S/MIME Message Specification [RFC5751], 112 Section 3.2.2, specifies guidelines for assigning new smime-type 113 parameter values, and those guidelines apply to the assignment of 114 values in this registry. 116 3. Security Considerations 118 This document is purely administrative, and presents no security 119 issues. 121 4. References 123 4.1. Normative References 125 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 126 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 127 May 2008. 129 4.2. Informative References 131 [I-D.ietf-pkix-est] 132 Pritikin, M., Yee, P., and D. Harkins, "Enrollment over 133 Secure Transport", draft-ietf-pkix-est-09 (work in 134 progress), August 2013. 136 [RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail 137 Extensions (S/MIME) Version 3.1 Message Specification", 138 RFC 3851, July 2004. 140 [RFC5273] Schaad, J. and M. Myers, "Certificate Management over CMS 141 (CMC): Transport Protocols", RFC 5273, June 2008. 143 [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet 144 Mail Extensions (S/MIME) Version 3.2 Message 145 Specification", RFC 5751, January 2010. 147 Author's Address 149 Barry Leiba 150 Huawei Technologies 152 Phone: +1 646 827 0648 153 Email: barryleiba@computer.org 154 URI: http://internetmessagingtechnology.org/