Request for review of media type from draft-ietf-keyprov-pskc-05.txt

Folks, Please review the following media type registration excerpted from draft-ietf-keyprov-pskc-05.txt, which is currently in IETF Last Call. Thanks, Tim Polk ----------------------- 12.1. Content-type registration for 'application/pskc+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 4288 [RFC4288] and guidelines in RFC 3023 [RFC3023]. MIME media type name: application MIME subtype name: pskc+xml Mandatory parameters: none Optional parameters: charset Indicates the character encoding of enclosed XML. Encoding considerations: Uses XML, which can employ 8-bit characters, depending on the character encoding used. See RFC 3023 [RFC3023], Section 3.2. Security considerations: This content type is designed to carry PSKC protocol payloads. Interoperability considerations: None Published specification: RFCXXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number of this specification.] Applications which use this media type: This MIME type is being used as a symmetric key container format for transport and provisioning of symmetric keys (One Time Password (OTP) shared secrets or symmetric cryptographic keys) to different types of strong authentication devices. As such, it is used for key provisioning systems. Additional information: Magic Number: None File Extension: .pskcxml Macintosh file type code: 'TEXT' Personal and email address for further information: Philip Hoyer, Philip.Hoyer@actividentity.com Intended usage: LIMITED USE Author: This specification is a work item of the IETF KEYPROV working group, with mailing list address <keyprov@ietf.org>. Change controller: The IESG <iesg@ietf.org>

* Polk, William T. wrote:
Please review the following media type registration excerpted from draft-ietf-keyprov-pskc-05.txt, which is currently in IETF Last Call.
12.1. Content-type registration for 'application/pskc+xml'
This specification requests the registration of a new MIME type according to the procedures of RFC 4288 [RFC4288] and guidelines in RFC 3023 [RFC3023].
MIME media type name: application
This is based on an obsolete template, the template from RFC 4288 should be used instead (some field names are different).
MIME subtype name: pskc+xml
Mandatory parameters: none
Optional parameters: charset
Indicates the character encoding of enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit characters, depending on the character encoding used. See RFC 3023 [RFC3023], Section 3.2.
As per RFC 3023, section 7.1: Registrations for new XML-based media types under top-level types other than "text" SHOULD, in specifying the charset parameter and encoding considerations, define them as: "Same as [charset parameter / encoding considerations] of application/xml as specified in RFC 3023."
Security considerations: This content type is designed to carry PSKC protocol payloads.
This should probably include a reference to the security considerations section in the draft.
Additional information:
Magic Number: None
File Extension: .pskcxml
Macintosh file type code: 'TEXT'
Personal and email address for further information: Philip Hoyer, Philip.Hoyer@actividentity.com
The usual rendering here is "Name <email>". -- 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
-
Polk, William T.