Registration of media type application/vnd.apple.mpegURL

[Roger Pantos]

It's a coincidence for the most part, unless the original author had  
m3u playlists in mind when text/uri-list was conceived.

Note that vnd.apple.mpegurl goes beyond what  uri-list specifies by  
defining tags that relate specifically to media URIs.


Roger.

On Jul 2, 2009, at 6:58 PM, Jan Algermissen wrote:

> Roger,
>
> Out of curiosity..
>
> is the compatibility with text/uri-list a purpose or a coincidence?
>
> Jan
>
>
>
>
> On Jun 26, 2009, at 1:36 PM, Roger Pantos wrote:
>
>>
>> Hello there. I'm planning to submit this registration to IANA soon,  
>> but per RFC 4288 I'm sending it here first to solicit initial  
>> feedback. Thanks.
>>
>>
>> Type name:  application
>>
>> Subtype name:  vnd.apple.mpegURL
>>
>> Required parameters:  (none)
>>
>> Optional parameters:  (none)
>>
>> Encoding considerations:  Encoded as text, either ASCII or UTF-8.   
>> UTF-8 is recommended.
>>
>> Security considerations:
>>
>> - As with any text format, parsers must guard against buffer  
>> overflow attacks
>>
>> - Active content:
>> - Several elements of this format are URIs, which clients will use  
>> to make network requests of arbitrary entities
>> - Clients should range-check responses to prevent buffer overflows
>> - Clients should load resources identified by URI lazily (specified  
>> by protocol) to reduce server DoS
>> - See also Security Considerations in RFC 3986
>>
>> - Privacy:
>> - URIs are typically http. Implementations may send cookie data  
>> with http requests, which could include user data.
>> - Implementations must follow cookie restriction & expiry rules  
>> specified by RFC 2965.
>>
>> - Compression: this media type does not employ compression.
>>
>> - The format includes the specification of encryption keys, by URI.  
>> The delivery of these keys should be secure, but it is up to the  
>> distributor of the media to ensure that it is, e.g. by using HTTP  
>> over TLS in conjunction with a secure realm or a session cookie.
>>
>> Interoperability considerations:
>>
>> - No byte-ordering issues, since files are encoded as ASCII or  
>> UTF-8 text
>> - Applications may encounter unrecognized tags. These should be  
>> ignored.
>>
>> Published specification:  http://tools.ietf.org/html/draft-pantos-http-live-streaming
>>
>> Applications that use this media type:
>> - iPhone media player (OS 3.0)
>> - QuickTime Player in Mac OS X (Snow Leopard)
>>
>> Additional information:
>>
>> Magic number(s):  #EXTM3U
>> File extension(s):  m3u, m3u8
>> Macintosh file type code(s):  none
>>
>> Person & email address to contact for further information:  David  
>> Singer, singer at .apple.com
>>
>> Intended usage:  LIMITED USE
>>
>> Restrictions on usage:  (none)
>>
>> Author:  Roger Pantos
>>
>> Change controller:  David Singer
>>
>>
>>
>> Roger.
>