Re: [httpstreaming] [dispatch] Q-HTTP

"GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <> Tue, 09 November 2010 04:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C2A373A680D; Mon, 8 Nov 2010 20:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.838
X-Spam-Status: No, score=-4.838 tagged_above=-999 required=5 tests=[AWL=1.411, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qOGBeXtztKb1; Mon, 8 Nov 2010 20:57:54 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id BECA73A677C; Mon, 8 Nov 2010 20:57:52 -0800 (PST)
Received: from ( []) by (8.14.3/8.14.3/ICT) with ESMTP id oA94wADb031705 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 9 Nov 2010 05:58:10 +0100
Received: from ([]) by ([]) with mapi; Tue, 9 Nov 2010 05:58:10 +0100
To: Mark Nottingham <>
Date: Tue, 9 Nov 2010 05:53:18 +0100
Thread-Topic: [httpstreaming] [dispatch] Q-HTTP
Thread-Index: Act/ucma0OpOn8J8TYK0i7gocPK0egADlZUg
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: es-ES
acceptlanguage: 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
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: Tue, 09 Nov 2010 04:57:55 -0000

Hi Mark,

Our first approach was to integrate this protocol into WWW (for example,  as a protocol handler embeded in the web browser) and reuse some of the existing standards like HTTP syntax and SDP, which are compact and efficient ways to define the messages.

Q-HTTP can be used out of web context, but inside a web context, a website could have a httpq URI inside the web page, like images, sound and other files, and this mechanism could be the door for provide/measure/react QoS on demand in web services. In this sense can be seen as a complement for HTTP in the real-time field.

Any suggestion about a better name? This is an open debate among technician people. Some of them push the name but others reject it. And for the moment we have not found a better one. Perhaps this could be an opportunity to re-baptize the protocol. 

-----Mensaje original-----
De: Mark Nottingham [] 
Enviado el: martes, 09 de noviembre de 2010 3:57
CC: Qin Wu;; httpstreaming
Asunto: Re: [httpstreaming] [dispatch] Q-HTTP

Without going into the details of the proposal itself --

"Q-HTTP" is a *horrible* name. It will confuse many people -- is it a replacement for HTTP? An enhancement to HTTP? Etc.

Please change the name and proposed URI scheme ASAP; it'll make it a lot easier to socialise if it does gain traction.

Furthermore, based on this statement:

>    Q-HTTP does not establish multimedia sessions and it does not transport application data.

... the only thing it shares with HTTP is the syntax of the messages. Lots of IETF experience shows that basing new protocols on HTTP syntax isn't such a good idea; if you want an easy-to-parse format, how about JSON?

Please don't take this as criticism of the proposal itself -- I'm excited to see so many people working in this area.


On 09/11/2010, at 3:33 AM, GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER) wrote:

> 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:
> ml
> Regards!
> -Qin
> ----- 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