Re: [httpstreaming] [dispatch] Q-HTTP

"GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <> Mon, 08 November 2010 16:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1B69628C0DE; Mon, 8 Nov 2010 08:33:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fl2nnMGF1pCz; Mon, 8 Nov 2010 08:33:29 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 843763A692F; Mon, 8 Nov 2010 08:33:27 -0800 (PST)
Received: from ( []) by (8.14.3/8.14.3/ICT) with ESMTP id oA8GXbCO026317 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Nov 2010 17:33:37 +0100
Received: from ([]) by ([]) with mapi; Mon, 8 Nov 2010 17:33:37 +0100
To: Qin Wu <>, "" <>
Date: Mon, 8 Nov 2010 17:33:20 +0100
Thread-Topic: [dispatch] Q-HTTP
Thread-Index: Act/Ui1FVbaXyq/OQeykYBcapoQUPQAD+Zhw
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: es-ES
X-MS-Has-Attach: yes
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_3349FECF788C984BB34176D70A51782F1067054DFRMRSSXCHMBSB3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on
Cc: httpstreaming <>
Subject: Re: [httpstreaming] [dispatch] Q-HTTP
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network based HTTP Streaming discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Nov 2010 16:33:30 -0000

Hi Qin and all,

Now the Q-HTTP draft is accesible at

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 [] 
Enviado el: lunes, 08 de noviembre de 2010 15:35
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:

----- Original Message -----
To: <>
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