Re: [tsvwg] Call for Adoption: draft-kuhn-tsvwg-careful-resume - to end May 31st 2023

Michael Tuexen <michael.tuexen@lurchi.franken.de> Wed, 31 May 2023 09:23 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
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 577FBC14CE39 for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 02:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 kwD39eTYS0Ie for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 02:23:36 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A150FC14F74E for <tsvwg@ietf.org>; Wed, 31 May 2023 02:23:35 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:e422:dc49:497b:89]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 46C7F751951B9; Wed, 31 May 2023 11:23:31 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <7854c5aa-1779-bbda-a1c5-a148ceb423fc@erg.abdn.ac.uk>
Date: Wed, 31 May 2023 11:23:30 +0200
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3870E770-38D4-44E6-A563-F537AACAA20B@lurchi.franken.de>
References: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com> <7854c5aa-1779-bbda-a1c5-a148ceb423fc@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Ip2fVO8YQT108sYw2IfaluPvHps>
Subject: Re: [tsvwg] Call for Adoption: draft-kuhn-tsvwg-careful-resume - to end May 31st 2023
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 31 May 2023 09:23:40 -0000

> On 31. May 2023, at 08:45, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> 
> Just a wee reminder that the adoption call ends today, in case you missed the on-list call for people to say if they support this as a TSVWG work item.
I do support it and I'm willing to review it.

Best regards
Michael
> Best wishes,
> Gorry and Marten
> (tsvwg co-chairs) 
> 
> -------- Forwarded Message -------- Subject: [tsvwg] Call for Adoption: draft-kuhn-tsvwg-careful-resume Date: Tue, 16 May 2023 10:22:33 +0300 From: Marten Seemann <martenseemann@gmail.com> To: tsvwg@ietf.org CC: tsvwg-chairs <tsvwg-chairs@ietf.org> 
> 
> Hello TSV WG, 
> 
> During IETF 116 we discussed draft-kuhn-tsvwg-careful-resume [1] and the sense in the room was strong support for adoption (29 people indicated they would support work on this topic, 1 was against).
> 
> Abstract
>     This document specifies careful convergence of Congestion Control
>     (CC), providing a cautious method that enables fast startup for a
>     wide range of connections or reconnections.
> 
>     The method reuses a set of computed CC parameters that are based on
>     the previously observed path characteristics between the same pair of
>     transport endpoints, such as the bottleneck bandwidth, available
>     capacity, or the RTT.  These parameters are stored, allowing them to
>     be later used to modify the CC behavior of a subsequent connection.
>     The document also discusses assumptions and defines requirements
>     around how a sender utilizes these parameters to provide
>     opportunities for a connection to more quickly get up to speed (i.e.
>     utilize the available capacity).  It discusses how these changes
>     impact the capacity at a shared network bottleneck and the safe
>     response that is needed after any indication that the new rate is
>     inappropriate.  The method is expected to be appropriate to IETF
>     transports.
> 
> This is a formal adoption call that will run 2 weeks, ending on May 31st 2023 at 23:59 anywhere on earth [2]. Please respond to this email thread with any comments indicating support or objection. In either case, elucidation of your opinion would be appreciated.
> This email is to confirm the adoption as a TSVWG work item and to ask if there are any other concerns or issues that the working group should consider.
> 
> Best wishes,
> Gorry and Marten
> (tsvwg co-chairs)
> 
> [1] - https://datatracker.ietf.org/doc/draft-kuhn-tsvwg-careful-resume/
> [2] - https://time.is/Anywhere_on_Earth