rfc-7114

Creation of a Registry for smime-type Parameter Values

B. Leiba

date2014-01 streamIETF wgnon working group statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc7114 doi10.17487/RFC7114

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.

Extracted elements (6)

design-rationale §1

The registry was created because the smime-type parameter values accumulated across multiple documents (RFC 3851, RFC 5273, RFC 5751, RFC 2634, RFC 3854, RFC 7030) without a central registry, making it difficult to track all valid values. RFC 5751 replaced RFC 3851 and registered the media type but did not create a smime-type value registry.

email, registry

interoperability-note §2

IANA updated the reference field for the media type application/pkcs7-mime to refer to RFC 5751 and RFC 7114, replacing previous references to RFC 5273 and RFC 7030 which are no longer needed in that context.

email, registry

normative-requirement §2 REQUIRED

New smime-type parameter values MUST be registered using the Specification Required policy as defined in RFC 5226. Guidelines from RFC 5751 Section 3.2.2 apply to value assignments in this registry.

registry, email

registry §2

IANA created a new sub-registry 'Parameter Values for the smime-type Parameter' under the 'MIME Media Type Sub-Parameter Registries' top-level registry. It references RFC 7114 and RFC 5751, and documents all defined values for the smime-type Content-Type parameter used with application/pkcs7-mime.

registry, email

registry §2

The initial ten values registered in the smime-type parameter registry are: certs-only, CMC-Request, CMC-Response, compressed-data, enveloped-data, enveloped-x400, server-generated-key, signed-data, signed-receipt, and signed-x400, each with a reference to the RFC and section where it was defined.

registry, email

security-consideration §3

This document is purely administrative and presents no security issues.

security, email