Re: [aqm] IETF88 Fri 08Nov13 - 12:30 Regency B

"Akhtar, Shahid (Shahid)" <shahid.akhtar@alcatel-lucent.com> Fri, 08 November 2013 20:08 UTC

Return-Path: <shahid.akhtar@alcatel-lucent.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77DF321E8152 for <aqm@ietfa.amsl.com>; Fri, 8 Nov 2013 12:08:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.357
X-Spam-Level:
X-Spam-Status: No, score=-10.357 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id luEOA4HsaDfu for <aqm@ietfa.amsl.com>; Fri, 8 Nov 2013 12:08:31 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id EA12921E8202 for <aqm@ietf.org>; Fri, 8 Nov 2013 12:08:25 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rA8K8Im3028944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 8 Nov 2013 14:08:19 -0600 (CST)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id rA8K8HkV010052 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Nov 2013 15:08:17 -0500
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.204]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Fri, 8 Nov 2013 15:08:17 -0500
From: "Akhtar, Shahid (Shahid)" <shahid.akhtar@alcatel-lucent.com>
To: David Ros <David.Ros@telecom-bretagne.eu>
Thread-Topic: [aqm] IETF88 Fri 08Nov13 - 12:30 Regency B
Thread-Index: AQHO3LgYYRJ73SkRuUGeumV/fMXv9ZobwxY8
Date: Fri, 08 Nov 2013 20:08:17 +0000
Message-ID: <2763134A-F3B0-4BB2-BB76-B5AF52A1787E@alcatel-lucent.com>
References: <012C3117EDDB3C4781FD802A8C27DD4F25E6A85C@SACEXCMBX02-PRD.hq.netapp.com> <C0611F522A6FA9498A044C36073E49657E5FF524@US70UWXCHMBA01.zam.alcatel-lucent.com> <5B72ED36-A189-4C01-80DB-F6D2F247CDDF@cisco.com> <C0611F522A6FA9498A044C36073E49657E5FFA98@US70UWXCHMBA01.zam.alcatel-lucent.com> <6A0A7988-7CEA-40E2-924A-80BCC141F1F1@cisco.com> <C0611F522A6FA9498A044C36073E49657E5FFFB8@US70UWXCHMBA01.zam.alcatel-lucent.com>, <B7249D76-0F19-4456-A01D-8C075E9946E9@telecom-bretagne.eu>
In-Reply-To: <B7249D76-0F19-4456-A01D-8C075E9946E9@telecom-bretagne.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Richard Scheffenegger <rs@netapp.com>, Wesley Eddy <wes@mti-systems.com>, "Fred Baker (fred)" <fred@cisco.com>, "Naeem Khademi (naeemk@ifi.uio.no)" <naeemk@ifi.uio.no>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] IETF88 Fri 08Nov13 - 12:30 Regency B
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 20:09:08 -0000

David,

Please see a quick answer to your questions below.

-Shahid.

Sent from my iPhone

On Nov 8, 2013, at 1:24 PM, "David Ros" <David.Ros@telecom-bretagne.eu> wrote:

> 
> On 8 nov. 2013, at 10:38, Akhtar, Shahid (Shahid) <shahid.akhtar@alcatel-lucent.com> wrote:
> 
> [snip]
>> Recommend the following text in section 4.7
>> 
>> Research should focus on improving end user QoE from AQMs rather than network related metrics only. Often a significant change in a network metric may only make a minimal change in end-user QoE and thus the value of such change may be minimal.
> 
> Can this be said to be true for the QoE of *any* application?
> 
> And, if we focus on QoE instead of network metrics, (a) what apps are we going to consider? (b) do we have easy-to-use, readily-available and accurate models for assessing QoE for all those apps?
> 
> (Note, I'm not trying to contradict what you say, I just want to better understand what concrete evaluation guidelines could be given on this)

My text says to focus on QoE as well - meaning both network metrics and service QoE.

Key services on the Internet like web browsing have been around for like 20 years - so major services are slow to change. 

Research does exist on translating application performance to QoE - key new example may be HAS where I have mentioned a couple of papers in my talk at ICCRG. Note that since this is a research topic, we do not need to have all the answers now.

> 
> Thanks,
> 
> David
> 
>> 
>> Research should make suggestions on how to make good decisions on buffer sizes with each type of AQM (e.g. 2xBDP) - explaining why or how such buffer sizes improve end-user QoE and network health.
>> 
>> Research should be done on methods or good configurations that leverage deployed AQMs such as RED/WRED that reduce delays and prevent lockout with typical traffic and network conditions. 
>> 
>> 
>> 
>> From: Fred Baker (fred) [mailto:fred@cisco.com] 
>> Sent: Friday, November 08, 2013 10:27 AM
>> To: Akhtar, Shahid (Shahid)
>> Cc: Richard Scheffenegger; aqm@ietf.org; Naeem Khademi (naeemk@ifi.uio.no); Gorry Fairhurst; Wesley Eddy
>> Subject: Re: IETF88 Fri 08Nov13 - 12:30 Regency B
>> 
>> 
>> 
>> On Nov 8, 2013, at 5:56 AM, "Akhtar, Shahid (Shahid)" <shahid.akhtar@alcatel-lucent.com> wrote:
>> 
>>> One of the the objectives of newer AQMs being defined here should be to minimize tuning, but we should recognize that likely tuning or some configuration cannot be eliminated altogether.
>>> 
>>> FB: That's an opinion. One of the objectives of Van and Kathy's work, and separately of Rong Pan et al's work, is to design an algorithm that may have different initial conditions drawn from a table given the interface it finds itself on, but requires no manual tuning. The great failure of RED, recommended in RFC 2309, is not that it doesn't work when properly configured; it's that real humans don't have the time to properly tune it differently for each of the thousands of link endpoints in their networks. There is no point in changing away from RED if that is also true of the replacement.
>>> 
>>> SA: You argue that "initial conditions" determine some of the parameters of newer AQMs (like Codel and PIE), then those same initial conditions would also determine some of the key parameters for RED/WRED.
>> 
>> I'm simply going to point out that Van and Kathy spent quite a bit of time and effort trying to do exactly that, and it didn't pan out. Codel is their suggestion of a replacement that is largely auto-tuning within a specified range of situations.
>> 
>> On your other points, please suggest text, and the WG can discuss whether they buy it.
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
> 
> =================================================================
> David ROS
> http://www.rennes.enst-bretagne.fr/~dros/
> 
> Deadlines really start to press a week or two after they pass. -- John Perry
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm