Re: [httpstreaming] Current Status and Our Goal

How about  we say:
To provide better transport to satisfy real time streaming requirements.
----- Original Message ----- 
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Ye-Kui Wang" <yekuiwang@huawei.com>om>; "Lars Eggert" <lars.eggert@nokia.com>om>; "Colin Perkins" <csp@csperkins.org>
Cc: <httpstreaming@ietf.org>
Sent: Sunday, October 10, 2010 8:04 AM
Subject: Re: [httpstreaming] Current Status and Our Goal

> -----Original Message-----
> From: Ye-Kui Wang [mailto:yekuiwang@huawei.com]
> Sent: Sunday, October 10, 2010 7:28 AM
> To: Ali C. Begen (abegen); 'Lars Eggert'; 'Colin Perkins'
> Cc: httpstreaming@ietf.org
> Subject: RE: [httpstreaming] Current Status and Our Goal
> 
> 
> > I imagine the only work the IETF should do (if we decide to)
> > is the transport and HTTP-layer optimization for better
> > streaming performance.

Actually for one, I don’t like the word "optimization" myself which is not very meaningful here. So, I should rather say "any marginal improvement is welcome".

-acbegen

> I second, as one who has been heavily involved HTTP streaming
> standardization in 3GPP, MPEG and OIPF.
> 
> BR, YK
> 
> > -----Original Message-----
> > From: httpstreaming-bounces@ietf.org
> > [mailto:httpstreaming-bounces@ietf.org] On Behalf Of Ali C.
> > Begen (abegen)
> > Sent: Saturday, October 09, 2010 12:44 PM
> > To: Lars Eggert; Colin Perkins
> > Cc: httpstreaming@ietf.org
> > Subject: Re: [httpstreaming] Current Status and Our Goal
> >
> >
> >
> > > -----Original Message-----
> > > From: httpstreaming-bounces@ietf.org
> > > [mailto:httpstreaming-bounces@ietf.org] On Behalf Of Lars Eggert
> > > Sent: Friday, October 08, 2010 4:17 PM
> > > To: Colin Perkins
> > > Cc: httpstreaming@ietf.org
> > > Subject: Re: [httpstreaming] Current Status and Our Goal
> > >
> > > On 2010-10-7, at 14:16, Colin Perkins wrote:
> > > > There are clearly some issues to consider here. What seems to be
> > > > missing from the discussion to me though, is some
> > identification of
> > > > the concrete problems. What protocol pieces do we need,
> > but not have?
> > > > What protocols are problematic, and need enhancement? Is there
> > > > protocol work to do in IETF, or should we be documenting best
> > > > current practices for using the existing protocols and/or
> > relying on
> > > > other bodies to fill the gaps?
> > > >
> > > > The draft-wu-http-streaming-optimization-ps is a good
> > start at such
> > > > an analysis, but doesn't go deep enough to let us decide
> > what work
> > > > IETF should do.
> > >
> > > +1
> > >
> > > The key question really is "what do you think the IETF needs to do?"
> >
> > I imagine the only work the IETF should do (if we decide to)
> > is the transport and HTTP-layer optimization for better
> > streaming performance.
> >
> > -acbegen
> >
> > > Lars
> > _______________________________________________
> > httpstreaming mailing list
> > httpstreaming@ietf.org
> > https://www.ietf.org/mailman/listinfo/httpstreaming
> >
> 

_______________________________________________
httpstreaming mailing list
httpstreaming@ietf.org
https://www.ietf.org/mailman/listinfo/httpstreaming