wdiff rfc7114.original rfc7114.txt


Security Area
Internet Engineering Task Force (IETF)                          B. Leiba
Internet-Draft
Request for Comments: 7114                           Huawei Technologies
Intended status:
Category: Standards Track                       November 12, 2013
Expires: May 14,                                   January 2014
ISSN: 2070-1721

         Creation of a registry Registry for smime-type parameter values
                   draft-leiba-smime-type-registry-02 Parameter Values

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 these values.  This document creates that the
   registry, registers the current values, and specifies the policies
   for registration of new values.

Status of this This Memo

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

   Internet-Drafts are working documents an Internet Standards Track document.

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

   Internet-Drafts are draft documents valid the IETF community.  It has
   received public review and has been approved for a maximum publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of six months this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained 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.
   http://www.rfc-editor.org/info/rfc7114.

Copyright Notice

   Copyright (c) 2013 2014 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)
   (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
   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 this registry,
   registers the current values that are defined in the three previous previously published
   documents, and specifies the policies for registration of new values.

2.  IANA Considerations

   This document requests two IANA actions.

   IANA is asked to change has changed the reference field for the media type
   "application/pkcs7-mime" "application/
   pkcs7-mime" to "[RFC5751], [RFC-leiba-smime-type-
   registry]", replacing the latter with the RFC number for refer to [RFC5751] and this RFC. document.  This document
   replaces the references to RFC5273 RFC 5273 and RFC7030 with this
   document, as those references RFC 7030, which are no longer
   needed.

   IANA is asked to create has created a new sub-registry under the Multipurpose
   Internet Mail Extensions (MIME) and "MIME Media Types Type Sub-
   Parameter Registries" top-level registry.  The new registry is
   "Parameter values Values for the smime-type parameter",
   the reference for the registry is "[RFC-leiba-smime-type-registry],
   [RFC5751]", Parameter", and the it references
   this document and [RFC5751].  The initial values for the registry are
   as follows:

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

   New values can be registered using the RFC 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.

3.  Security Considerations

   This document is purely administrative, 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. 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. 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:
   EMail: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/