Shepherd writeup
rfc7114-02

1. Summary

Alexey Melnikov is the document shepherd. Sean Turner is the responsible Area Director.

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 document is targeted for Proposed Standard. This is appropriate
as it creates a new IANA registry for one of the parameters defined
in RFC 5751, which is itself a Proposed Standard.

Note that this document is not a product of a WG.


2. Review and Consensus

The document is rather self explanatory. It came out of Barry Leiba's IESG review of another document.
The document had several reviews on the SAAG mailing list.

The document is non controversial and I don't believe it requires extra reviews.


3. Intellectual Property

The author has stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79.


4. Other Points

The IANA Considerations section is well written.

The document creates a new registry with "RFC Required" IANA policy. The document registers values in this registry from 3 earlier RFCs, so this seems appropriate. The document also requires conformance with Section 3.2.2 of [RFC5751] when assigning new values.


ID-nits returns a couple of warnings: 


== Missing Reference: 'RFC-ietf-pkix-est' is mentioned on line 100, but not
     defined

This is a false positive. It is used in an instruction to IANA about removing
an existing pending reference.


== Outdated reference: draft-ietf-pkix-est has been published as RFC 7030

This Informative reference can be updated during publication process.
Back