Re: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 1

Hi Peter , all

relation with rtcweb
===============
rtcweb try to identify and find a consensus on a  set of components to communicate universally for real-time communications. Inside this approach, Q4S protocol could be part of this set of agreed protocols. The intention of rtcweb is to standarize as much as possible, without leaving these set of protocols or functionalities in the scope of web applications or plug-ins for browsers. We believe that a standarized protocol for Quality measurements and alerts would be interesting for all internet community because if we compare a Q4S standard protocol  with propietary solutions, we found that the range of benefited applications and the number of possible implementations are higher with a standardized solution.
In addition a multi-ISP solution could be reached using a standard protocol, in which each peer of communication belongs to a different ISP and possibilities based on Q4S protocol are available for QoS profile managemen.

relation with http
=====================
The measurement and/or alert in realtime functions would be  covered by the Q4S wg, in particular the Q - HTTP protocol ( which may be renamed to Q4S or other name).
This protocol (formerly named Q-HTTP) uses HTTP syntax, and uses specific URI for easy integration in www. However can be used out of www context.  In fact,  the protocol is not an http extension.  It is an out-of-band protocol to measure and alert participants of a communication based in any protocol ( http could be the protocol to transmit application data and Q-HTTP the protocol to monitor the quality end2end).  The protocol can be used in conjuntion with any other protocol used for application data transport (HTTP, FTP, RTP, whatever) . In fact, Q-HTTP is not used  to  transpor t  data, but for measurement the latency, jitter, packetloss end2end and alert if some thresholds are being violated for trigger adaptative solutions or changes in QoS profile.

The concrete adatative solution or how the QoS profile is changed is out of scope of the protocol. The protocol only monitor and send an alert, that is useful to know when these types of actions should be taken

- jose javier

________________________________
De: Peter Musgrave [mailto:peter.musgrave@magorcorp.com]
Enviado el: viernes, 17 de diciembre de 2010 12:57
Para: GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
CC: 'dispatch@ietf.org'; pedrochas@dit.upm.es; CUBILLO PASTOR, CLARA (CLARA); ORTIGA HERRERA, GUADALUPE (GUADALUPE); jquemada@dit.upm.es; HERRANZ PABLO, SONIA (SONIA); gabriel@dit.upm.es; barcenilla@dit.upm.es; jsr@dit.upm.es; DIAZ VIZCAINO, LUIS MIGUEL (LUIS MIGUEL)
Asunto: Re: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 1

Hi Jose,

Can you comment on the relationship of this work to the rtcweb drafts currently in dispatch? Those seems to me a method to use existing protocols to solve very similar issues.

I am also unsure of what defining an application level standard protocol really means. Is this changes to http? Something that runs beside http? Instead of? Over?

Thanks,

Peter Musgrave

On 2010-12-13, at 10:39 AM, GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER) wrote:

Hi everybody,

Here is the charter proposal for Q4S ( Quality for service) WG. This WG will include the achieved works with  "Q-HTTP"

Thanks for your comments

Description of Working group
============================

   Problem Statement:

   The QoS over Internet is a hot issue today. Current QoS handling
   mechanisms used in  modern network transport layers (MPLS, RSVP,
   Diffserv,Traffic Engineering) do not provide  themselves a
   QoS-on-demand end-to-end solution and existing adaptative
   solutions based on In-band Control protocols (such as RTCP)
   are very difficult to combine with any other protocols for which
   they have not been designed for.

   Four Network Parameters comprises the QoS at application level:
   Bandwidth, packet-loss, latency and Jitter.

   Interactive-video applications define flows in both directions.
   Different applications require different constraints (in terms of
   latency, jitter, packet loss) in one or both directions and
   different responsiveness. The proposed solution must be an
   effective out-of-band application level protocol capable of
   reacting when any of these constraints are violated. Such protocol
   must trigger adaptive solutions and/or QoS network profile changes.

   Currently content providers are only able to provide services based
   on adaptative methods or last-mille deployments which prefer
   dedicated network resources (vs. Internet), and therefore, restricts
   the subscriber population and increases the costs.

   Objetives:

   The goal of this working group is to define a
   QoS application-level  standard protocol optimized for its use over
   the internet that may be widely implemented and easily managed
   by application developers and service providers.

   The core technical considerations for such protocol include, but
   are not necessarily limited to, the following:

   1. Protocol design to be used in interactive applications (including
      virtualized videogames,and interative-video applications)

   2. Ensuring interoperability with all existing transport protocols

   3. Optimizing for low bit rates (typlically below 2.4 kbps)

   4. To ensure a feasible practical implementation based on
      policy servers and interoperability between service providers

   Deliverables:

   1. Specification of protocol that meets the requirements in the
      form of an Internet-Draft that defines the negotiation of QoS
      parameters, the measurement process and alert mechanisms.

   2. Dimensioning rules and performance analysis

   3. A set of technical requirements for a practical
      implementation which may include adaptative solutions and/or
      QoS profile modification.

Goals and Milestiones
=====================

Nov 2010    Submit Internet-Draft as a proposed standard for QoS
             application-level protocol

             Proposed charter for Q4S WG

             Informational document with rules for dimensioning
             and performance analysis

             Specification of architecture document for implementation

- Jose Javier

_______________________________________________
dispatch mailing list
dispatch@ietf.org<mailto:dispatch@ietf.org>
https://www.ietf.org/mailman/listinfo/dispatch