Re: [Congress] CONGRESS is about ready to go

Bob Briscoe <in@bobbriscoe.net> Thu, 23 February 2023 16:59 UTC

Return-Path: <in@bobbriscoe.net>
X-Original-To: congress@ietfa.amsl.com
Delivered-To: congress@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9772DC1522BD for <congress@ietfa.amsl.com>; Thu, 23 Feb 2023 08:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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=bobbriscoe.net
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 ZD49XG2J0nH0 for <congress@ietfa.amsl.com>; Thu, 23 Feb 2023 08:59:44 -0800 (PST)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C317EC151539 for <congress@ietf.org>; Thu, 23 Feb 2023 08:59:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To: 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=X9RDt8NXEdBgCKY3EnX7cfnBcPma++bISTgHm0bP22U=; b=efnYtGGQtMEzbTLMgUVybrZiu0 fUP9Tvlren/3d21j+/JIB9NxQJclHPw7BAUyG294/NoHavvIRxlBMpvjPvvlHMeImr5Vu65KsgUsj GgQzIpyFHmb3KJ7PpMrkBTQ4HEfq6DoQp0TmgtPkt4JTuTYW2/ZHlZB6Z46h1Hwl4OOSzvVN043Fv Qtkdiiradq5y+t7el14DrVFevUwnOOjN698PAIyszYK6m6c/HdTnNxOVtbezMLz+rrB0f5V5PsYBm +3127hOkFxg30JbCQQlO9d9FXvHO6qUkxtHnnZ5VgBF993ljvx3UwcqWaKMHbisnTUHXzEDyfTvCu Rges0JAA==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:52256 helo=[192.168.1.2]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from <in@bobbriscoe.net>) id 1pVEwd-009Bni-T3; Thu, 23 Feb 2023 16:59:40 +0000
Content-Type: multipart/alternative; boundary="------------d6dcdUINOwOq1ZjjypgSNwly"
Message-ID: <f257f6db-c3c1-3ba4-b99f-cf141c0d90d5@bobbriscoe.net>
Date: Thu, 23 Feb 2023 16:59:38 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
Content-Language: en-GB
To: Matt Mathis <mattmathis@measurementlab.net>
Cc: Martin Duke <martin.h.duke@gmail.com>, congress@ietf.org
References: <CAM4esxQwvo-QNiq_1PDx_z8RvxcJwrMdkb+GJLYJDYw6+_gO2g@mail.gmail.com> <71579EDF-5910-49E4-A76E-3291A133A533@gmail.com> <CAEsRLK_v50CjouSRga2_DQDXOi0rFUVHUGEtL9UJMt+UtnRAiA@mail.gmail.com>
From: Bob Briscoe <in@bobbriscoe.net>
In-Reply-To: <CAEsRLK_v50CjouSRga2_DQDXOi0rFUVHUGEtL9UJMt+UtnRAiA@mail.gmail.com>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/6i6TZUv5J9CZSCdu-9u1cDVCVqw>
Subject: Re: [Congress] CONGRESS is about ready to go
X-BeenThere: congress@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussions about the CONGestion RESponse and Signaling \(CONGRESS\) Working Group" <congress.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/congress>, <mailto:congress-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/congress/>
List-Post: <mailto:congress@ietf.org>
List-Help: <mailto:congress-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/congress>, <mailto:congress-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2023 16:59:48 -0000

Matt,

On 21/02/2023 22:15, Matt Mathis wrote:
> Looks great!   I would like to suggest some more some "in charter" items:
>
>   *  Interactions between congestion control and lower layer
>     algorithms that alter packet timing or thin cumulative ACKs. 
>      Such algorithms are pervasive in half duplex link layers, such as
>     WiFi, where channel arbitration overhead often dominates
>     performance in terms of both latency and bandwidth.
>

[BB] I'd agree that this is a good pair of generalizations to be 
addressed by the WG. Do you envisage writing guidelines for implementers 
of the lower layer algos to be in scope, or only guidelines for 
implementers of end-system algos? My vote would be for both.


>   *  Upper layer or application algorithms that implicitly or
>     explicitly defeat transport layer algorithms intended to protect
>     the network.  An example would be an application that aborts and
>     restarts transport connections on a fixed interval timer,
>     implicitly defeating the transport layer's exponential RTO backoff.
>

[BB] Were you prompted to include this by some current implementation 
attempting this?

I don't think it belongs in a list of things the WG is chartered to work 
on though (a charter isn't normally a place where you would find a list 
of things to /not/ do). I don't think it would even need to be in the 
ICCRG charter - we don't need any (more) research to prove that this 
would cause congestion collapse. It is surely just sthg that the 
proposed RFC5330bis would say is highly dangerous, explain why, and say 
"thou SHALT NOT".


Bob


> Thanks,
> --MM--
> Evil is defined by mortals who think they know "The Truth" and use 
> force to apply it to others.
>
>
> On Tue, Feb 21, 2023 at 10:19 AM Jeff Tantsura 
> <jefftant.ietf@gmail.com> wrote:
>
>     Hi Martin,
>
>     From my point of view, the charter looks good and is ready to be
>     submitted to the IESG.
>     Thanks for the good work, looking forward to working together!
>
>     Thanks,
>     Jeff
>
>>     On Feb 21, 2023, at 9:12 AM, Martin Duke
>>     <martin.h.duke@gmail.com> wrote:
>>
>>     Hello transport enthusiasts,
>>
>>     I'm pleased to announce that all the pieces are in place to move
>>     forward with congress, the working group focused on congestion
>>     control and related topics.
>>
>>     (1) If you haven't already done so, and are interested, please
>>     subscribe to the congress mailing list:
>>     https://www.ietf.org/mailman/listinfo/congress. This is the last
>>     time I'll crosspost (Bcc:) to multiple WG lists, and I encourage
>>     others to stop as well.
>>
>>     (2)  Although the proposed charter has no formal standing at this
>>     time, I'm initiating a "last call". Please have a look and file
>>     issues by the end of this week:
>>     https://github.com/martinduke/congestion-control-charter
>>     The only recent additions to the scope are Fair Queueing and rate
>>     pacing. I'd like to hand this to Zahed, our sponsoring AD, to run
>>     through the IESG process next week.
>>     -- 
>>     Congress mailing list
>>     Congress@ietf.org
>>     https://www.ietf.org/mailman/listinfo/congress
>
>     -- 
>     Congress mailing list
>     Congress@ietf.org
>     https://www.ietf.org/mailman/listinfo/congress
>
>

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/