application/pkcs10
Sean Turner
turners at ieca.com
Thu Apr 22 17:22:37 CEST 2010
Bjoern Hoehrmann wrote:
> * Sean Turner wrote:
>> 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.
>
> This should just say "binary" or "binary; see section 2 for details" or
> some such, see section 4.8 of RFC 4288.
Fixed.
>> Security considerations:
>>
>> Clients use a certification request to request that a
>> Certification Authority certify a public key. The certification
>> request is digitally signed.
>
> (This should probably reference the Security considerations section.)
I'll add this.
>> 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].
>
> This should identify what type of applications use the media type, like,
> 3d modelling applications or word processing software.
I changed it to:
The content type is by applications that support 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
>
> The syntax should be "Sean Turner <turners at ieca.com>".
Fixed.
>> Restrictions on usage: none
>>
>> Author:
>> Sean Turner <turners at ieca.com>
>>
>> Intended usage: COMMON
>>
>> Change controller:
>> The IESG <iesg at ietf.org>
>
> (It is uncommon to cite the IESG's email address here)
Fixed.
More information about the Ietf-types
mailing list