Re: [rmcat] Still looking for reviews of draft-ietf-rmcat-nada

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Thu, 20 July 2017 17:48 UTC

Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8D1129B14; Thu, 20 Jul 2017 10:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ZrW1CkPld5pz; Thu, 20 Jul 2017 10:48:13 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB62F1252BA; Thu, 20 Jul 2017 10:48:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4522; q=dns/txt; s=iport; t=1500572892; x=1501782492; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=PY4GIbUBwHEpbtL8aMLj5iOJZnJdGU8BQE2KA/njFuY=; b=Oa3ttLLhhbmQpB0wY0BGnoW4ktpnjex56X4qMbGRyBxkh/BHyHiCFYnc IQEW4WL2CksGvFQfJcqPLEssC4uHmsyrPUdJ/6MKHoiBa+WNhnL12Gh3y lLUdgIQ+zdo7zA0NKy4A74F66Fix6qYy7TODNpjRF159fvdYTtu3lY6zw c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CYAABO7HBZ/5hdJa1VBQMZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDWmSBFAeGN4dNkWd0gxwBA5FxghEkhSMCg3U/GAECAQEBAQE?= =?us-ascii?q?BAWsohRgBAQEBAgFuCwUJAgIBCBEEAQEBCSUPDBcdCAIEAQ0FiicItGqLIQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAR0FgyODTYFhgnA0hDsNBQEcDBUmhS0Fnz4ClBi?= =?us-ascii?q?CDJAoiUiMFQEfOD9AC3UVSYUTHIFndodJgSOBDgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.40,384,1496102400"; d="scan'208";a="453713682"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2017 17:48:12 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v6KHmBwl006253 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jul 2017 17:48:11 GMT
Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 12:48:11 -0500
Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1210.000; Thu, 20 Jul 2017 12:48:11 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: "Flohr, Julius" <julius.flohr@uni-due.de>, "Sergio Mena de la Cruz (semena)" <semena@cisco.com>
CC: Anna Brunstrom <anna.brunstrom@kau.se>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-nada@ietf.org" <draft-ietf-rmcat-nada@ietf.org>
Thread-Topic: [rmcat] Still looking for reviews of draft-ietf-rmcat-nada
Thread-Index: AQHS8Y2pxcJQ+kMB70aHp0rw3JJZPqJD6DwAgBXQrQCAAN95AIAAkgMAgABIEQCAAacuPQ==
Date: Thu, 20 Jul 2017 17:48:11 +0000
Message-ID: <1500572924701.63015@cisco.com>
References: <7c5453a5-65f6-6f74-6214-346469c8abce@kau.se> <c8d9ec64-c332-fa8d-dd20-3dd307aabb97@kau.se> <DB4PR07MB348F7D8702DC16028081554C2D70@DB4PR07MB348.eurprd07.prod.outlook.com> <62513FF8-0A36-45FC-878C-7D03A1772A2A@uni-due.de> <6ca96a44-0ca2-2704-41f6-3eaeaf35afa7@kau.se> <aa200a17-1d8c-9570-2b51-364a08a131a6@cisco.com>, <830396B0-DCDB-42F3-BAF7-EE122CA123D1@uni-due.de>
In-Reply-To: <830396B0-DCDB-42F3-BAF7-EE122CA123D1@uni-due.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.152.245.107]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/VB9KEaBFVjf9MTdqSl6_s55knPk>
Subject: Re: [rmcat] Still looking for reviews of draft-ietf-rmcat-nada
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 17:48:15 -0000

Catching up on this thread. 

Thanks much to Julius, Ingmar, and Safiqul for reviewing this draft and providing your input. 

Regarding Ingmar's comments:

* Page 8, computation of d_tilde and the risk of being locked in the loss-based mode due to non-linear warping:  fully agree that this is a limitation of the algorithm we should acknowledge in the draft.  In the meanwhile would like to work with Julius to look into specific example failure cases, and hopefully derive further insights on how to better tune the algorithm parameters.  Will update both our ns3-rmcat implementation and NADA draft after that investigation. 

* Section 5.1.2 : Estimation of p_mark : as I understand your comments point to the fact that different ECN marking behaviors may occur and some (e.g., L4S) may not interact well with NADA.  It is true that we have not tested NADA extensively against different variants of ECN markings --- the one's we've tried before are RED (marking instead of dropping).  One way to help clarify that will be to point to our Appendix A.2 as the specific ECN marking behavior we expect, in Sec. 5.1.2.  Do you think that will address your concern?   

And, thanks to Julius for sharing with us issues you've observed in your implementation efforts.  We've set up a separate email thread to meet up remotely and go over that in greater technical details. 

Question back to the Chairs:  our plan now is to update both our draft (to address both sets of Ingmar's comments) and corresponding ns3 open-source implementation, within a month.  Procedure-wise, are we expecting the updated version (-05) to go through WGLC again at that point?  Just trying to understand what to expect next. 

Thanks,
Xiaoqing
 

    
________________________________________
From: Flohr, Julius <julius.flohr@uni-due.de>
Sent: Wednesday, July 19, 2017 6:19 AM
To: Sergio Mena de la Cruz (semena)
Cc: Anna Brunstrom; Ingemar Johansson S; rmcat@ietf.org; draft-ietf-rmcat-nada@ietf.org
Subject: Re: [rmcat] Still looking for reviews of draft-ietf-rmcat-nada

Hi,

> On 19. Jul 2017, at 09:01, Sergio Mena <semena@cisco.com> wrote:
>
>
> As for Julius's tests, we thank Julius for the effort put into it, and would like to see how his results compare to our latest ones (see Slides presented by Xiaoqing in April's RMCAT interim).
>

I haven’t done too much testing, but as far as I can tell there is an issue when the bottleneck bandwidth is smaller than RMAX:
If you have a competition scenario between NADA and a loss based flow, it seems that nada gets stuck in the competitive mode because itself creates queueing delay that is larger than QTH.

I actually made a little mistake when I said the problem has gotten worse compared to the last version of the draft. The issue actually has been introduced in version 03 with the introduction of TEXPLOSS. Before, the draft was very unclear and stated that one should warp the congestion signal IFF packet loss is present, but without stating a time span.

Therefore the implementation just used the knowledge it had from the recent observation window LOGWIN (500 ms). That worked really well because it helped the algorithm to return to the normal mode of operation more easily, because after that timespan it would stop warping regardless whether there is lots of queueing delay present or not.

I don’t know if this is an issue with my implementation or if there is an actual issue with the algorithm, but this is what I have observed.

I’ll contact Xiaoqing and Sergio directly so we can work together on this issue and post our findings to this mailing list directly.

Regards,

Julius


=====================================
Julius Flohr, M.Sc.
University of Duisburg-Essen
Computer Networking Technology Group

Room SL-408
Schützenbahn 70
D-45326 Essen/Germany

E-Mail:  julius.flohr@uni-due.de
Phone: +49-201-183-7667
Fax:     +49-201-183-7673
=====================================