Re: [httpstreaming] [conex] [dispatch] Q-HTTP

"Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com> Wed, 10 November 2010 13:26 UTC

Return-Path: <tom.van_caenegem@alcatel-lucent.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 C5F8C3A68ED; Wed, 10 Nov 2010 05:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.537
X-Spam-Level:
X-Spam-Status: No, score=-5.537 tagged_above=-999 required=5 tests=[AWL=0.712, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 Uim0FUsHwzG6; Wed, 10 Nov 2010 05:26:56 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 772F83A6909; Wed, 10 Nov 2010 05:26:56 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id oAADRGXe006639 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 10 Nov 2010 14:27:17 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 10 Nov 2010 14:27:16 +0100
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: David Singer <singer@apple.com>, Roland Bless <roland.bless@kit.edu>
Date: Wed, 10 Nov 2010 14:27:15 +0100
Thread-Topic: [httpstreaming] [conex] [dispatch] Q-HTTP
Thread-Index: AcuA15ARlYYFRIX4QHy509JeQKp3VgAASpwg
Message-ID: <EC3FD58E75D43A4F8807FDE07491754616613C62@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <3349FECF788C984BB34176D70A51782F106701E2@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <6750274E2CC345C18EDE9FDDD59F24FA@china.huawei.com> <3349FECF788C984BB34176D70A51782F1067054D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <DBB1DC060375D147AC43F310AD987DCC180E504600@ESESSCMS0366.eemea.ericsson.se> <3349FECF788C984BB34176D70A51782F168772C1@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <EAA2CFBF-9434-4E52-A586-7AE5F665A9DF@apple.com> <4CDA53B2.9000209@kit.edu> <57CDBEC2-8424-4A16-95B5-2006FC9C4F9C@apple.com>
In-Reply-To: <57CDBEC2-8424-4A16-95B5-2006FC9C4F9C@apple.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Ingemar, httpstreaming <httpstreaming@ietf.org>, "conex@ietf.org" <conex@ietf.org>, Johansson S <ingemar.s.johansson@ericsson.com>, "GARCIA ARANDA, JOSE JAVIER \(JOSE JAVIER\)" <jose_javier.garcia_aranda@alcatel-lucent.com>
Subject: Re: [httpstreaming] [conex] [dispatch] Q-HTTP
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 13:26:57 -0000

Hi David,

In the end, SPs are driven by costs and revenus. Does option (a) represent the same cost as (b)? (I do not know..)

-How will the investment be paid  back in case of (a).. Raising subscription fees for everyone? Will that not lead to enhanced subscriber churn? Is net revenu then positive for the SP?

-How will the investment be paid back in case of (b)... Those subscribers that want 1st class service will be willing to pay extra for it. Other that won't, will probably sense they get a smaller piece of the bandwidth pie, and may decide to change SP. What is net revenu here?

My impression is that it is not immediately clear whether (a) or (b) or any mix of (a) and (b) is the best strategy for a SP.

Regards
Tom 

-----Original Message-----
From: httpstreaming-bounces@ietf.org [mailto:httpstreaming-bounces@ietf.org] On Behalf Of David Singer
Sent: woensdag 10 november 2010 14:02
To: Roland Bless
Cc: dispatch@ietf.org; httpstreaming; conex@ietf.org; Ingemar Johansson S; GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
Subject: Re: [httpstreaming] [conex] [dispatch] Q-HTTP

Hi Roland,

On Nov 10, 2010, at 9:11 , Roland Bless wrote:

> Hi David,
> 
> On 09.11.2010 11:31, David Singer wrote:
> 
>> It is that there are two ways to solve a real-time bandwidth need.
>> One is to reserve bandwidth, manage QoS and so on;  one gets 
>> protocols and systems like diffserv, ATM, and so on.  The other is 
>> simply to have 'too much' of the resource.  Though it feels wrong,
> 
> QoS mechanisms are usually only necessary if you've got some kind of 
> resource shortage. They try to manage the resource scarcity in some 
> way then. So having "too much of a resource" seems to imply that we 
> actually don't need any QoS support.
> 

I think this raises a question that happens at a service provider.  Imagine I observe that my networks are getting more busy, and decide to invest some more in them.  Do I (a) deploy a QoS management infrastructure or (b) use those same funds to pay for capacity upgrades?  I think that most operators end up choosing (b) as it 'lifts all boats', whereas they are not confident that anyone will use (a) in the near future, and they know it won't benefit everyone (and in fact, will be to the detriment of some users who don't use it, and were previously doing 'fair competition' for bandwidth and now are 'second class' behind those with reserved bandwidth).

David Singer
Multimedia and Software Standards, Apple Inc.

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