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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 31 May 2023 06:45 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2BA47C15106B for <tsvwg@ietfa.amsl.com>; Tue, 30 May 2023 23:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2Cul8rzSnyfQ for <tsvwg@ietfa.amsl.com>; Tue, 30 May 2023 23:45:17 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0E844C151065 for <tsvwg@ietf.org>; Tue, 30 May 2023 23:45:16 -0700 (PDT)
Received: from [] (fgrpf.plus.com []) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7C5431B000E8 for <tsvwg@ietf.org>; Wed, 31 May 2023 07:45:10 +0100 (BST)
Content-Type: multipart/alternative; boundary="------------OMkIPbfFEklHtViiApSFqfYH"
Message-ID: <7854c5aa-1779-bbda-a1c5-a148ceb423fc@erg.abdn.ac.uk>
Date: Wed, 31 May 2023 07:45:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
References: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
In-Reply-To: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com>
X-Forwarded-Message-Id: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/QdArNFkVNRQ0hWqTH_nRPDLtqF4>
Subject: [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 06:45:21 -0000

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.

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).

     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

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 

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