IETF Logo Mail Archive

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

Michael Welzl <michawe@ifi.uio.no> Wed, 31 May 2023 08:17 UTC

Return-Path: <michawe@ifi.uio.no>
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 483F3C151082 for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 01:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ifi.uio.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 aSYahLZQI4t8 for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 01:17:38 -0700 (PDT)
Received: from mail-out04.uio.no (mail-out04.uio.no [IPv6:2001:700:100:8210::76]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 A2D66C14CE4F for <tsvwg@ietf.org>; Wed, 31 May 2023 01:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ifi.uio.no; s=key2103; h=Message-Id:In-Reply-To:To:References:Date:Subject:Mime-Version: Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=1pP+kwyrGt8Mh6PQTf83IlJfo3fzF1ADYCVLB6snsUY=; b=FuarrbkTZfs/z26/xUGVwwar+O jekLh88kf/K5Hld7jT9p65TNXIQ0sqrkn2xP7u9igGeHe2G28oS7+MvEDjsr05hvamEgIu1vu1rp6 A/KjJGddw1RTGTu4Cb4uYCs5FGBOOcBka8uir1srbMVdH0XmTyTuxpf7POFwQu/Mj6H+vUEQJPRdB YHtNF9FSMEpDZLO2K7dasLP06s4AhPy6thEg/STw7QA2cxdn6N4b01V6xzV8QoQK2rlSedvEuhaRJ WOhFP8BsM1A+XmUCGGQ2n3O4XI/1SqPJsEc1hMDSMqM1pHZCL8ASAwyr4aB3XWMs4KwwvgwEwKaEq 99o80ydw==;
Received: from mail-mx11.uio.no ([129.240.10.83]) by mail-out04.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <michawe@ifi.uio.no>) id 1q4H1S-00CzZN-14 for tsvwg@ietf.org; Wed, 31 May 2023 10:17:34 +0200
Received: from collaborix.ifi.uio.no ([129.240.69.78] helo=smtpclient.apple) by mail-mx11.uio.no with esmtps (TLS1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256) (Exim 4.96) (envelope-from <michawe@ifi.uio.no>) id 1q4H1R-0009A2-1T for tsvwg@ietf.org; Wed, 31 May 2023 10:17:34 +0200
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7517C809-EC64-4DE4-A2CD-5BB3C9910FB3"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Wed, 31 May 2023 10:17:32 +0200
References: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com> <7854c5aa-1779-bbda-a1c5-a148ceb423fc@erg.abdn.ac.uk>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
In-Reply-To: <7854c5aa-1779-bbda-a1c5-a148ceb423fc@erg.abdn.ac.uk>
Message-Id: <E938E9B8-2387-42C3-A05F-43130EFFEA5E@ifi.uio.no>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx11.uio.no: 129.240.69.78 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.69.78; envelope-from=michawe@ifi.uio.no; helo=smtpclient.apple;
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: 6F077D6125471DB9BAC6CFDD8E35F589D9A6C9B3
X-UiOonly: 336911FEDE4F3D37232C3A8A34A5916CB3A1AC22
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/WtzME7IUkagrSshr3Vvrns_aM8M>
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 08:17:43 -0000

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 <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.
> 
> 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> <mailto:martenseemann@gmail.com>
> To:	tsvwg@ietf.org <mailto:tsvwg@ietf.org>
> CC:	tsvwg-chairs <tsvwg-chairs@ietf.org> <mailto: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/ <https://datatracker.ietf.org/doc/draft-kuhn-tsvwg-careful-resume/>
> [2] - https://time.is/Anywhere_on_Earth <https://time.is/Anywhere_on_Earth>

v2.23.0 | Report a Bug | By Email