Magnus Westerlund | 26 Apr 2012 17:10
Picon
Favicon

Review of text/parameters

The MMUSIC WG is currently doing an WG Last Call on RTSP 2.0. The WG
last call ends on May 16th, 2012.

https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/

This document includes the definition (Appendix F) and registration of
the text/parameters format.

22.16.  Media Type Registration for text/parameters

   Type name:  text

   Subtype name:  parameters

   Required parameters:

   Optional parameters:

   Encoding considerations:

   Security considerations:  This format may carry any type of
      parameters.  Some can have security requirements, like privacy,
      confidentiality or integrity requirements.  The format has no
      built in security protection.  For the usage it was defined the
      transport can be protected between server and client using TLS.
      However, care must be take to consider if also the proxies are
      trusted with the parameters in case hop-by-hop security is used.
      If stored as file in file system the necessary precautions needs
      to be taken in relation to the parameters requirements including
      object security such as S/MIME [RFC5751].
(Continue reading)

Bjoern Hoehrmann | 5 May 2012 21:59
Picon

Re: Review of text/parameters

* Magnus Westerlund wrote:
>https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/

>22.16.  Media Type Registration for text/parameters
>
>   Type name:  text
>
>   Subtype name:  parameters
>
>   Required parameters:
>
>   Optional parameters:

Well, text types usually have a 'charset' parameter, and applications
are known to treat, say, a HTTP response with

  Content-Type: text/parameters;charset=iso-8859-1

As ISO-8859-1 encoded document, even though I gather they are to use
UTF-8 to decode the document. If you don't want a 'charset' parameter,
this problem should be noted in the Security or Interoperability con-
siderations.

>   Encoding considerations:

This field needs a value (probably "8bit" or "binary").
--

-- 
Björn Höhrmann · mailto:bjoern <at> 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/ 
(Continue reading)

Magnus Westerlund | 9 May 2012 09:41
Picon
Favicon

Re: Review of text/parameters

Thanks for the review.

On 2012-05-05 21:59, Bjoern Hoehrmann wrote:
> * Magnus Westerlund wrote:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/
> 
>> 22.16.  Media Type Registration for text/parameters
>>
>>   Type name:  text
>>
>>   Subtype name:  parameters
>>
>>   Required parameters:
>>
>>   Optional parameters:
> 
> Well, text types usually have a 'charset' parameter, and applications
> are known to treat, say, a HTTP response with
> 
>   Content-Type: text/parameters;charset=iso-8859-1
> 
> As ISO-8859-1 encoded document, even though I gather they are to use
> UTF-8 to decode the document. If you don't want a 'charset' parameter,
> this problem should be noted in the Security or Interoperability con-
> siderations.

Yes, you are correct. I guess having the charset being applicable to the
values of the parameters would be very reasonable. The parameters
themselves are in this format restricted to visible 7-bit US-ASCII
characters.
(Continue reading)


Gmane