[Congress] Éric Vyncke's Block on charter-ietf-congress-00-00: (with BLOCK and COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 09 March 2023 10:01 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 BAC47C14F74A; Thu, 9 Mar 2023 02:01:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke 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.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <167835606174.14540.17002253585147910246@ietfa.amsl.com>
Date: Thu, 09 Mar 2023 02:01:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/MIwLIin0p43KQG24_-Ti72MFAlY>
Subject: [Congress] Éric Vyncke's Block on charter-ietf-congress-00-00: (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: Thu, 09 Mar 2023 10:01:01 -0000
Éric Vyncke has entered the following ballot position for charter-ietf-congress-00-00: 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: ---------------------------------------------------------------------- Indeed, the world has changed since TCP is no more *the* protocol, so this work is welcome. I think that this text needs a rewrite: `However, if the working group has adopted further work in accordance with the guidelines above, it can recharter, add milestones for them, and continue until that work is complete.` Isn't the above putting the cart before the horses ? I.e., why not doing the usual process of rechartering *before* adopting an IETF draft ? (this of course does not prevent the WG to work/discuss an individual draft) Another point is about what will be the deliverables of this WG ? The current charter appears to be more suited for a directorate (doing reviews of WG documents) than for a WG (publishing documents). ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- One comment about `empirical evidence of safety` as safety is rather vague (or do you mean information security or network stability ?). "Empirical" is also rather vague, should it rather be "experimental" ? I second Erik Kline's comment on ### P7/Bullet 1. The charter is also rather long, but this is a matter of taste.
- [Congress] Éric Vyncke's Block on charter-ietf-co… Éric Vyncke via Datatracker
- Re: [Congress] Éric Vyncke's Block on charter-iet… Zaheduzzaman Sarker
- Re: [Congress] Éric Vyncke's Block on charter-iet… Eric Vyncke (evyncke)
- Re: [Congress] Éric Vyncke's Block on charter-iet… Zaheduzzaman Sarker
- Re: [Congress] Éric Vyncke's Block on charter-iet… Eric Vyncke (evyncke)
- Re: [Congress] Éric Vyncke's Block on charter-iet… Zaheduzzaman Sarker
- Re: [Congress] Éric Vyncke's Block on charter-iet… Reese Enghardt