Fixing the definition of the smime-type parameter by creating a registry

In the handling of draft-ietf-pkix-est, it came up that there really
ought to be a registry for values of the "smime-type" content-type
parameter.  Sean and I discussed it, and I put together a quick
document (see below) to create the registry and do the magic.  We
should have a brief discussion of it here before Sean AD-sponsors it
and sends it out for last call.

In particular, we decided to propose "RFC Required" for the
registration policy.  Is that the right policy?  Does anyone have
other comments about the registry or the document?

Please, a few reviews and comments will be needed before we can
proceed.  And it' short.  So have at it.

Barry

> From:  <[email protected]>
> Date: Wed, Aug 28, 2013 at 10:38 AM
> Subject: New Version Notification for draft-leiba-smime-type-registry-00.txt
> To: Barry Leiba <[email protected]>
>
> A new version of I-D, draft-leiba-smime-type-registry-00.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Filename:        draft-leiba-smime-type-registry
> Revision:        00
> Title:           Creation of a registry for smime-type parameter values
> Creation date:   2013-08-28
> Group:           Individual Submission
> Number of pages: 4
> URL:
> http://www.ietf.org/internet-drafts/draft-leiba-smime-type-registry-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-leiba-smime-type-registry
> Htmlized:        http://tools.ietf.org/html/draft-leiba-smime-type-registry-00
>
>
> 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.