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

IETF Secretariat <ietf-secretariat-reply@ietf.org> Thu, 01 June 2023 13:04 UTC

Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A56FC152575; Thu, 1 Jun 2023 06:04:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: draft-kuhn-tsvwg-careful-resume@ietf.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 10.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <168562469147.10864.3031049982682233461@ietfa.amsl.com>
Date: Thu, 01 Jun 2023 06:04:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/JCsrd1RFpwiM54gxqBZR8hfbozY>
Subject: [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
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: Thu, 01 Jun 2023 13:04:51 -0000

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)