Re: [tsvwg] Call for Adoption: draft-kuhn-tsvwg-careful-resume

Joerg Deutschmann <joerg.deutschmann@fau.de> Wed, 31 May 2023 19:51 UTC

Return-Path: <joerg.deutschmann@fau.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 14195C14CE42 for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 12:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=fau.de
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 I1P8P5ueB-oC for <tsvwg@ietfa.amsl.com>; Wed, 31 May 2023 12:51:15 -0700 (PDT)
Received: from mx-rz-3.rrze.uni-erlangen.de (mx-rz-3.rrze.uni-erlangen.de [IPv6:2001:638:a000:1025::16]) (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 A7B8AC14CE2E for <tsvwg@ietf.org>; Wed, 31 May 2023 12:51:13 -0700 (PDT)
Received: from mx-rz-smart.rrze.uni-erlangen.de (mx-rz-smart.rrze.uni-erlangen.de [IPv6:2001:638:a000:1025::1e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-rz-3.rrze.uni-erlangen.de (Postfix) with ESMTPS id 4QWfyj1Rfyz27kF for <tsvwg@ietf.org>; Wed, 31 May 2023 21:51:09 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fau.de; s=fau-2021; t=1685562669; bh=NGMGpSp0YZdKcaML+F3H2qwaVfSIT8vWJbiZ5mKNrd8=; h=Date:Subject:To:References:From:In-Reply-To:From:To:CC:Subject; b=tsqyKqztm6KtrF+2ft5N6qvmb41YS5IUhIDwWNv4+hqDqd120/Bssu0ZsmHROF4ri ewwTYpKDpC+TbWPpDF7AX378xxbI41tdrP0XkO79ZXXO3qpbsKv2AUFJG6OL5oSpZX lpiD+pI3eqOx4CbVAQ/W+kyEZfbTyNy1PhRxKn7VXRG+yvv6OCjG+c9CzwFWwBUQJ+ WdIP123Un4B0DzRPF8FwEaBegqfQ/SCyfOEWpOlrrIb5kwarRjcw6xeVmNMA9M4ECT tvkx3qQR1HSTa6t76LWTT38GexefD5+LBRqzrntqvAPkCOW9ys8AuOpJLLpfH3U8TH 24HPjd3ZG60qQ==
X-Virus-Scanned: amavisd-new at boeck1.rrze.uni-erlangen.de (RRZE)
X-RRZE-Flag: Not-Spam
X-RRZE-Submit-IP: 131.188.37.210
Received: from faui7s0.informatik.uni-erlangen.de (faui7s0.informatik.uni-erlangen.de [131.188.37.210]) by mailhub.rrze.uni-erlangen.de (Postfix) with ESMTP id 4QWfyf3yz1z25vX for <tsvwg@ietf.org>; Wed, 31 May 2023 21:51:06 +0200 (CEST)
Received: from [192.168.178.35] (dynamic-077-002-120-064.77.2.pool.telefonica.de [77.2.120.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by faui7s0.informatik.uni-erlangen.de (Postfix) with ESMTPSA id 43F0240F2456 for <tsvwg@ietf.org>; Wed, 31 May 2023 21:51:06 +0200 (CEST)
Message-ID: <4c081db9-e3eb-c985-3870-44bfe1e5117e@fau.de>
Date: Wed, 31 May 2023 21:51:02 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
To: tsvwg@ietf.org
References: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com>
Content-Language: en-US
From: Joerg Deutschmann <joerg.deutschmann@fau.de>
Organization: Friedrich-Alexander-Universität Erlangen-Nürnberg
In-Reply-To: <CAOYVs2o1X8ZyL+bB=nWdHXYRWTswa6JoMtRu1gLrSGb9Oz08XQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms010300040404020700070803"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/z0fTZb3suDAlH8vnBinyGdw9QJU>
Subject: Re: [tsvwg] Call for Adoption: draft-kuhn-tsvwg-careful-resume
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 19:51:19 -0000

Dear all,

to confirm my statement made at IETF 116: I think this is a useful draft 
and I plan to contribute (both simulations and prototype code) and 
collaborate with others.

Best regards,
Joerg


On 16.05.23 09:22, Marten Seemann wrote:
> 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>