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

[Ballot comment]
No objection to the publication of the document, but I was under the impression that the following paragraph should be updated.

  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.

Indeed, you don't tell in which registry IANA has to make the changes.
Interestingly, from https://datatracker.ietf.org/doc/draft-leiba-smime-type-registry/history/ IANA understands that we speak about http://www.iana.org/assignments/media-types/application.
So maybe everything is alright then...

IESG/Authors/WG Chairs:

IANA has reviewed draft-leiba-smime-type-registry-01. Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

IANA's reviewer has the following comments/questions:

IANA understands that, upon approval of this document, there are two action which IANA must complete.

First, in the application media types registry located at:

http://www.iana.org/assignments/media-types/application

the current references for media type

application/pkcs7-mime

will be replaced with

[RFC5751][ RFC-to-be ]

Second, a new registry will be created in a new webpage in the category "Multipurpose Internet Mail Extensions (MIME) and Media Types."

The new registry, "Parameter values for the smime-type parameter," will be managed via the RFC Required policy, as defined in RFC 5226.

IANA also notes that the S/MIME Message Specification [RFC5751], Section 3.2.2, specifies guidelines for assigning new smime-type parameter values, and that those guidelines apply to the assignment of values in this registry, which will list [RFC5751] as an additional reference.

The initial registrations in the new registry:

+----------------------+-----------------------------------+
|  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          |
+----------------------+-----------------------------------+

IANA understands that these two actions are the only ones required to upon approval of this document. 

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce , smime@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Creation of a registry for smime-type parameter values) to Proposed Standard


The IESG has received a request from an individual submitter to consider
the following document:
- 'Creation of a registry for smime-type parameter values'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-11-28. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-leiba-smime-type-registry/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-leiba-smime-type-registry/ballot/


No IPR declarations have been submitted directly on this I-D.