Re: [httpstreaming] [dispatch] Q-HTTP

Qin Wu <> Mon, 08 November 2010 14:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4ED263A677D; Mon, 8 Nov 2010 06:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.322
X-Spam-Status: No, score=-1.322 tagged_above=-999 required=5 tests=[AWL=-0.827, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S7k0jLih42mM; Mon, 8 Nov 2010 06:34:36 -0800 (PST)
Received: from (unknown []) by (Postfix) with ESMTP id 38B753A6888; Mon, 8 Nov 2010 06:34:36 -0800 (PST)
Received: from (szxga02-in []) by (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <>; Mon, 08 Nov 2010 22:34:47 +0800 (CST)
Received: from ([]) by (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <>; Mon, 08 Nov 2010 22:34:46 +0800 (CST)
Received: from jys1037603 ([]) by (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <>; Mon, 08 Nov 2010 22:34:46 +0800 (CST)
Date: Mon, 08 Nov 2010 22:34:55 +0800
From: Qin Wu <>
Message-id: <>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <>
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 14:34:37 -0000

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