[Gendispatch] Benjamin Kaduk's No Objection on charter-ietf-gendispatch-01-00: (with COMMENT)
Benjamin Kaduk via Datatracker <noreply@ietf.org> Thu, 02 December 2021 06:10 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: gendispatch@ietf.org
Delivered-To: gendispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EE33A0AE5; Wed, 1 Dec 2021 22:10:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: gendispatch-chairs@ietf.org, gendispatch@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <163842543502.20877.4835523817199553759@ietfa.amsl.com>
Date: Wed, 01 Dec 2021 22:10:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/PSfbi9GDXwuYB3NlOhGkPS-kgis>
Subject: [Gendispatch] Benjamin Kaduk's No Objection on charter-ietf-gendispatch-01-00: (with COMMENT)
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2021 06:10:35 -0000
Benjamin Kaduk has entered the following ballot position for charter-ietf-gendispatch-01-00: No Objection 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-gendispatch/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Proposed new work may be deferred in cases where GENDISPATCH does not have enough information for the chairs to determine consensus. New work may be rejected in cases where there is not sufficient interest in GENDISPATCH or the proposal has been considered and rejected in the past, unless a substantially revised proposal is put forth, including compelling new reasons for accepting the work. Can work be rejected because the WG thinks it is a bad idea? (Is that supposed to be part of "not sufficient WG interest"?) The existence of GENDISPATCH does not change the IESG's responsibilities and discretion as described in RFC 3710. Work related to the IAB, IETF LLC, IRTF, and RFC Editor processes is out of scope. It's a little bit hard to square "out of scope" with a willingness to request that those bodies consider taking up work on a given topic.
- [Gendispatch] Benjamin Kaduk's No Objection on ch… Benjamin Kaduk via Datatracker
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Pete Resnick
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Lars Eggert
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Tony Rutkowski
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Lars Eggert
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Benjamin Kaduk
- Re: [Gendispatch] Benjamin Kaduk's No Objection o… Lars Eggert