application/pkcs10

[Sean Turner]

Here's the actual template:

   The media type for a PKCS#10 certification request is
    application/pkcs10.

      Type name: application

      Subtype name: pkcs10

      Required parameters: None

      Optional parameters: None

      Encoding considerations:

       This media type carries binary content and needs proper encoding
       for non-8bit clear transports; See Section 2.

      Security considerations:

       Clients use a certification request to request that a
       Certification Authority certify a public key.  The certification
       request is digitally signed.

      Interoperability considerations: See Section 2.

      Published specification: RFC 2986

      Applications which use this media type:

       The content type is used with MIME-compliant transport to
       transfer PKCS#10 certification requests [RFC2986].

      Additional information:

        Magic number(s): None
        File extension(s): .p10
        Macintosh File Type Code(s):

      Person & email address to contact for further information:
        Sean Turner
        turners at ieca.com

      Restrictions on usage: none

      Author:
        Sean Turner <turners at ieca.com>

      Intended usage: COMMON

      Change controller:
            The IESG <iesg at ietf.org>

spt

Sean Turner wrote:
> I'd like to request an expert review for the application/pkcs10 media 
> type registration found in:
> http://tools.ietf.org/html/draft-turner-application-pkcs10-media-type
> 
> The text for formation of the application/pkcs10 media type is adapted
> from RFC 2311.  Only minor changes were made, as can be seen in the
> diffs between version -00 and -01. The changes in -02 were editorial. An 
> IETF LC has been requested for this ID.
> 
> spt
> 
>