IETF Logo Mail Archive

Re: [httpstreaming] Current Status and Our Goal

"Ali C. Begen (abegen)" <abegen@cisco.com> Sat, 09 October 2010 16:43 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: httpstreaming@core3.amsl.com
Delivered-To: httpstreaming@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DC7D3A689F for <httpstreaming@core3.amsl.com>; Sat, 9 Oct 2010 09:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level:
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id klazgFq1Nkan for <httpstreaming@core3.amsl.com>; Sat, 9 Oct 2010 09:43:05 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 0A73F3A6874 for <httpstreaming@ietf.org>; Sat, 9 Oct 2010 09:43:05 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHM4sEyrR7Hu/2dsb2JhbACiRHGecpwphUcEhFGIdw
X-IronPort-AV: E=Sophos;i="4.57,308,1283731200"; d="scan'208";a="198313911"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 09 Oct 2010 16:44:12 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o99GiCqu007677; Sat, 9 Oct 2010 16:44:12 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 9 Oct 2010 09:44:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 9 Oct 2010 09:43:40 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540D5BF35F@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <9690AB8A-315E-4730-ABD8-78F4BB3E4CB6@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [httpstreaming] Current Status and Our Goal
Thread-Index: ActmwTgan48Na+ciRYiI95TewO+0dQBD5E6Q
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com><AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com><03f501cb65a1$50699d70$f13cd850$%roni@huawei.com><B1C30D3B-6D5C-46B9-848D-3AE0C8B6058C@csperkins.org> <9690AB8A-315E-4730-ABD8-78F4BB3E4CB6@nokia.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 09 Oct 2010 16:44:12.0533 (UTC) FILETIME=[33D0AA50:01CB67D1]
Cc: httpstreaming@ietf.org
Subject: Re: [httpstreaming] Current Status and Our Goal
X-BeenThere: httpstreaming@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network based HTTP Streaming discussion list <httpstreaming.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/httpstreaming>
List-Post: <mailto:httpstreaming@ietf.org>
List-Help: <mailto:httpstreaming-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2010 16:43:06 -0000

> -----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

v2.8.7 | Report a Bug | By Email