W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

Re: iPhone streaming Internet-Draft posted

From: David Singer <singer@apple.com>
Date: Tue, 4 Aug 2009 15:15:16 -0700
Message-Id: <p06240803c69e62b61cd7@[17.202.35.52]>
To: HTTP Working Group <ietf-http-wg@w3.org>, Daniel Stenberg <daniel@haxx.se>
Cc: http-live-streaming-review <http-live-streaming-review@group.apple.com>, Travis Brown <travis@apple.com>, Steve Sinclair <steve.sinclair@apple.com>, Stuart Cheshire <cheshire@apple.com>
On Aug 2, 2009, at 11:53 PM, Daniel Stenberg wrote:
>On Sun, 2 Aug 2009, David Singer wrote:
>>>In fact, I think the proposal would benefit from loosening its 
>>>fixation to HTTP.
>>
>>Hm.  I don't know how to do that while still making it clear that 
>>the only transport the client is required to be able to parse and 
>>use is HTTP.  Do you?
>
>First, it also mentions HTTPS so that makes it two different 
>protocols URI wise at least.
>
>The protocol _could_ say something like HTTP and HTTPS MUST be 
>supported by the client, but that it MAY support other protocols. 
>That would at least not close the door for other protocols to get 
>used at some point without them violating the spec.

The goal of the draft is to produce interoperable implementations. We 
wish to keep it focused on a single transport: HTTP.

>But really, I'm mostly speaking with my HTTP hat on here and this 
>spec has very little to do with HTTP and I think I'd better rest my 
>case about the rest.

We believe that the title live-media-streaming-over-http removes any 
impression that it is an extension of the HTTP standard.


-- 
David Singer
Multimedia Standards, Apple Inc.
Received on Tuesday, 4 August 2009 22:18:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:08 GMT