Re: [httpstreaming] [dispatch] Q-HTTP

[Henry Sinnreich <[e-mail]>]

+1
Fully agree.

Thanks, Henry


On 11/9/10 4:31 AM, "David Singer" <[e-mail]> wrote:

> There is a bitter lesson I have learned over the years to do with QoS
> reservation.
> 
> It is that there are two ways to solve a real-time bandwidth need.  One is to
> reserve bandwidth, manage QoS and so on;  one gets protocols and systems like
> diffserv, ATM, and so on.  The other is simply to have 'too much' of the
> resource.  Though it feels wrong, the latter often ends up being the cheaper
> and easier solution.  So, for example, voice over IP is getting used quite a
> lot, and to good effect, on the internet today not because we have
> successfully deployed any bandwidth reservation or QoS management protocols
> and systems, but because the available bandwidth is, for the most part,
> greatly in excess of what is needed, and the systems can adapt in real-time to
> what they get (rather than asking for what they want).  The same is true for
> multimedia delivery;  the complexity of RTP + TCP friendliness + QoS
> management is not worth it compared to having adaptable end-systems and
> overall more bandwidth than needed.
> 
> (I worked on real-time scheduling systems as well, and the same applies;  it's
> cheaper to have a processor which is much faster than needed, with a normal
> scheduler, than to have a just-enough processor with a real-time scheduler).
> 
> I know, it 'feels' wrong.
> 
> David Singer
> Multimedia and Software Standards, Apple Inc.
> 
> _______________________________________________
> httpstreaming mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/httpstreaming