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

[Michael Welzl <[e-mail]>]

Hi,

I do support this as a TSVWG work item. This is in line with the basic rationale of our RFC 9040, just going further, which seems well worth the try.

Cheers,
Michael


> On 31 May 2023, at 08:45, Gorry Fairhurst <[e-mail]> 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.
> 
> 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 <[e-mail]> <mailto:[e-mail]>
> To:	[e-mail] <mailto:[e-mail]>
> CC:	tsvwg-chairs <[e-mail]> <mailto:[e-mail]>
> 
> 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/ <https://datatracker.ietf.org/doc/draft-kuhn-tsvwg-careful-resume/>
> [2] - https://time.is/Anywhere_on_Earth <https://time.is/Anywhere_on_Earth>