Re: [tsvwg] The TSVWG WG has placed draft-kuhn-tsvwg-careful-resume in state "Call For Adoption By WG Issued"

Martin Duke <martin.h.duke@gmail.com> Wed, 14 June 2023 18:04 UTC

Return-Path: <martin.h.duke@gmail.com>
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 15CE5C15108A; Wed, 14 Jun 2023 11:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8W017aoU-nfU; Wed, 14 Jun 2023 11:04:10 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 7C89EC15154D; Wed, 14 Jun 2023 11:04:10 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id ada2fe7eead31-4301281573aso1037233137.3; Wed, 14 Jun 2023 11:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686765848; x=1689357848; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IPkh781sQZPEG0VLFHRlKDqG2JpGk/mmZD5euzInblg=; b=I7pZuJ3KPgOe0+6OALeNH2N2NMK3aXE7vCM+FovTdqPlzUpbvv8R7Zh3Bqjah0WGlN b0IDLPEsBhRZviu4LRpQAzrLMEQJwzdZykH+UPrPw+VI8D7mXtWQnVntfXh58fxcSDxA wh27+eUABHGqyZa8M7SGbRApdzQutGxTjtXknTU1hFxVJqBUy5oLuX1hHunnxo4Tyn80 ZTCMDsHRkYuc3nfQWM/kwcWovG7YfKF24ihiPxuM3mPaQXRVUrj9AZNBDmzoegBMCFg7 IC1gtsymupniaqPZZqqrne8AmWhQRLx0SXWkeSLM9qEYIDb3o3BNNqDNwuhqsTbX0HMO osCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686765848; x=1689357848; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IPkh781sQZPEG0VLFHRlKDqG2JpGk/mmZD5euzInblg=; b=C/mf2FnLXNIA+QZ7nuLftdwp/HHwjZR+tkfzkm/BREM65qZ2t0BnmFTmiY7KVZG7c1 fCUQ9BUiWXWE/TovxSZxWFckm8gmyVUKjclTr5LjUqJx8zctNRHKJa16xWtyb0G0zn2M 7tQpSQvSV79ZsH37Uljbe1Nr0sMaQPa+/qd8XjcmkUhuGCBqVR8U9iVtswQFL0+/dUg9 NF98enExxM3s77VNi2DvtkxBnphq+Ayg5pDPPFYucvZ+oSP6bG1RWGY76xB5PUXFZ86v nhEpYl8q+W0S9eM1fKQvcZoG0DgjgB+1vq5FsiQgwWCmGHy6QJMX0oYcz8THBZXKPZGN QL6w==
X-Gm-Message-State: AC+VfDzLVkjGDwUSTHtpCPWpQTswiv/EYS1hr12LWrRM3KSMay2dvok9 BivheMZ+f9ZTVskNYj7stwDXep5kgJ0KrZbwlZKL7MMz
X-Google-Smtp-Source: ACHHUZ4FeGLjFdPekjrVrh7u5IK8Yk6YEckX55smH1ZIJAdUuV/YAox1Qr1y3Lbgl9YnOT2Q/AcCteoBQSBScgGbui0=
X-Received: by 2002:a05:6102:141:b0:43c:89d6:ef6 with SMTP id a1-20020a056102014100b0043c89d60ef6mr7173964vsr.8.1686765848426; Wed, 14 Jun 2023 11:04:08 -0700 (PDT)
MIME-Version: 1.0
References: <168562469147.10864.3031049982682233461@ietfa.amsl.com>
In-Reply-To: <168562469147.10864.3031049982682233461@ietfa.amsl.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 14 Jun 2023 11:03:54 -0700
Message-ID: <CAM4esxTj=Rgt_AEp+XpWgTUbiSRSAUYsAg7bvBE+epVSZeMKsQ@mail.gmail.com>
To: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Cc: draft-kuhn-tsvwg-careful-resume@ietf.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="00000000000036fd9005fe1ac71b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/kAsNs87Rpcn8hImaLQlo_4GD9YY>
Subject: Re: [tsvwg] The TSVWG WG has placed draft-kuhn-tsvwg-careful-resume in state "Call For Adoption By WG Issued"
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, 14 Jun 2023 18:04:15 -0000

I am a bit confused by a 6/1 email with a 5/31 deadline, but I support
adoption, as an individual.

As AD, I confirm that this is in scope for TSVWG, though we may want to
discuss moving this work to CCWG if that is created.

In its current state, the Informational status is correct. However, this
will complicate referencing it in later standards. I'd like the WG to
consider tightening this up enough to be PS.

Martin

On Thu, Jun 1, 2023 at 6:05 AM IETF Secretariat <
ietf-secretariat-reply@ietf.org> wrote:

>
> The TSVWG WG has placed draft-kuhn-tsvwg-careful-resume in state
> Call For Adoption By WG Issued (entered by Gorry Fairhurst)
>
> The document is available at
> https://datatracker.ietf.org/doc/draft-kuhn-tsvwg-careful-resume/
>
> Comment:
> 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)
>
>