application/pkcs10
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
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@ieca.com Restrictions on usage: none Author: Sean Turner <turners@ieca.com> Intended usage: COMMON Change controller: The IESG <iesg@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
* 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.
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.)
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.
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@ieca.com
The syntax should be "Sean Turner <turners@ieca.com>".
Restrictions on usage: none
Author: Sean Turner <turners@ieca.com>
Intended usage: COMMON
Change controller: The IESG <iesg@ietf.org>
(It is uncommon to cite the IESG's email address here) -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
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@ieca.com
The syntax should be "Sean Turner <turners@ieca.com>".
Fixed.
Restrictions on usage: none
Author: Sean Turner <turners@ieca.com>
Intended usage: COMMON
Change controller: The IESG <iesg@ietf.org>
(It is uncommon to cite the IESG's email address here)
Fixed.
* Sean Turner wrote:
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].
That lacks a verb, perhaps just "Applications that support PKCS#10 certification requests [RFC2986]."? -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
participants (2)
-
Bjoern Hoehrmann -
Sean Turner