Re: [Congress] John Scudder's Block on charter-ietf-congress-00-01: (with BLOCK and COMMENT)

Reese Enghardt <ietf@tenghardt.net> Thu, 16 March 2023 15:44 UTC

Return-Path: <ietf@tenghardt.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 79890C1516F8; Thu, 16 Mar 2023 08:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=tenghardt.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 FxVBK5jS-LV1; Thu, 16 Mar 2023 08:44:12 -0700 (PDT)
Received: from mail.hemio.de (mail.hemio.de [136.243.12.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 B8F19C1522C4; Thu, 16 Mar 2023 08:44:10 -0700 (PDT)
Received: from user.client.invalid (localhost [136.243.12.180]) by mail.hemio.de (Postfix) with ESMTPSA id 32423B2; Thu, 16 Mar 2023 16:43:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tenghardt.net; s=20170414; t=1678981448; bh=QSbqU0FqXCYp1LSXNMFquzZCV5yv0klkUhQvz8EmiD8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=VJZFutZZvjW/ZVn9CfDQ3jWFNtD1LWz2KV4xW2F3vCWwmJNH2+Odz1u2gDq2M+Z20 Iide9t9WUPDpPVc5VfBDIfsTQhod2JCBHkXpC+i3G7BPC164X60ItJKVxqqeBnw5Pz a35LknXcyLppqigKx8PN2R9lVzNu5JLrlXhfcZR0UaWBV9GvBDbgiru4RFz3jVo4HY KiHRp2qHZDINVMlLnd1vvq1kd5fuvJkSfqgSxkXfnOa5RqNorZl3vj2KFiQgDNvbQW 2GDlcqkDkrmMbxZUgRVqZuNrC4tu379X5PWJxzAEzlO4qOztXu8EM5XEokFHKz4P++ UiMOkZ41elrnQ==
Message-ID: <52e9ce3b-3636-f8ac-ac61-66db6ea3b4b4@tenghardt.net>
Date: Thu, 16 Mar 2023 08:43:55 -0700
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-US
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, John Scudder <jgs@juniper.net>
Cc: The IESG <iesg@ietf.org>, "congress-chairs@ietf.org" <congress-chairs@ietf.org>, "congress@ietf.org" <congress@ietf.org>
References: <167892166775.59322.18147185317386549961@ietfa.amsl.com> <CB732DEA-EB6C-4782-9104-B7F356C98678@ericsson.com>
From: Reese Enghardt <ietf@tenghardt.net>
In-Reply-To: <CB732DEA-EB6C-4782-9104-B7F356C98678@ericsson.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/yX5Owl8Y-fUIPCVjqHCDarDe10M>
Subject: Re: [Congress] John Scudder's Block on charter-ietf-congress-00-01: (with BLOCK and COMMENT)
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, 16 Mar 2023 15:44:17 -0000

Hi John,

Thanks for the review.

I created a PR on the charter Github to address the issues raised: 
https://github.com/martinduke/congestion-control-charter/pull/34


Please see inline for further replies:

On 3/16/23 01:21, Zaheduzzaman Sarker wrote:
>> - I agree with Paul that the WG acronym seems likely to lead to future
>> confusion. I encourage you to find another; my recent experience with CAN ->
>> CATS is that it's not that hard to make this change even late in the game.
> We can consider that if it becomes too much of issue..

I am in favor of choosing a different name, too. We have a few proposals 
in this Github issue, which should probably be reopened: 
https://github.com/martinduke/congestion-control-charter/issues/18


>> ```
>> The CONGestion RESponse and Signaling working group (CONGRESS) can review some
>> of the impediments to early congestion control work occurring in the IETF, and
>> can generalize transport in this area from TCP to all of the relevant transport
>> protocols.
>> ```
>>
>> - Is there some specific reason for the use of the weak "can" instead of the
>> more intentional "will" in this paragraph?
> Not to me at least. Chairs and proponents can say more.

I agree that "will" is a better fit for this paragraph, and I updated 
the text accordingly in the PR.


Best,
Reese