Re: [tsvwg] Consensus call on ECT(1)
"Mohit P. Tahiliani" <tahiliani.nitk@gmail.com> Mon, 18 May 2020 21:59 UTC
Return-Path: <tahiliani.nitk@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321133A00E0 for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 14:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level:
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 WltxK2DotWoi for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 14:59:20 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264183A00D3 for <tsvwg@ietf.org>; Mon, 18 May 2020 14:59:19 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id f4so12372711iov.11 for <tsvwg@ietf.org>; Mon, 18 May 2020 14:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wxl/PMCBkbSvzguDOThmYDrDsDkKsgXRX+YZNuS1kUY=; b=KioImulIVa2JiHVbFx/A3zQuIpnL4S2sgM5YDIB/27RpP89mHq4Q7Ermn/dnYUWQFm vCSPJDB6ynVt09XivIr5+zfx2m6T47S8qFI6QAt41O/RWYZ5GITi17xQh1kdA6Bzz85x zmLpkC6mR6N8BRYAyQ7xn7lJ2CZDPsp4RRbkWnMDVlXQDFEJhHr45gtESf4gZOa1FLae ECCkfXUIl9K0IZv2WN8LKk7osPaOnVGMIRIpVIFhaG4hkZKY34pSvqJqFPNh1rYQ7Sxz XZamXTveaS0xV5gtiXGrCUUDaghFPjmvrQkVRuYNKWuwAJp/1CfT5+o5z+MR7yz+NKQZ VY3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wxl/PMCBkbSvzguDOThmYDrDsDkKsgXRX+YZNuS1kUY=; b=RYh4DCysBxEh1eJnvU82I8I0f+u+WHt3mq+FdOw6GMr8KjmQgKqw5Er5/kml8uqiAs NCYqeg62+BbQZBcLNjcda5EPAjEYmhtIl/v0MFO8VyJP0ZUeWsMzMojcPW/MJYz0nW4E uW+hLM/j5PV++RXNGKyuJRRiv9S1D+YD5bCAlE16h0ji/m5xnAZnB6WKVq3damgnfSXR c7VnDhNgv2TPeHXnTPgWJkUge0yUc2jR3TgZBVpnkYGWBIToIXEISxJuCJyMe+p/3BQY TdR3uEdD2n/6sETq6+Xi4m3GbAbwsZYO47NKdnoKeHH85pG+YnPMG9Fb5qYJgTG8v6NI 7ntw==
X-Gm-Message-State: AOAM532cjCV7mK/jWBDC/T09OVMlWprWPaRnoKJ+D7sW5gkTDGu2jrVB pthXmAZEpvr/83ssOEUmzvlGLRSmdob9/D3xO3o=
X-Google-Smtp-Source: ABdhPJy1HeO8E6H7i1Gh0cbG3NGnmCys2JoMHvU5hdNoQ5V36KKELibTSFeXJTBvMqdSxNecRac2zkPSIIa4gDmpBjc=
X-Received: by 2002:a5d:96ca:: with SMTP id r10mr16189905iol.19.1589839158940; Mon, 18 May 2020 14:59:18 -0700 (PDT)
MIME-Version: 1.0
References: <46720ce0-ffcb-e97f-3e2d-6b5274b73b15@mti-systems.com>
In-Reply-To: <46720ce0-ffcb-e97f-3e2d-6b5274b73b15@mti-systems.com>
From: "Mohit P. Tahiliani" <tahiliani.nitk@gmail.com>
Date: Tue, 19 May 2020 03:29:07 +0530
Message-ID: <CA+4FxsiVD798WOeUpxnQCoFOfsMkKH0cW6cR5Xdy69XSkQgEHw@mail.gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000051995105a5f34695"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/yKBjqJPbm6tt9-THR6yq4WxymJU>
Subject: Re: [tsvwg] Consensus call on ECT(1)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 21:59:23 -0000
I would prefer Option 3, and the following is my view: Besides the inter-protocol fairness tests that have been already discussed in the list, I would suggest to extensively evaluate the intra-protocol fairness of the proposed mechanisms. One of the tests for evaluating intra-protocol fairness could be to consider a scenario where long lasting flows are transmitting at rates that sum up to the link capacity, and the buffer is below the marking threshold. Add new flows that are short lived so that the buffer starts growing, and eventually the ECN marks begin to be generated. We should then confirm that the long lasting flows back off sufficiently to provide a fair share to the newly started short lived flows, the queue control is as desired and the link capacity is fully utilised. After the short flows end, let only the long lasting flows operate for some duration, and then again add short lived flows. This test could be repeated with varying RTTs for short flows in each epoch to evaluate the proposals in scenarios with different feedback delays. In my opinion, it is important to evaluate both the proposals (L4S and SCE) in a realistic traffic model consisting of a mixture of long lasting flows and short lived flows (the ones that do not last beyond the slow start phase), and feedback delays ranging from a 100s of microseconds to 100s of milliseconds. I would suggest that we carefully outline the benchmark tests to extensively evaluate the new proposals in terms of other desired metrics and network scenarios. Thanks and Regards, Mohit P. Tahiliani On Mon, May 4, 2020 at 11:45 PM Wesley Eddy <wes@mti-systems.com> wrote: > *In this email thread, please state, concisely, which of the following > viewpoints on ECT(1) you prefer. Please have extended discussion in a > different thread. If you are uncomfortable sharing your opinion on the > list, you may email the tsvwg chairs directly (tsvwg-chairs@ietf.org > <tsvwg-chairs@ietf.org>). * > > > > > > * If you did not attend the 27 April interim, please watch the meeting > video [https://www.youtube.com/watch?v=dw3YKyeFxQU > <https://www.youtube.com/watch?v=dw3YKyeFxQU>] for context on this > question. 1. I support using ECT(1) as an input signal to the network. This > is the approach consistent with the current L4S drafts. This position does > not mean that there are no remaining issues with L4S, but that the > remaining issues can be resolved by continued WG effort on the current > drafts. 2. I support using ECT(1) as an output signal from the network. > This is consistent with SCE. If you believe L4S will not be safe for the > internet without significant architectural changes, you are in this group. > 3. There is a specific test or tests I need to see before making a decision > about ECT(1). Please be specific about the tests in your response. Please > submit your opinion by 5/18/2020. * > >
- [tsvwg] Consensus call on ECT(1) Wesley Eddy
- Re: [tsvwg] Consensus call on ECT(1) Greg White
- Re: [tsvwg] Consensus call on ECT(1) Jonathan Morton
- Re: [tsvwg] Consensus call on ECT(1) Steven Blake
- Re: [tsvwg] Consensus call on ECT(1) Sebastian Moeller
- Re: [tsvwg] Consensus call on ECT(1) Jeremy Harris
- Re: [tsvwg] Consensus call on ECT(1) Smith, Kevin, Vodafone Group
- Re: [tsvwg] Consensus call on ECT(1) Roland Bless
- Re: [tsvwg] Consensus call on ECT(1) Neal Cardwell
- Re: [tsvwg] Consensus call on ECT(1) Mirja Kuehlewind
- Re: [tsvwg] Consensus call on ECT(1) Anders Bloom
- Re: [tsvwg] Consensus call on ECT(1) Finkelstein, Jeff (CCI-Atlanta)
- Re: [tsvwg] Consensus call on ECT(1) Tommy Pauly
- Re: [tsvwg] Consensus call on ECT(1) De Schepper, Koen (Nokia - BE/Antwerp)
- Re: [tsvwg] Consensus call on ECT(1) C. M. Heard
- Re: [tsvwg] Consensus call on ECT(1) Uma Chunduri
- Re: [tsvwg] Consensus call on ECT(1) Ruediger.Geib
- Re: [tsvwg] Consensus call on ECT(1) Kyle Rose
- Re: [tsvwg] Consensus call on ECT(1) Black, David
- Re: [tsvwg] Consensus call on ECT(1) Holland, Jake
- Re: [tsvwg] Consensus call on ECT(1) Ozer, Sebnem
- [tsvwg] 3) "There is a specific test or tests I n… Dave Taht
- Re: [tsvwg] Consensus call on ECT(1) Ranganathan, Ram
- Re: [tsvwg] Consensus call on ECT(1) Paul Vixie
- Re: [tsvwg] Consensus call on ECT(1) Bob Briscoe
- Re: [tsvwg] Consensus call on ECT(1) Adi Masputra
- Re: [tsvwg] Consensus call on ECT(1) Asad Sajjad Ahmed
- Re: [tsvwg] Consensus call on ECT(1) Christoph Paasch
- Re: [tsvwg] Consensus call on ECT(1) Scheffenegger, Richard
- Re: [tsvwg] Consensus call on ECT(1) Lars Eggert
- Re: [tsvwg] Consensus call on ECT(1) Tilmans, Olivier (Nokia - BE/Antwerp)
- Re: [tsvwg] Consensus call on ECT(1) Andreas Petlund
- Re: [tsvwg] Consensus call on ECT(1) Rodney W. Grimes
- Re: [tsvwg] Consensus call on ECT(1) Jana Iyengar
- Re: [tsvwg] Consensus call on ECT(1) Joakim Misund
- Re: [tsvwg] Consensus call on ECT(1) Pete Heist
- Re: [tsvwg] Consensus call on ECT(1) Stuart Cheshire
- Re: [tsvwg] Consensus call on ECT(1) Sebastian Moeller
- Re: [tsvwg] Consensus call on ECT(1) Vividh Siddha
- Re: [tsvwg] Consensus call on ECT(1) David Pullen
- Re: [tsvwg] Consensus call on ECT(1) Campos, Angel, Vodafone Spain
- Re: [tsvwg] Consensus call on ECT(1) Flinck, Hannu (Nokia - FI/Espoo)
- Re: [tsvwg] Consensus call on ECT(1) Karthik Sundaresan
- Re: [tsvwg] Consensus call on ECT(1) Praveen Balasubramanian
- Re: [tsvwg] Consensus call on ECT(1) philip.eardley
- Re: [tsvwg] Consensus call on ECT(1) Tom Henderson
- Re: [tsvwg] Consensus call on ECT(1) Dave Taht
- Re: [tsvwg] Consensus call on ECT(1) K. K. Ramakrishnan
- Re: [tsvwg] Consensus call on ECT(1) Liyizhou
- Re: [tsvwg] Consensus call on ECT(1) Dan Siemon
- Re: [tsvwg] Consensus call on ECT(1) Mohit P. Tahiliani
- [tsvwg] More testing (was: Consensus call on ECT(… Bob Briscoe
- Re: [tsvwg] Consensus call on ECT(1) Roland Bless
- Re: [tsvwg] Consensus call on ECT(1) Mikael Abrahamsson
- Re: [tsvwg] Consensus call on ECT(1) Steven Blake