review of media type and URI from draft-levin-mmusic-xml-media-control-10.txt
Hi, I would like to ask for review of a media type and new URI for an XML namespace defined in http://tools.ietf.org/wg/mmusic/draft-levin-mmusic-xml-media-control-10.txt. The text from the draft is listed here. 1. Application/media_control+xml media type registration Media Type Name: application subtype name: media_control+xml Required parameters: None Optional parameters: charset See RFC 3023 [4] for a discussion of the charset parameter on XML- derived types. Since this type is used exclusively in SIP, the use of UTF-8 encoding is strongly encouraged. Encoding considerations: 8-bit text Security considerations: Security considerations specific to uses of this type are discussed in RFC xxxx [[Note to RFC editor: replace xxxx with the RFC number of this document when published]]. RFC 1874 [1] and RFC 3023 [4] discuss security issues common to all uses of XML. Interoperability considerations: The use of this media type body is intended to be generally interoperable. No unique considerations have been identified. Published specification: RFC xxxx [[Note to RFC editor: replace xxxx with the RFC number of this document when published]] Applications which use this media type: This media type is used to convey information regarding media control commands and responses between SIP endpoints particularly for allowing a Video Fast Update intra-frame request. Additional information: Magic Number(s): None. File Extension(s): None. Macintosh File Type Code(s): None. Object Identifier(s) or OID(s): None. Intended usage: Limited Use Person to contact for further information: Name: Orit Levin E-Mail: oritl@microsoft.com Other Information/General Comment: None. Author/Change Controller: Orit Levin. 2. URN for XML schema URI: urn:ietf:params:xml:ns:media_control Description: This is the XML namespace URI for XML elements defined by [RFCXXXX] to describe information exchanged between SIP endpoints for media control. It is used in the application/media_control+xml body type. Registrant Contact: Name: Orit Levin E-Mail: oritl@microsoft.com Author/Change Controller: Orit Levin. XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=utf-8"/> <title>Namespace for Tight Media Control</title> </head> <body> <h1>Namespace for Tight Media Control</h1> <h2>application/media_control+xml</h2> <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p> </body> </html> END Thanks Roni Even
* Even, Roni wrote:
1. Application/media_control+xml media type registration
It seems this is quite out of sync with the template in RFC 4288, for example, "Media Type Name" should be "Type name", "Person to contact for further information" should be "Person & email address to contact for further information".
Media Type Name: application subtype name: media_control+xml
Is is really necessary to use a "_" here? I think this would be the first type to use an underscore.
See RFC 3023 [4] for a discussion of the charset parameter on XML- derived types. Since this type is used exclusively in SIP, the use of UTF-8 encoding is strongly encouraged.
This should go into the missing "Restrictions on usage", but why would it be "used exclusively in SIP"?
Encoding considerations: 8-bit text
This should be one of "7bit", "8bit", "binary", "framed", or, preferably a reference to the application/xml encoding considerations in RFC 3023.
Intended usage: Limited Use
This should be uppercased. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Hi, Thanks for the review. See my response inline Thanks Roni Even
-----Original Message----- From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] Sent: Thursday, June 14, 2007 8:21 PM To: Even, Roni Cc: ietf-types@alvestrand.no; Colin Perkins Subject: Re: review of media type and URI from draft-levin-mmusic-xml- media-control-10.txt
* Even, Roni wrote:
1. Application/media_control+xml media type registration
It seems this is quite out of sync with the template in RFC 4288, for example, "Media Type Name" should be "Type name", "Person to contact for further information" should be "Person & email address to contact for further information".
Media Type Name: application subtype name: media_control+xml
[RE:] I will update the draft
Is is really necessary to use a "_" here? I think this would be the first type to use an underscore. [RE:] I prefer to keep it this way since the purpose of the document is an informational RFC that describe current usage. So if we change it will cause interop problems.
See RFC 3023 [4] for a discussion of the charset parameter on XML- derived types. Since this type is used exclusively in SIP, the use of UTF-8 encoding is strongly encouraged.
This should go into the missing "Restrictions on usage", but why would it be "used exclusively in SIP"? [RE:] I will put the restriction in the right section. The reason for the restriction is to discourage usage of this mode in new implementations. It is explained in the text of the draft.
Encoding considerations: 8-bit text
This should be one of "7bit", "8bit", "binary", "framed", or, preferably a reference to the application/xml encoding considerations in RFC 3023. [RE:] OK, I will update to 8bit
Intended usage: Limited Use
This should be uppercased. [RE:] OK. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
participants (2)
-
Bjoern Hoehrmann -
Even, Roni