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

Neal Cardwell <> Mon, 02 May 2022 15:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8E3E5C15E3EC for <>; Mon, 2 May 2022 08:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -22.6
X-Spam-Status: No, score=-22.6 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, RCVD_IN_DNSWL_HI=-5, 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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VNJNqM8CKEum for <>; Mon, 2 May 2022 08:00:34 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::830]) (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 (Postfix) with ESMTPS id C9C01C159A23 for <>; Mon, 2 May 2022 08:00:34 -0700 (PDT)
Received: by with SMTP id t11so11232758qto.11 for <>; Mon, 02 May 2022 08:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E0RS0nFz4p+dQr/0vg69yAQ+iJYRiDeGty8KLLD/CnU=; b=Br0Bga+rtopqrujyCts2/bpvdpHqt6RkqRC+IKWuI8b808NjrYSNekso41hNb1oslf xSwigiT+5y36Dihmx07gS51A6gietHdr2jc9UY33h7dEyNI29AGmzB+TXQ2H4IB48x3X ZjArMc+YINBOMoVL8nysvJS993AyiXHuVuMNNV8j8ntB7ARJMr6rLw0GK2HNxtIxVH8b V2KdIMAoM6KqLabZe9Yj4uhkdrMFdm7DJJRZ7F7di15ptfAi55t9ObLUkAk+nrhIEjdO yl6LnJKmdO+OybUkeFpROS6IXA45WOWDqLVh+b1xPEvlCSXZr0/Ebuye4b/jq6EPqzZc kNag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E0RS0nFz4p+dQr/0vg69yAQ+iJYRiDeGty8KLLD/CnU=; b=npaacXXX+jQwWprhdUp5OGuAAAjhKn+LbHpv7n4/0MJCWiiZ1qH39qG825BEpY36Tp mau1hdMUTPJ9DPFSHMUZTBYyM7IjYhpmbHW7pEo0biDc+u9Trw0hzX2zakum9O8hTYao l1ZuYB2wCeZqEur7XCFCHmM8bw2elS+AJ9CETPUgx6ifMgbxp6PL5nHEvNVNr4WPXdns rLS7O5HihYCTl/7jGb60yVfVocMphSQ6ov/jVU3ij8kqEWUiFfWGRHzm8rCObh/J61B1 lxhDgUB2g0mtOZZpIPZNp8EEPHTqWMlswfa/t0qYsfqJ472AUvtwCuJEAydZlgXi2oky ptTw==
X-Gm-Message-State: AOAM530MZ9P8/rjXXvDFqpu10ZWoIQXLfUAGOki0eqynwtsGFPA+h/Bg s6n0SSoz22jxbxPtNbBfzJyxkTmN8bu9XciBxGgq0g==
X-Google-Smtp-Source: ABdhPJwDvO70Dqijw5m/h5CEXt6A687+OThfOcApUwvlhD5SNOQkJWJ1DiEuqDw93bBJ0qqG4N4oZnQWWHbQTdC08gk=
X-Received: by 2002:ac8:578a:0:b0:2e1:a0d2:c3a with SMTP id v10-20020ac8578a000000b002e1a0d20c3amr10791622qta.261.1651503633449; Mon, 02 May 2022 08:00:33 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Neal Cardwell <>
Date: Mon, 02 May 2022 11:00:17 -0400
Message-ID: <>
To: Michael Tuexen <>
Cc: tcpm IETF list <>, Randall Stewart <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [tcpm] WGLC for draft-ietf-tcpm-hystartplusplus-04
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 May 2022 15:00:38 -0000

On Wed, Apr 13, 2022 at 4:19 PM Michael Tuexen <> 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
> 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,