[dispatch] Ketan Talaulikar's No Objection on charter-ietf-dispatch-03-00: (with COMMENT)

Ketan Talaulikar via Datatracker <noreply@ietf.org> Tue, 02 June 2026 17:29 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from [10.244.11.174] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 45A34F96E5B2; Tue, 2 Jun 2026 10:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780421399; bh=qAUaNTQPjBhX363Tte9KM08kIMXqmnv0JgW3AC7OFXs=; h=From:To:Cc:Subject:Reply-To:Date; b=zNTEVwMPZJ786NtImNOc1VYPZYTDFdTvo34wk7HpQWVDDstLImN5Hm0ypbmzqaPSu pGw4uG6eJBZXYSI38x0XMjhiuOSjSv+nwihABLlCBVV/XGUdg47kAfQOXAHIR/QQJl ZKzBStOPowyI3qtCTHWwb07djSow2JRgzfGTv+gE=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ketan Talaulikar via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.65.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178042139903.2384387.6758730153240403574@dt-datatracker-5b4c8598b5-4ztf9>
Date: Tue, 02 Jun 2026 10:29:59 -0700
Message-ID-Hash: BZKHGDMOJIYBNXJPS3KMV3SX7SIGF3PV
X-Message-ID-Hash: BZKHGDMOJIYBNXJPS3KMV3SX7SIGF3PV
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dispatch-chairs@ietf.org, dispatch@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Ketan Talaulikar <ketant.ietf@gmail.com>
Subject: [dispatch] Ketan Talaulikar's No Objection on charter-ietf-dispatch-03-00: (with COMMENT)
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/a08d6xClnhgQ-WS-UD87J6lytwY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

Ketan Talaulikar has entered the following ballot position for
charter-ietf-dispatch-03-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-dispatch/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for putting this together and I support the idea of introducing some
flexibility for alternate work flows besides dispatching only during the IETF
plenary meeting week sessions.

Now I know that DISPATCH did process some documents, but I wonder if that is
something that should be done away with going forward so the WG focus is purely
on guiding and dispatching new work.

"The DISPATCH working group may, with the agreement of the relevant
ART, SEC, or WIT ADs, process and have as work items simple administrative
documents for media-type specifications and other IANA actions. Otherwise,
the DISPATCH working group does not process documents."

Why not remove this? Can't it be done elsewhere?