Re: [rmcat] test cases for coupled cc [was: Re: Review of draft-ietf-rmcat-eval-test-02]

Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com> Fri, 26 February 2016 08:15 UTC

Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB68E1A6FA3 for <rmcat@ietfa.amsl.com>; Fri, 26 Feb 2016 00:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level:
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WxWOpx8w_H0 for <rmcat@ietfa.amsl.com>; Fri, 26 Feb 2016 00:15:49 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1151A21A9 for <rmcat@ietf.org>; Fri, 26 Feb 2016 00:15:48 -0800 (PST)
X-AuditID: c1b4fb2d-f794c6d000006f31-40-56d009b15c9c
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 8C.C3.28465.1B900D65; Fri, 26 Feb 2016 09:15:46 +0100 (CET)
Received: from [150.132.141.43] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.3.248.2; Fri, 26 Feb 2016 09:15:44 +0100
To: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
References: <170F0EA5-EAB0-4B01-A8DF-56A0B2923A9A@ifi.uio.no> <56AA17AD.8060806@ericsson.com> <EA475291-B965-43EE-965B-F5435B595493@tik.ee.ethz.ch> <56BB01D5.5040902@ericsson.com> <FA953D22-37A1-4645-8F20-56C79A4B2806@ifi.uio.no> <56C312A9.1000609@ericsson.com> <CD27383B-9B91-4B86-AF72-17F2BDE4784A@ifi.uio.no> <56CD8EA6.9010603@tik.ee.ethz.ch> <56CEC358.9060103@ericsson.com> <56CF29C7.20200@tik.ee.ethz.ch>
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Organization: Ericsson AB
Message-ID: <56D009B0.2030005@ericsson.com>
Date: Fri, 26 Feb 2016 09:15:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56CF29C7.20200@tik.ee.ethz.ch>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM2K7t+4mzgthBmsmS1v8OLuT1WLD6iks FqtvfmBzYPZYsuQnk8fq1Q+ZPY59+MoWwBzFZZOSmpNZllqkb5fAldEw7SxbQb94RfvfbsYG xi1CXYycHBICJhK3H11hhbDFJC7cW8/WxcjFISRwmFHiw9mFjBDOGkaJn4cesoBUCQskS7y5 eJsJxBYRcJOYt2o9K0TRSmaJSWfnM4MkmAU8Jc5+ewJUxMHBJmAj8XixH0iYX0BSYkPDbmaQ MK+AtsSahWogYRYBVYmHu2ewg9iiAjESx9+dYwSxeQUEJU7OfAK2llNAR+LF/uVMENMtJGbO P88IYctLNG+dDTZSSEBXoutl3ARGoVlIumch6ZiFpGMBI/MqRtHi1OLi3HQjY73Uoszk4uL8 PL281JJNjMDAPrjlt+4OxtWvHQ8xCnAwKvHwfvh+PkyINbGsuDL3EKMEB7OSCC/XX6AQb0pi ZVVqUX58UWlOavEhRmkOFiVx3jXO68OEBNITS1KzU1MLUotgskwcnFINjO5x7BuWPVj5J2fP gdSmeedZFR78/vF5qkBKjsrP+/uYT9wW2i/AvEi60cxzZUDyzvKy44+fXyidbrXs29GJymwy BRrzVrrNefj03Le5K/v2HnI9G/RVTtf4btnimZsP7Zp06OOFl8t2vdW/H/I1L5rLeyPj3fTu nkeP4/19fsf96f+uG/pyf4akEktxRqKhFnNRcSIAdTKlpWgCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/kdeLJmkimNgDOzzxuwkbFPopwQo>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, Michael Welzl <michawe@ifi.uio.no>
Subject: Re: [rmcat] test cases for coupled cc [was: Re: Review of draft-ietf-rmcat-eval-test-02]
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 08:15:50 -0000


On 2016-02-25 17:20, Mirja Kühlewind wrote:

>>>
>>> I agree with Michael. My view is here that we need to evaluate each
>>> combination of a certain scheme to couple things using a certain
>>> congestion control algorithm separately.
>> Fine. but again what exactly are we supposed to evaluate? the
>> performance of the congestion control algorithm or the performance of
>> the coupled congestion control algorithm? or something else.
>
> The performance of the combined system of the coupling algo and the
> selected cc aglo.
ok, the current draft says "This document describes the test cases
    to be used in the performance evaluation of those candidate
    algorithms."
as now we are talking about combined system, this needs to be changed I 
guess. right? but we need to clarify what this combined system means, I 
hope we are not leaning towards the whole RTC system evaluation.
>
>>> That means, if someone proposes a new (generic) scheme for coupling,
>>> we as a group would only advise to use this scheme with a certain cc
>>> algorithm if we have seen results for this specific combination. Does
>>> this make sense to you?
>> Kind of, this means it is fine to have a coupled congestion control that
>> may not work will all the combinations even if RMCAT proposes more that
>> one congestion control algorithms.
>
> Yes (as long as this is clearly stated in the doc).
ok. but the eval-test draft doesn't need to clarify that, right?
>
>>
>> I didnt get the "generic"  part though. How can the WG call a coupled
>> congestion "generic" even if that fails to show results with all the
>> RMCAT CC algorithms (assuming RMCAT has proposed more than one CC
>> algorithms)?
>
> That's only a matter of how it is described in the doc. Basically you
> say, we describe this in a generic way, but it's only tested together
> with these algos. If you want use it with others, it might be possible,
> but you have to (adapt and) test it on your own. Important is that you
> have both in the same doc: the generic description and how it is applied
> to certain algos. Does that make sense? Or it this a problem for any of
> your work?
Ok so here "generic" does not mean the algorithm is generic, it points 
to the generic description of the coupled CC.

No problem for any work as long as the above clarification text is not 
part of the eval-test draft.

>
> I believe that is at least the approach we are currently taking for the
> coupled-cc draft that we have. Micheal, please speak up if you have a
> different view here!
>

BR
-- 
Zahed

==================================================
ANM ZAHEDUZZAMAN SARKER


Ericsson AB
Services, Media and Network Features
Laboratoriegränd 11
97128 Luleå, Sweden
Phone +46 10 717 37 43
Fax +46 920 996 21
SMS/MMS +46 76 115 37 43
zaheduzzaman.sarker@ericsson.com
www.ericsson.com

==================================================