Re: [httpstreaming] [dispatch] Q-HTTP

"Ali C. Begen (abegen)" <abegen@cisco.com> Tue, 09 November 2010 17:37 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 F19FC3A699F; Tue, 9 Nov 2010 09:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 N7lqXoIeL4jb; Tue, 9 Nov 2010 09:37:20 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id C2CDB3A6A0D; Tue, 9 Nov 2010 09:37:07 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMYV2UyrRN+J/2dsb2JhbACiJHGjPptfgwQIgj4EhFmJDw
X-IronPort-AV: E=Sophos;i="4.59,175,1288569600"; d="scan'208";a="379138223"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 09 Nov 2010 17:37:31 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id oA9HbVX9003161; Tue, 9 Nov 2010 17:37:31 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); Tue, 9 Nov 2010 09:37:31 -0800
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: Tue, 9 Nov 2010 09:37:21 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540DA66D35@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <3349FECF788C984BB34176D70A51782F1067054D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] Q-HTTP
Thread-Index: Act/Ui1FVbaXyq/OQeykYBcapoQUPQAD+ZhwADSSeYA=
References: <3349FECF788C984BB34176D70A51782F106701E2@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com><6750274E2CC345C18EDE9FDDD59F24FA@china.huawei.com> <3349FECF788C984BB34176D70A51782F1067054D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com>, "Qin Wu" <sunseawq@huawei.com>, <dispatch@ietf.org>
X-OriginalArrivalTime: 09 Nov 2010 17:37:31.0404 (UTC) FILETIME=[C94BE4C0:01CB8034]
Cc: httpstreaming <httpstreaming@ietf.org>
Subject: Re: [httpstreaming] [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: Tue, 09 Nov 2010 17:37:25 -0000

I wish your FAQ were something a lot shorter so that it would give us the main points very quickly. You are welcome to join tomorrow's bof session on http streaming but I don't see these two topics particularly relevant to each other (at this stage).

-acbegen

> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of GARCIA ARANDA, JOSE JAVIER (JOSE
> JAVIER)
> Sent: Tuesday, November 09, 2010 12:33 AM
> To: Qin Wu; dispatch@ietf.org
> Cc: httpstreaming
> Subject: Re: [dispatch] Q-HTTP
> 
> Hi Qin and all,
> 
> Now the Q-HTTP draft is accesible at
> 
> http://www.ietf.org/id/draft-aranda-dispatch-qhttp-00.txt
> 
> In addition, i have attached in this email a FAQ document for easier understanding of the protocol. This document clarifies
> the philosophy and shows different alternatives for the implementation
> 
> Regards and thanks
> 
> - Jose javier
> 
> 
> -----Mensaje original-----
> De: Qin Wu [mailto:sunseawq@huawei.com]
> Enviado el: lunes, 08 de noviembre de 2010 15:35
> Para: GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER); dispatch@ietf.org
> CC: httpstreaming
> Asunto: Re: [dispatch] Q-HTTP
> 
> Hi, Joes Javier:
> Your bring a quite interesting draft. We have a Bar BOF on HTTP streaming on Wednesday evening, Emenrald room, which
> aims at  building new area and working out appropriate working scope to offer more efficient transport and better QoE. One
> of key issues we are ready to address is QOE improvement. If you are interested, please join our discussion.
> Also you can track the following link for our meeting agenda, location and time:
> http://www.ietf.org/mail-archive/web/httpstreaming/current/maillist.html
> 
> Regards!
> -Qin
> ----- Original Message -----
> From: "GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com>
> To: <dispatch@ietf.org>
> Sent: Monday, November 08, 2010 4:14 PM
> Subject: [dispatch] Q-HTTP
> 
> 
> 
> Hi experts,
> 
> We are a group of researchers which have written a draft about QoS measurements & reactions. We believe the
> standardization of this topic could benefit internet community in the coming years, for example for virtualization of
> videogames through intenet. We would like to receive comments and some feedback and also oppinions about the target
> area, because we believe that the draft fits into Real-time App and infrastructure Area scope, but currently the draft is in
> "looking for an area" state
> 
>    The draft describes Q-HTTP (Quality HTTP) , which is an application level protocol based on HTTP and SDP associated to a
> new specific uri "httpq://..." intended for carrying out quality negotiation and quality measurement between two parties. The
> final goal of this
> process is to verify that a certain application which depends on bandwidth, latency, jitter parameters, will work under
> current network conditions. Our idea tackles the fact that real-time services (virtualization, on line gaming, video, voice)
> nowadays are increasing and that in an internet (or WAN) environment propagation conditions may change with time for our
> connection; what works for most applications may not work for real-time ones and they should have a standard way of
> negotiating and verifying their requirements. Q-HTTP also provides a mechanism of account/alerting when required
> constraints are not met after the measurement is carried out.
> 
>  Implementation details on the actions to be triggered upon reception/detection of QoS alerts exchanged by the protocol are
> out of scope of this draft, it is application dependant (e.g. increase quality, reduce bit-rate) or even network dependant (e.g.
> change connection's quality profile).
> 
> Comments? Thanks
> 
> - Jose Javier
> 
> 
> 
> --------------------------------------------------------------------------------
> 
> 
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> >