Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplusplus-12.txt
Martin Duke <martin.h.duke@gmail.com> Wed, 18 January 2023 22:08 UTC
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EABC15153F; Wed, 18 Jan 2023 14:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2IwP2i6ZdIG; Wed, 18 Jan 2023 14:08:08 -0800 (PST)
Received: from mail-ua1-x92e.google.com (mail-ua1-x92e.google.com [IPv6:2607:f8b0:4864:20::92e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2780C15155F; Wed, 18 Jan 2023 14:08:08 -0800 (PST)
Received: by mail-ua1-x92e.google.com with SMTP id i23so38816ual.13; Wed, 18 Jan 2023 14:08:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GXVYFmxr/D6HAHM1K/hKiR9Tx4DTeyZGBLVvL+qmwP4=; b=c9vkf6ab7jzEFtAFye36A0xbi8vM3HhFyiKRyyQ6JHKWodCymUQGz6E7eirzEcqzvy aRRL4lLFoGvQV+3+i6Vx9D7cQjC7xpU+/EJ9rzRCawnRyrRtl4T8uynAnA/pa7ewXOiQ frHS+rPSQgviNwIuYTFmSq11jQ9fTuuP68NOzSmk+La9VfjuJK9lu2pBxnI7tUb/FPln yiIugKS31yanObNDZGZAmDheYCn3+wgKdY143tgTu4oUdlDoKeNOI9l2qCEadevleoRR 1bshN1svqi6drvcqyCm0EDJZ3illfS3EHaVHbCQaJqUbZAjH9dbtW2Q75mHF4s1mLUz0 UTJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GXVYFmxr/D6HAHM1K/hKiR9Tx4DTeyZGBLVvL+qmwP4=; b=1qio3GsX2C2x8k6SxU5IQqSxtmoWkoXfeqGAWjtr4WTycT3C8Tzy4ckYIF8yecSxNd Cvj2CnPKv5ba3siN23yQf0Nw5u3JK5yLMnyZAGgi3QHb0AwG76B4DdFx3cp2h2RBt6/b 52L2qrQkAdqY3PB9s1DPHuwMztYFi28M6MiZY8KQkT7xak+8aF8wij/7/SlS1T8fx07B HL1/1LP8zIPc4Y7U75S5nj0PgxlDiWFffH77T4FfpupAknfXZ637jMqP1gELEYj7tywQ G7GT6krFuPbbXLWbUh63E35RL9yWbYsxZJTqKz1rqqTIEGw21wmHGdiZs6All3enG3kJ yhnA==
X-Gm-Message-State: AFqh2kpeU0yZRqIDE5r7iofKqIOu3V1E8TU0tjZQ0WRhY2KQ5FqGneNt QM8BHh+GRtJalPxfmgH6iSpgNCrZ6r+ygjePP6GSAOEL
X-Google-Smtp-Source: AMrXdXvk4Ai0/3JXac9vLPhVQJjic6WJMVNmTa87y1JjgoiZTAHuOT6Nhaz4qdkI7VJ9Cztw6+hASRCuOgubEgncbjA=
X-Received: by 2002:ab0:156f:0:b0:582:7c28:7c72 with SMTP id p44-20020ab0156f000000b005827c287c72mr1024679uae.107.1674079686615; Wed, 18 Jan 2023 14:08:06 -0800 (PST)
MIME-Version: 1.0
References: <167330410669.3759.12442685855520700837@ietfa.amsl.com> <CADVnQymKgWE+Jx8-eTw=1nZmpgb2tAYbSUxxKVm=Rgw6W8jmVw@mail.gmail.com> <CADVnQy=W+_nOk9rPPuV0yqqh1CxNz_J_d53tL40Er462CafDaw@mail.gmail.com> <CAL=F3y+9CNBX1+LSAG+TzvW_Hc8KgZOdurNB6x7CF5ROMZ_Gsg@mail.gmail.com> <CD063F96-045E-427F-8DA5-EF1399F16066@lurchi.franken.de>
In-Reply-To: <CD063F96-045E-427F-8DA5-EF1399F16066@lurchi.franken.de>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 18 Jan 2023 14:07:46 -0800
Message-ID: <CAM4esxT=DW48ewfDu9my3DigCJfusjyEt8mWAu5yd085KRxgyA@mail.gmail.com>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
Cc: Praveen Balasubramanian <pravb.ietf@gmail.com>, tcpm@ietf.org, i-d-announce@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000be68f05f2910d0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/aup0c3bWfOiQdJjWYbj264KivoQ>
Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplusplus-12.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2023 22:08:11 -0000
While, if it were me, I might attempt to capture the nuance Neal describes about the Linux default and Google, I do not object to deleting it entirely. On Sun, Jan 15, 2023 at 1:10 PM Michael Tuexen < michael.tuexen@lurchi.franken.de> wrote: > > On 12. Jan 2023, at 00:47, Praveen Balasubramanian <pravb.ietf@gmail.com> > wrote: > > > > I see, thanks Neal for the clarification. I then suggest that we > eliminate this deployment experience line completely because its not with > the proposed algorithm in this document and that it will confuse new > developers as to why the document suggests using pacing with L=infinity > when the default in Linux contradicts it. > > > > Any concerns with just removing this line entirely? > In general I think providing data points precisely is a good thing, > even if they are inconclusive. > > I think the document can still suggest to use L = infinity, if pacing is > used. > Also using L < 2 is not optimal. > > The only unclear point is what value of L to use if you do not use pacing. > Maybe the threshold of 8 is not a hard value for all traffic patterns, > link characteristics and implementations. > > Best regards > Michael (as an individual) > > > > On Wed, Jan 11, 2023 at 2:07 PM Neal Cardwell <ncardwell@google.com> > wrote: > > Martin pointed out out-of-band that my various attempts at explaining > this point have not been clear, so let me try to express this a different > way: > > > > For about the last decade the Linux TCP default has been: [ CUBIC + > Hystart + L=infinity + unpaced ]. This is because the commonly deployed > qdiscs for the major Linux distributions do not implement pacing. > > > > For 2013-2016 Google/YouTube Linux TCP ran with: [ CUBIC + Hystart + > L=infinity + paced ]. This was using the fq qdisc to implement pacing. > > > > best regards, > > neal > > > > > > On Tue, Jan 10, 2023 at 10:24 AM Neal Cardwell <ncardwell@google.com> > wrote: > > Looks like there is still one significant word in the "Deployments and > Performance Evaluations" section that needs to be updated to be accurate. > > > > Existing draft-ietf-tcpm-hystartplusplus-12 text: > > > > There has been over a decade of experience using the > > original Hystart algorithm for all TCP connections in the > > Linux operating system with pacing enabled and an > > actual L = infinity. > > > > Suggested text: > > > > There has been over a decade of experience using the > > original Hystart algorithm for all TCP connections in the > > Linux operating system with pacing disabled and an > > actual L = infinity. > > > > I mentioned the rationale in the "Re: [tcpm] Changes to > draft-ietf-tcpm-hystartplusplus after WGLC" thread on Nov 29: > > > > > https://mailarchive.ietf.org/arch/msg/tcpm/CSzCgxxSLrO9u63dymyyxqB6bD4/ > > > > cheers, > > neal > > > > > > On Mon, Jan 9, 2023 at 8:53 PM <internet-drafts@ietf.org> wrote: > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > This draft is a work item of the TCP Maintenance and Minor Extensions WG > of the IETF. > > > > Title : HyStart++: Modified Slow Start for TCP > > Authors : Praveen Balasubramanian > > Yi Huang > > Matt Olson > > Filename : draft-ietf-tcpm-hystartplusplus-12.txt > > Pages : 9 > > Date : 2023-01-09 > > > > Abstract: > > This document describes HyStart++, a simple modification to the slow > > start phase of congestion control algorithms. Traditional slow start > > can overshoot the ideal send rate in many cases, causing high packet > > loss and poor performance. HyStart++ uses a delay increase heuristic > > to find an exit point before possible overshoot. It also adds a > > mitigation to prevent jitter from causing premature slow start exit. > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-tcpm-hystartplusplus/ > > > > There is also an htmlized version available at: > > https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-hystartplusplus-12 > > > > A diff from the previous version is available at: > > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-tcpm-hystartplusplus-12 > > > > > > Internet-Drafts are also available by rsync at rsync.ietf.org: > :internet-drafts > > > > > > _______________________________________________ > > tcpm mailing list > > tcpm@ietf.org > > https://www.ietf.org/mailman/listinfo/tcpm > > _______________________________________________ > > tcpm mailing list > > tcpm@ietf.org > > https://www.ietf.org/mailman/listinfo/tcpm > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm >
- [tcpm] I-D Action: draft-ietf-tcpm-hystartplusplu… internet-drafts
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Neal Cardwell
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Neal Cardwell
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Praveen Balasubramanian
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Neal Cardwell
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Gorry Fairhurst
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Michael Tuexen
- Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplu… Martin Duke