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

Janet P Gunn <jgunn6@csc.com> Thu, 16 December 2010 22:24 UTC

Return-Path: <jgunn6@csc.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 1C1283A6979; Thu, 16 Dec 2010 14:24:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 XoBXVP3rRt3z; Thu, 16 Dec 2010 14:24:05 -0800 (PST)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by core3.amsl.com (Postfix) with ESMTP id 73B943A6915; Thu, 16 Dec 2010 14:24:05 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-3.tower-171.messagelabs.com!1292538349!35709035!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [20.137.2.87]
Received: (qmail 24649 invoked from network); 16 Dec 2010 22:25:50 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-3.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Dec 2010 22:25:50 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (Switch-3.4.3/Switch-3.3.3mp) with ESMTP id oBGMPmjO009531; Thu, 16 Dec 2010 17:25:48 -0500
In-Reply-To: <3349FECF788C984BB34176D70A51782F18374A47@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
References: <3349FECF788C984BB34176D70A51782F18374A47@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
To: "GARCIA ARANDA, JOSE JAVIER (JOSE JAVIER)" <jose_javier.garcia_aranda@alcatel-lucent.com>
MIME-Version: 1.0
X-KeepSent: B818205E:091BC16F-852577FB:007ADF83; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 CCH2 April 23, 2009
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFB818205E.091BC16F-ON852577FB.007ADF83-852577FB.007B37FE@csc.com>
Date: Thu, 16 Dec 2010 17:25:51 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.1FP1 HF440|June 18, 2010) at 12/16/2010 05:25:25 PM, Serialize complete at 12/16/2010 05:25:25 PM
Content-Type: multipart/alternative; boundary="=_alternative 007B37B3852577FB_="
X-Mailman-Approved-At: Thu, 16 Dec 2010 14:54:50 -0800
Cc: "pedrochas@dit.upm.es" <pedrochas@dit.upm.es>, "'dispatch@ietf.org'" <dispatch@ietf.org>, dispatch-bounces@ietf.org, "ORTIGA HERRERA, GUADALUPE (GUADALUPE)" <guadalupe.ortiga_herrera@alcatel-lucent.com>, "jquemada@dit.upm.es" <jquemada@dit.upm.es>, "CUBILLO PASTOR, CLARA (CLARA)" <clara.cubillo_pastor@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>, "HERRANZ PABLO, SONIA (SONIA)" <sonia.herranz@alcatel-lucent.com>, "DIAZ VIZCAINO, LUIS MIGUEL (LUIS MIGUEL)" <luismi.diaz@alcatel-lucent.com>
Subject: Re: [dispatch] Charter proposal for Q4S WG ( formerly Q-HTTP) Version 1
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, 16 Dec 2010 22:24:07 -0000

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