Re: [httpstreaming] Current Status and Our Goal

"Luby, Michael" <luby@qualcomm.com> Thu, 30 September 2010 19:14 UTC

Return-Path: <luby@qualcomm.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 A65B43A6E6A for <httpstreaming@core3.amsl.com>; Thu, 30 Sep 2010 12:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 w6uUlbEVlv43 for <httpstreaming@core3.amsl.com>; Thu, 30 Sep 2010 12:14:20 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id CCDB63A6DCA for <httpstreaming@ietf.org>; Thu, 30 Sep 2010 12:14:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=luby@qualcomm.com; q=dns/txt; s=qcdkim; t=1285874106; x=1317410106; h=from:to:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:user-agent: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20Be n=20Niven-Jenkins=20<ben@niven-jenkins.co.uk>,=20David=20 A.Bryan=0D=0A=09<dbryan@ethernot.org>,=20"httpstreaming@i etf.org"=20<httpstreaming@ietf.org>|Date:=20Thu,=2030=20S ep=202010=2012:15:03=20-0700|Subject:=20Re:=20[httpstream ing]=20Current=20Status=20and=20Our=20Goal|Thread-Topic: =20[httpstreaming]=20Current=20Status=20and=20Our=20Goal |Thread-Index:=20Actg0d+cTP0++OlTTBWyIUxfxdcWVgAAej8h |Message-ID:=20<C8CA2FC7.5093%luby@qualcomm.com> |In-Reply-To:=20<18429BFD-5C5F-4513-85B7-8B91F6D28C97@niv en-jenkins.co.uk>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|user-agent:=20Microsoft-Entourage/ 13.6.0.100712|acceptlanguage:=20en-US|Content-Type:=20tex t/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=yU8EhBFkXhh2vbbB/qeN8JTHF1MYf8dnIF9vscZ5kRo=; b=jto6+2PAYcN0V48uax1WBy1tBeyI60Xk4jLhTswCvNGEW4gyoUhUqt0C jQwo1OJOS04CZnEmtWZiu0Ar5dKO3v93UgcTNXuqlFQMBL4yd6JH+jSRS KFhbR5W21Xq5oYL8qQ5Vop8TvICmhNsj/INGqa72pEkt1EmlLDtxaEqXb k=;
X-IronPort-AV: E=McAfee;i="5400,1158,6122"; a="56265368"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 30 Sep 2010 12:15:06 -0700
X-IronPort-AV: E=Sophos;i="4.57,260,1283756400"; d="scan'208";a="10417059"
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-MD5; 30 Sep 2010 12:15:06 -0700
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 30 Sep 2010 12:15:06 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Thu, 30 Sep 2010 12:15:05 -0700
From: "Luby, Michael" <luby@qualcomm.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, David A.Bryan <dbryan@ethernot.org>, "httpstreaming@ietf.org" <httpstreaming@ietf.org>
Date: Thu, 30 Sep 2010 12:15:03 -0700
Thread-Topic: [httpstreaming] Current Status and Our Goal
Thread-Index: Actg0d+cTP0++OlTTBWyIUxfxdcWVgAAej8h
Message-ID: <C8CA2FC7.5093%luby@qualcomm.com>
In-Reply-To: <18429BFD-5C5F-4513-85B7-8B91F6D28C97@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.6.0.100712
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 30 Sep 2010 19:14:24 -0000

One thing I suggest is that this group seriously study DASH standardization
work in 3GPP and MPEG to understand what these standards do and do not
address, preferably before deciding whether or not to start a group and
definitely before establishing a charter if the decision is to start a
group.


On 9/30/10 10:13 AM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> wrote:

> David, Colleagues,
> 
> On 29 Sep 2010, at 19:59, David A. Bryan wrote:
> 
>> So we have had a number of threads, some about possible work, some
>> about details in the charter, etc. I think it is great to start
>> thinking about a possible charter if this work turns into a WG, and
>> some good reference drafts (thanks to Qin and the folks from Apple for
>> putting these together), but I think another way to look at this might
>> be to at least initially take a step back and see if the folks on the
>> list can take a stab at some more basic questions. I think that was
>> perhaps what Qin was getting at when we started this thread, but it is
>> always good to refocus.
>> 
> 
> Ah! I (wrongly) assumed that the areas of possible work were already known to
> someone and the proposed charter was just an attempt to articulate them.
> 
>> I'll ask two really basic questions to the folks on list, and let's
>> see what the opinions may be, and maybe we can move forward from
>> there. Personally, I think that if we have a bar BoF, focusing just on
>> these two basic questions (ok, one is a compound question, but one is
>> basic!) might be a good way to move forward. I expect we'll have some
>> VERY different answers. Remember that HTTP streaming may mean
>> different things to people, and might even be the wrong term...but
>> these are the things we need to try to figure out.
>> 
>> So the two big questions:
>> 
>> 1) On the topic of this list/HTTP streaming, what do you think is the
>> problem/problems/scenario we should be looking at?
>> 
> 
> I do not feel I am in a position just yet to start making statements about
> what problems I think a HTTP streaming group (if formed) should look at,
> however one area that I think may be interesting to study and that I am not
> aware of other bodies looking at is "chunk hints".
> 
> A lot of streaming media today is delivered via CDNs that operate as more than
> just a dumb (inline) proxy cache.
> 
> HTTP naturally supports the insertion of caches transparently to the end
> points so one could argue that nothing more needs to be done for HTTP
> streaming than for regular HTTP.
> 
> As adaptive bit rate combined with HTTP delivery relies on throughput
> measurements to determine the appropriate bit rate to download for subsequent
> chunks, variation in latency (e.g. the difference between a request for a
> chunk being a cache hit Vs a cache miss) is likely to affect the throughput
> perceived by the client and therefore may cause bit rate switch on a cache
> miss that wouldn't have occurred had the request actually been a cache hit.
> 
> If there was some way to provide a "hint" to the server/cache as to which
> chunk the client is likely to request next then a CDN could elect to retrieve
> that chunk ahead of it actually being requested to keep the response latency
> (or some other factor) more consistent and avoid additional bit rate switches.
> 
> 
> 
>> 2) What other standards body work in this space are you aware of
>> (including IETF work), and how do you think any new work would fit in
>> (or not!) with the answer above?
> 
> None that I am aware of.
> 
> 
>