[dns-at-ietf] Discussion: how do we decide when a carefully chartered, narrow WG is needed

Wes Hardaker <wjhns1@hardakers.net> Mon, 10 November 2025 23:32 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dns-at-ietf@mail2.ietf.org
Delivered-To: dns-at-ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 16F3F8732585 for <dns-at-ietf@mail2.ietf.org>; Mon, 10 Nov 2025 15:32:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KT3YFrpMOUiW for <dns-at-ietf@mail2.ietf.org>; Mon, 10 Nov 2025 15:32:09 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8C91C8732580 for <dns-at-ietf@ietf.org>; Mon, 10 Nov 2025 15:32:09 -0800 (PST)
Received: from localhost (unknown [10.0.0.9]) (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 mail.hardakers.net (Postfix) with ESMTPSA id 6026420AFA for <dns-at-ietf@ietf.org>; Mon, 10 Nov 2025 15:32:08 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 6026420AFA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1762817528; bh=Ie8AjIXylRkOJ8YMMnVkNQaYsow1IXbJqePHDdoixVo=; h=From:To:Subject:Date:From; b=l05f8Dzq9pnS4QnK4hJqEGUrsnANKn1ldr7QvZFD15rKrkGKFSAWD8sZES3G9VrDz fe+QfHP4m0db3Y8DGWuGoODlcvuXhYAAIDU3Qd3BUG8v66zIzsjw2Bcbxf4SsJ0kt4 LOWK4N+q3Klf27dVE/Qgr9tnBEt3aUbhW2EO+geA=
From: Wes Hardaker <wjhns1@hardakers.net>
To: dns-at-ietf@ietf.org
Date: Mon, 10 Nov 2025 15:32:08 -0800
Message-ID: <yblo6p9ihvr.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: UVNP4W2RZXAVIWUY5NTD75V2GXYN5APY
X-Message-ID-Hash: UVNP4W2RZXAVIWUY5NTD75V2GXYN5APY
X-MailFrom: wjhns1@hardakers.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dns-at-ietf] Discussion: how do we decide when a carefully chartered, narrow WG is needed
List-Id: "This list is to discuss the structure of DNS work in the IETF, and DNSOP in particular." <dns-at-ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-at-ietf/ZVI3Ob8fSjbJ3ZCU2_NcRmanfDM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-at-ietf>
List-Help: <mailto:dns-at-ietf-request@ietf.org?subject=help>
List-Owner: <mailto:dns-at-ietf-owner@ietf.org>
List-Post: <mailto:dns-at-ietf@ietf.org>
List-Subscribe: <mailto:dns-at-ietf-join@ietf.org>
List-Unsubscribe: <mailto:dns-at-ietf-leave@ietf.org>

How should the IETF (and thus IESG) decide when a new WG is needed
(e.g. include but are not limited to deleg, add, and dprive), vs
adopting a draft in an existing group?

- Should it be based on expected time to accomplish a goal?
- Should it be based on the level of effort required?
- Should it be based on the amount of discussion time that is expected?
- Should it be based on the complexity of the problem to be solved?

Is there a clear, crisp line that could be drawn?  Most likely there is
no way to define a crisp line, but can we provide guidance about how to
best break down the problem to at least create a sensible starting point
for a discussion that hopefully fits most of the time?

-- 
Wes Hardaker
Google