IETF Logo Mail Archive

Re: [httpstreaming] Agenda and Slides

Mark Watson <watsonm@netflix.com> Wed, 10 November 2010 04:23 UTC

Return-Path: <watsonm@netflix.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 47A4D3A6876 for <httpstreaming@core3.amsl.com>; Tue, 9 Nov 2010 20:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Rbw4gQlqJPVS for <httpstreaming@core3.amsl.com>; Tue, 9 Nov 2010 20:23:49 -0800 (PST)
Received: from mx2.netflix.com (mx2.netflix.com [208.75.77.145]) by core3.amsl.com (Postfix) with ESMTP id 6DFC43A67FD for <httpstreaming@ietf.org>; Tue, 9 Nov 2010 20:23:49 -0800 (PST)
Received: from exchnmc101.netflix.com (exchnmc101.netflix.com [10.64.32.131]) by mx2.netflix.com (8.12.11.20060308/8.12.11) with ESMTP id oAA4OEs0003683; Tue, 9 Nov 2010 20:24:14 -0800
Received: from EXCHMBX103.netflix.com ([fe80::c8e2:ac0e:d177:53c6]) by exchnmc101.netflix.com ([fe80::4894:38ba:ac0c:e4bc%13]) with mapi; Tue, 9 Nov 2010 20:24:08 -0800
From: Mark Watson <watsonm@netflix.com>
To: Kathy McEwen <kathy@iridescentnetworks.com>
Date: Tue, 09 Nov 2010 20:24:07 -0800
Thread-Topic: [httpstreaming] Agenda and Slides
Thread-Index: AcuAjx3Kw+CcYm6sTTKabPhz8SaKXA==
Message-ID: <CEA40436-871D-4748-80F0-1D515E7ED054@netflix.com>
References: <AANLkTimsEDGkDVjTj0uVg7g4h+L8JtmM7FJMRM4TvWtv@mail.gmail.com> <01df01cb8089$568d0b30$03a72190$@iridescentnetworks.com>
In-Reply-To: <01df01cb8089$568d0b30$03a72190$@iridescentnetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: httpstreaming <httpstreaming@ietf.org>
Subject: Re: [httpstreaming] Agenda and Slides
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: Wed, 10 Nov 2010 04:23:50 -0000

Sent from my iPad

On Nov 9, 2010, at 7:42 PM, "Kathy McEwen" <kathy@iridescentnetworks.com> wrote:

> After doing some digging on the various
> protocols (RTMP/http, RTSP, HTML5/http, etc... ), we found that all of them
> that are doing any kind of adaptive rate streaming, but they do not today
> incorporate the messages/control mechanisms to allow for the network to take
> control and adapt the rate of the video.

But it does! It drops packets, causing a congestion response from TCP causing in turn an adaptation by the application. The network is completely in control of the packet delivery rate, which the application knows and adapts to.

This is the baseline, which is so simple and applicable across myriad access technologies. New mechanisms need to justify themselves against this baseline.

...Mark

v2.23.0 | Report a Bug | By Email