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/