Re: [httpstreaming] Agenda and Slides

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Thu, 11 November 2010 16:33 UTC

Return-Path: <ben@niven-jenkins.co.uk>
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 17A3A3A6A69 for <httpstreaming@core3.amsl.com>; Thu, 11 Nov 2010 08:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.299
X-Spam-Level:
X-Spam-Status: No, score=-104.299 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 d9BR38KHx7Nj for <httpstreaming@core3.amsl.com>; Thu, 11 Nov 2010 08:33:56 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 245143A6822 for <httpstreaming@ietf.org>; Thu, 11 Nov 2010 08:33:56 -0800 (PST)
Received: from [222.128.202.2] (helo=[10.40.76.211]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PGa6S-00033d-VU; Thu, 11 Nov 2010 16:34:25 +0000
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <204E7666-5455-4F51-A865-9043BE3EE84B@cisco.com>
Date: Thu, 11 Nov 2010 16:34:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9E53A09-5AE5-4006-8325-5726FB31AA59@niven-jenkins.co.uk>
References: <AANLkTimsEDGkDVjTj0uVg7g4h+L8JtmM7FJMRM4TvWtv@mail.gmail.com> <01df01cb8089$568d0b30$03a72190$@iridescentnetworks.com> <CEA40436-871D-4748-80F0-1D515E7ED054@netflix.com> <fba7d8a4195b6.195b6fba7d8a4@huawei.com> <20D6E2C9-8E84-42E8-8145-0AF0FE575AFE@cisco.com> <fba2dcf3187a6.187a6fba2dcf3@huawei.com> <204E7666-5455-4F51-A865-9043BE3EE84B@cisco.com>
To: David R Oran <oran@cisco.com>
X-Mailer: Apple Mail (2.1081)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
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: Thu, 11 Nov 2010 16:33:57 -0000

Dave, 

Thank you, the extract of your e-mail that I have included below precisely describes my concerns with the httpstreaming drafts/proposal in a much more eloquent way than I could have expressed it myself.

Ben

On 11 Nov 2010, at 15:44, David R Oran wrote:
> Again, "not sure" isn't good enough. (I'm not sure if I might win the lottery). I don't think we've even gotten to step (1), which is demonstrating with real numbers and real measurements that there is a problem to be solved here. Then we need step (2) which is seeing if the problem has any feasible solutions that don't break other things, or overcomplicate the architecture. Then we can get to step (3) which is to compare the solutions against the baseline of doing nothing. At that point if enough improvement is demonstrated to warrant spending a lot of the IETF's time standardizing something, we can work on the details.
> 
> My fear here is that we'll have a problem statement that boils down to "we need nano fiber transport cables to geosynchronous orbit" at one extreme, or "it sure would be nice if streaming HTTP made better use of scarce radio resources on 4G networks" at the other.
> 
> I don't think the case has yet been made that there's a well-scoped problem for IETF to work on here. I heard somebody proposed that perhaps an IRTF research group ought to be the first step. That might be an alternative worth considering, but only if we can get the right people actually doing work (i.e. researchers with the right skill sets and resources to do the modeling, simulation, and experiments).