[Congress] John Scudder's Block on charter-ietf-congress-00-01: (with BLOCK and COMMENT)
John Scudder via Datatracker <noreply@ietf.org> Wed, 15 March 2023 23:07 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: congress@ietf.org
Delivered-To: congress@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF49BC1524B4; Wed, 15 Mar 2023 16:07:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: congress-chairs@ietf.org, congress@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <167892166775.59322.18147185317386549961@ietfa.amsl.com>
Date: Wed, 15 Mar 2023 16:07:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/2x5pTcUoC7HTVzkuy8ANFQeT6Oo>
Subject: [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
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: Wed, 15 Mar 2023 23:07:47 -0000
John Scudder has entered the following ballot position for charter-ietf-congress-00-01: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-congress/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- I found the final paragraph to be odd: ``` CONGRESS will not remain open simply because “in case” further work comes along. ``` (Nit, the "because" in that sentence isn't quite grammatical, I think you can delete it without harm.) Do you mean something like this? NEW: CONGRESS will close once all of its milestones have been completed. If you don't mean that, what *do* you mean? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- - A number of unfortunate linebreaks look to have been introduced in version 01. Please fix these before releasing for IETF review. - 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. - Is there some specific reason for the use of the weak "can" instead of the more intentional "will" in this paragraph? ``` 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. ``` This is your charter, after all. It seems to me that the word should be "will". The same applies to ``` The working group should consider a revision ``` ISTM "should" should be "will".
- [Congress] John Scudder's Block on charter-ietf-c… John Scudder via Datatracker
- Re: [Congress] John Scudder's Block on charter-ie… Zaheduzzaman Sarker
- Re: [Congress] John Scudder's Block on charter-ie… Reese Enghardt