[tcpm] At TSVAREA in Philadelphia: The Future of Congestion Control at IETF

Martin Duke <martin.h.duke@gmail.com> Thu, 30 June 2022 22:49 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 66155C1594A9 for <tcpm@ietfa.amsl.com>; Thu, 30 Jun 2022 15:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Status: No, score=-2.106 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Wm_O-eopEVLx for <tcpm@ietfa.amsl.com>; Thu, 30 Jun 2022 15:49:29 -0700 (PDT)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (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 BEB15C15AACB for <tcpm@ietf.org>; Thu, 30 Jun 2022 15:49:24 -0700 (PDT)
Received: by mail-vs1-xe2e.google.com with SMTP id i186so662584vsc.9 for <tcpm@ietf.org>; Thu, 30 Jun 2022 15:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=iUKmCueEdkNQiJd4GUYoNwUeIqW7HT3q25ZPh3PZWrI=; b=ZY94f4x+MQ0HqE6883Ah7Du9uJJUy6MaKe3tdwkMZQwOe9hr042KBmu90V9aKNdS9t TZmeeGfYpju/pAqzHtM3Rp08SYAilPNag/b+WIkXdjODATLwTwqW+B3+ne1a97VA/HeY IlPv/ss8s46KwMEM6piOJInlbSbXQnPmjdxKdl1zc49JtZgkCbPmcRX+pCPuUso3QAsB zyrhOnps2b0jX9nKQXtI9mhzv2xVfgpgJ8WNLYgt3xS2SaniXp06I9Z2GcqMkfIy9Ycs oUIbf3anCpjPHMQLgxbciwbBuRq6oUtgumbVYK870mAvGX+FL4Mnef9QSleSUSfyYJqm e34Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iUKmCueEdkNQiJd4GUYoNwUeIqW7HT3q25ZPh3PZWrI=; b=KBxeE1mAHUXK78oG7nXiDXX+qvEO9paZYHhERd4gBOBFbRMxr2/szrXhTurFSn6v7j oGX47G7V4GGGdim2+jjs9HZIc7Aa+StoslaAYCpNqTgQdHDgSuGTTrIbAXDgkqPFBPu+ oc9IP4HEzAstugLbuI5AmwZrtxi8/qIGVqYBCfem31Bw4srtqQDZW3/H8hByHfKGEvNX cY+pirCckXpd55r3c1rgHckcim956sPs+TEBjvERQIa5cN70jfgNk1LfG2DiV+g4MEC6 rhjRp3VNowOqJcNmQsYyLl1jQtuthHilN2/thzz1TvZ5iHs+cymZ6A8Ka1et1h1Fzgnr bTfw==
X-Gm-Message-State: AJIora+vaezgnUFloj+QmCmRgFpXdQyaesnO0xf2O8ofTEXpT3eKa8fv c+Ps41ltVHoi65OZAQYI80D9Z/MmRGPHvm55QBc=
X-Google-Smtp-Source: AGRyM1ss5VyFKEbnOemQEsjO39xe5Plw/+O/kyeHpvgNIteV/cyTuLpnUpnF6zphuCW3RpTi681JLOxVZVs1YeJShFk=
X-Received: by 2002:a05:6102:23e7:b0:356:91c4:ae with SMTP id p7-20020a05610223e700b0035691c400aemr2981040vsc.61.1656629363326; Thu, 30 Jun 2022 15:49:23 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 30 Jun 2022 15:49:11 -0700
Message-ID: <CAM4esxSPF0a5piWSHOyvuuN-ewBfdMNaE64oj1R+WzGs=L_Ucw@mail.gmail.com>
To: tsv-area@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b9c35105e2b214e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/ZJDiec0XgKtvTtJsCvnP-JB9cyo>
X-Mailman-Approved-At: Fri, 01 Jul 2022 08:44:12 -0700
Subject: [tcpm] At TSVAREA in Philadelphia: The Future of Congestion Control at IETF
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2022 22:49:30 -0000

Hello Transport Enthusiasts,
(bcc: TCPM, QUIC, and ICCRG)

Zahed and I would like to invite you to the TSVAREA meeting at IETF 114
(Monday 13:30 local time), where we will be having a more action-oriented
discussion than usual.

*TL;DR* the way we do congestion control standards is written down in RFC
5033 <https://www.rfc-editor.org/rfc/rfc5033.html>, and is no longer
aligned with how congestion control innovation happens or the family of
transport protocols that use standard congestion control. The IETF is
largely irrelevant to new congestion control deployments. So we'll discuss
a proposal to fix it. This meeting will have some BoF-like elements but it
is not formally a BoF.

In consultation with several stakeholders, we've devised a strategy to
address this:

* Colin Perkins, IRTF chair, has agreed to add at least one chair to ICCRG
(I'm sure Colin would welcome volunteer candidates!). While retaining its
hosting presentations role, there will be renewed emphasis on serving as a
forum to produce experimental RFCs, with a charter update if necessary.

* The Transport ADs are going to consider chartering a new IETF working
group to update the administrative framework for congestion control
standardization, and potentially adopt any proposals that are sufficiently
mature for the standards track. We've formulated a proposed charter. Please
consider it a starting point for discussion.
I ask you to review this document before attending. It answers many of the
questions you may already have.

In Philadelphia, we hope to answer as many of the following questions as
possible, in order:
* Is there rough consensus on the problem to solve?
* Are the deliverables right?
* Are there people willing to take responsibility for those deliverables?
(The meeting is over if the answer is "no")
* Does the proposed charter need changes?
* Is anyone especially excited to chair this WG?

Please come to Philadelphia having thought about these questions and
prepared to answer them. You are also welcome to share thoughts on the
tsv-area list; all other recipients have been Bcced: so that the rest of
the thread will go to only that list. Subscribe if you want to track the

Although charter wordsmithing is somewhat premature, you are also welcome
to file issues and PRs on the github linked above.

See you there,
Martin and Zahed
Your friendly Transport ADs