[dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 3
"GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com> Thu, 03 February 2011 16:06 UTC
Return-Path: <jose_javier.garcia_aranda@alcatel-lucent.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 122043A69F7 for <dispatch@core3.amsl.com>; Thu, 3 Feb 2011 08:06:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.79
X-Spam-Level:
X-Spam-Status: No, score=-5.79 tagged_above=-999 required=5 tests=[AWL=0.458, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMyi8WlbGsBw for <dispatch@core3.amsl.com>; Thu, 3 Feb 2011 08:06:17 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 852D13A69E3 for <dispatch@ietf.org>; Thu, 3 Feb 2011 08:06:17 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p13G5W0T005847 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 3 Feb 2011 17:05:33 +0100
Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 3 Feb 2011 17:05:33 +0100
From: "GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com>
To: "'dispatch@ietf.org'" <dispatch@ietf.org>
Date: Thu, 03 Feb 2011 17:05:31 +0100
Thread-Topic: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 3
Thread-Index: AcugSvRWsT7gbY+GSyqLnLGU53HqvAAGPezQA4BiV1AFVZaPQA==
Message-ID: <3349FECF788C984BB34176D70A51782F1882C802@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
References: <3349FECF788C984BB34176D70A51782F18374A47@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <4D0F5BD8.4040506@alvestrand.no>
Accept-Language: en-US
Content-Language: es-ES
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_3349FECF788C984BB34176D70A51782F1882C802FRMRSSXCHMBSB3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 3
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 16:06:19 -0000
hi folks, that's the version 3 of Q4S charter , after including more received feedback and integration with rtcweb initiative into our objetives regards - jose javier 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. A Q4S protocol monitors and sends alerts, which are useful to know when those types of solutions should be taken, but it does not assume that that the network is not doing deep packet inspection or differential treatment of services. 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. Optimize to use low bit rates in the Q4S control flow (typlically below 2.4 kbps) in order to produce a minimum disturbance in the application flows. 4. To ensure a feasible practical implementation based on policy servers and interoperability between service providers 5. Integration into rtcweb inititative as a part of the set of components used to communicate universally in real-time communications. 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. 4. Analysis of benefits of Q4S in real-time internet applications and how Q4S complements the rest of components of rtcweb initiative Goals and Milestiones ===================== Nov 2010 Submit Internet-Draft as a proposed standard for QoS application-level protocol Jan 2011 Submision of Q4S protocol Internet-Draft as improvement of Q-HTTP protocol Feb 2011 Proposed charter for Q4S WG Informational document with rules for dimensioning and performance analysis Specification of architecture document for implementation
- [dispatch] Charter proposal for Q4S WG ( formerly… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Janet P Gunn
- Re: [dispatch] Charter proposal for Q4S WG ( form… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… DIAZ VIZCAINO, LUIS MIGUEL (LUIS MIGUEL)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Peter Musgrave
- Re: [dispatch] Charter proposal for Q4S WG ( form… Janet P Gunn
- Re: [dispatch] Charter proposal for Q4S WG ( form… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Harald Alvestrand
- Re: [dispatch] Charter proposal for Q4S WG ( form… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- [dispatch] Charter proposal for Q4S WG ( formerly… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Cullen Jennings
- Re: [dispatch] Charter proposal for Q4S WG ( form… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… DIAZ VIZCAINO, LUIS MIGUEL (LUIS MIGUEL)
- [dispatch] Q4S Protocol ( formerly Q-HTTP) GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- [dispatch] Charter proposal for Q4S WG ( formerly… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Harald Alvestrand
- Re: [dispatch] Charter proposal for Q4S WG ( form… GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)
- Re: [dispatch] Charter proposal for Q4S WG ( form… Harald Alvestrand