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

Hi Janet,

This new protocol nature for doing it is out-of-band. It means that it will run
in parallel with the protocol in charge of transport application data .
For example this new protocol could be used in parallel with FTP, HTTP , RTC or whatever.

The new protocol measures the quality ( latency, jitter, packetloss, bandwidth) at the
beggining and if the minimum quality is reached, the application can start asuring
a good experience. During the application timelife, the new protocol measures
continuously the latency, jitter an packetloss and alerts if one or some of these
parameters are below certain threshold ( which depends on the application nature).

Therefore, we propose a protocol compatible with all existing transport ones, to provide a
reliable mechanism for adaptative and QoS profile optimization.

The new protocol uses low resources. Depending on the resources being used, the
responsiveness is different. For example, it can be useful to have a better  responsiveness
 in downlink than uplink, depends on each application. However, in any case is a good point
to consume a low bit rate for this purpose, though there is a trade-off between responsiveness and
used bit-rate

- jose javier

________________________________
De: Janet P Gunn [mailto:jgunn6@csc.com]
Enviado el: jueves, 16 de diciembre de 2010 23:26
Para: GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
CC: barcenilla@dit.upm.es; CUBILLO PASTOR, CLARA (CLARA); 'dispatch@ietf.org'; dispatch-bounces@ietf.org; gabriel@dit.upm.es; ORTIGA HERRERA, GUADALUPE (GUADALUPE); jquemada@dit.upm.es; jsr@dit.upm.es; DIAZ VIZCAINO, LUIS MIGUEL (LUIS MIGUEL); pedrochas@dit.upm.es; HERRANZ PABLO, SONIA (SONIA)
Asunto: Re: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 1

I am a little bit confused by the combination  of
        1. Protocol design to be used in interactive applications (including
      virtualized videogames,and interative-video applications)
  and
    3. Optimizing for low bit rates (typlically below 2.4 kbps)

I do not know many video games that work effectively at 2.4 kbps.

Am I missing something?

Janet

From:   "GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com>
To:     "'dispatch@ietf.org'" <dispatch@ietf.org>
Cc:     "pedrochas@dit.upm.es" <pedrochas@dit.upm.es>, "CUBILLO PASTOR,        CLARA \(CLARA\)" <clara.cubillo_pastor@alcatel-lucent.com>, "ORTIGA        HERRERA,        GUADALUPE \(GUADALUPE\)" <guadalupe.ortiga_herrera@alcatel-lucent.com>, "jquemada@dit.upm.es" <jquemada@dit.upm.es>, "HERRANZ PABLO,        SONIA \(SONIA\)" <sonia.herranz@alcatel-lucent.com>, "gabriel@dit.upm.es" <gabriel@dit.upm.es>, "barcenilla@dit.upm.es" <barcenilla@dit.upm.es>, "jsr@dit.upm.es" <jsr@dit.upm.es>, "DIAZ        VIZCAINO, LUIS MIGUEL \(LUIS MIGUEL\)" <luismi.diaz@alcatel-lucent.com>
Date:   12/13/2010 10:56 AM
Subject:        [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 1

________________________________

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
https://www.ietf.org/mailman/listinfo/dispatch