Re: [tcpm] WGLC for draft-ietf-tcpm-hystartplusplus-04

Yuchung Cheng <ycheng@google.com> Tue, 03 May 2022 20:03 UTC

Return-Path: <ycheng@google.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 81BABC1594B1 for <tcpm@ietfa.amsl.com>; Tue, 3 May 2022 13:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 pAhqMyWHTQIo for <tcpm@ietfa.amsl.com>; Tue, 3 May 2022 13:03:06 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 D3843C157B5B for <tcpm@ietf.org>; Tue, 3 May 2022 13:03:06 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id k2so24768373wrd.5 for <tcpm@ietf.org>; Tue, 03 May 2022 13:03:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5Mz24qj5k1NnyQwJ7OSDHINh+01tnvG4zHlOIxjPtPc=; b=czfQMDvlTDCE7HqR1vTX3EmFe3G7N7YOaHH1x5owbBhrtWNOu4PjGy/3g6WFwHNJta 92haOZa/EaNsHl3DzsoHOOfQFhYXO2yb9Xv8JJUN1Xu+Sb6/rW71aDr1kxnDUKj/jKfu zYp4UI+6iIXgP5GhTUYMXj1rcV/obBrPF0dMFxOPSG7W9xW7F3BKQl7x0JGmGZk1GlBN vYK3wozMLQG9asaWFg1EpqWi5ixOZob1q4cduwO4AQApwST47bLc7afHHKGCr4sEmj+w Yy7Ozvu6mAR/EjW1GQ2hlDGDzPRvoUDAxQguFZJpExoKYqLKrfgV9eEkZbt9jAJNOXDJ kRkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5Mz24qj5k1NnyQwJ7OSDHINh+01tnvG4zHlOIxjPtPc=; b=Rwx9QoVtKBpQd1qGo9f80T5v8pgVs2ILgQ5avTk2RMHp0TuexOxzUymPnL2yAhF5tN OrXA/NOsj+k6w4eUKz+CIsUDSqy+PYGMzf3WJo6sVb9OA9V4Y+5Nca9o3tevjC94NWoI ZPUC3ZyH8v56G6gL7vT82Ty/cgAjSJ59QLH5tM1EXff1/2CtQ1HodWGYdxNDKraxOCDF /W5228UesS8xcmA6wBY5Qhmus0ZUJNvL+P8a4mk0GWTlRWOQXBJAAyrvUg4SbgTE+xS4 4oeyFCM7SirUmvQr44t5jj4ZtLBJ8Ugkd5vQD5cuATwXLpQekBXNPsfYUddReJdIFo/R 4XQw==
X-Gm-Message-State: AOAM531yW8dzxV+hAKDvQXty7q/087PdzFDQJdJTKaO4qr28BreLDg5G iHB2Hk8CpBtMd6X86AJOlCQa4YzwgxTwrkKokqss3A==
X-Google-Smtp-Source: ABdhPJztIAtljROysE6Nks67XYkEfoIGEu0RZZXsKUwd7b6kAjnz8yJjHPxxLYiPhv2+IFA4toqIGbKk99XDY7wu+Hw=
X-Received: by 2002:a05:6000:170a:b0:20c:5e04:af27 with SMTP id n10-20020a056000170a00b0020c5e04af27mr9774574wrc.547.1651608184613; Tue, 03 May 2022 13:03:04 -0700 (PDT)
MIME-Version: 1.0
References: <66261F55-7780-402B-954E-6D7A1AB3F3C5@fh-muenster.de> <CADVnQykw_JJMYHVD=zPHv6X4it9njXWiA-6sPYAKU4wGRQtmuQ@mail.gmail.com>
In-Reply-To: <CADVnQykw_JJMYHVD=zPHv6X4it9njXWiA-6sPYAKU4wGRQtmuQ@mail.gmail.com>
From: Yuchung Cheng <ycheng@google.com>
Date: Tue, 03 May 2022 13:02:28 -0700
Message-ID: <CAK6E8=dKQcqjX7XyRER+Wzmh9ggBcYip23LNPtDo19Yc7FD0yA@mail.gmail.com>
To: Neal Cardwell <ncardwell=40google.com@dmarc.ietf.org>
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tcpm IETF list <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000275b6705de20ff0f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/qM6M1JbCgIkSmTRr2VJPS9h81vU>
Subject: Re: [tcpm] WGLC for draft-ietf-tcpm-hystartplusplus-04
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 03 May 2022 20:03:07 -0000

Small suggestions to be more precise on actual implementation

5. Deployments and Performance Evaluations
As of the time of writing, HyStart++ as described in draft versions 01
through 04 was default enabled for all TCP connections in the Windows
operating system for over three years *with an actual L = 8*. The original
Hystart has been default-enabled for all TCP connections in the Linux
operating system using the default congestion control module CUBIC
([RFC8312]) for a decade *with an infinite L*.

Personally I think having the "L" ABC constraint would hinder hystart
performance.It's maybe too late to modify the actual algorithm hence I ask
the implementation description can be more precise.

On Mon, May 2, 2022 at 8:00 AM Neal Cardwell <ncardwell=
40google.com@dmarc.ietf.org> wrote:

> On Wed, Apr 13, 2022 at 4:19 PM Michael Tuexen <tuexen@fh-muenster.de>
> wrote:
> >
> > Dear all,
> >
> > this e-mail starts the working group last call for
> draft-ietf-tcpm-hystartplusplus-04.
> >
> > The WGLC runs until Friday, May 6th 2022.
> >
> > Please send any comments, including indications to support this document,
> > to the TCMP mailing list by then.
> >
> > The ID is available at
> > https://www.ietf.org/archive/id/draft-ietf-tcpm-hystartplusplus-04.html
> >
> > Best regards
> > Michael
>
> I am generally supportive of this draft advancing, but do want to put
> a word in about the application-limited issue Randall mentioned again
> earlier in this thread. After the algorithm exits slow start, it seems
> like it is likely to oscillate between:
>
> (a) application-limited periods that cause low RTT samples and a
> re-entry into slow start ("if current round's minRTT drops below
> baseline indicating that HyStart exit was spurious"), and then
>
> (b) non-application-limited periods that will cause a re-exit of
> slow-start and re-entry into CSS.
>
> It seems like the algorithm should either be adjusted to avoid this,
> or this expected oscillation dynamic should be documented.
>
> best regards,
> neal
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>