Re: [tcpm] [tsvwg] CONGestion RESponse and Signaling (CONGRESS) charter

Bob Briscoe <ietf@bobbriscoe.net> Wed, 09 November 2022 14:47 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7644C1522D0; Wed, 9 Nov 2022 06:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 4wdtiDyTkoeV; Wed, 9 Nov 2022 06:47:53 -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 F2BBEC14CE3F; Wed, 9 Nov 2022 06:46:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To: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=4iGmFe9yJpvrNFxo8XIa9TvjbuWNU/MtN1nO4jXsiZw=; b=mZf1DUrXg2EA2Gr4DPMPm6zdS8 5wT/7C71S7LnBnXp9wdnuD2HQx5R6CmOg+FND/UV6q045uL9J8TG98LiEE8Du8WPqYZnLnUgp/weu 0pde8HnJ5+jOX2rV+Q6cbcjvwxnCLfUVhghGQKN8njwdShmVg/MJmKd35GM8PBenmtKssagmlSJKp DPtvBhiuwanLkwlNWNYJgc9etidXJqC8qXdkvdB0okx/GuxMvuiITHXfdeOQWo4/y7di/JcJ1BISo igWjz91259dQbglbj7Gs0gP4bx2FxbiDttOsls5OktNrc7F1lIq/fS0pzCjuJJCvG8c3Cl/5dDQU3 sq8eqplQ==;
Received: from dhcp-8852.meeting.ietf.org ([31.133.136.82]:55666) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from <ietf@bobbriscoe.net>) id 1osmLE-00EYeI-L7; Wed, 09 Nov 2022 14:46:06 +0000
Message-ID: <36110731-130c-7c74-706a-19ca8d6a1bf8@bobbriscoe.net>
Date: Wed, 09 Nov 2022 14:46:05 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Subject: Re: [tcpm] [tsvwg] CONGestion RESponse and Signaling (CONGRESS) charter
Content-Language: en-GB
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Martin Duke <martin.h.duke@gmail.com>, tsv-area@ietf.org, tsvwg <tsvwg@ietf.org>, IETF QUIC WG <quic@ietf.org>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
References: <CAM4esxQFn6V0OK6KddFEyuOLTKAxUS1+HjO_NvCNaCqD5SpSew@mail.gmail.com> <46aaf74d-b623-0408-5d57-818011c1b11e@bobbriscoe.net> <c387ed77-f917-7a25-c572-2bd3e71f904d@bobbriscoe.net> <203BE851-B78A-4196-8C2E-99D0E23D49DE@gmail.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
In-Reply-To: <203BE851-B78A-4196-8C2E-99D0E23D49DE@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
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/quic/zz2xfNX7drHNqUqQbN-jpa00Wds>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 14:47:57 -0000

Jonathan,

On 09/11/2022 09:44, Jonathan Morton wrote:
>> On 9 Nov, 2022, at 11:10 am, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>>
>> 2/ Another question: Why 'and Signalling' in the title?
>> Other than the title and response to congestion signals, the charter doesn't say anything about signalling itself.
>> If, say, there were more work on tunnelling ECN or something, would tsvwg take that on, or congress?
> "Congestion signalling" refers not only to the mechanisms that allow congestion to be detected by transports, but the algorithms (from drop-tail overflow upwards) which generate those congestion signals to control transports' demand on network resources.
>
> The former aspect, referring to the wire protocols, may well be properly handled by TSVWG and/or individual protocol WGs (eg. TCPM, QUIC, etc).  The latter aspect, however, is more general in terms of protocol and more specific to congestion control itself.  I think "… & Signalling" would refer very naturally to text mentioning AQM in the body of the charter.

[BB] You're right. So this sort-of implies that 'congestion signalling' 
is a rather ambiguous phrase to have in the title. If both meanings will 
be handled by this group, then fine. But if only the generation of 
congestion signals is in scope, the title might need to be re-worked.


Bob

>
>   - Jonathan Morton

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/