[dns-at-ietf] Re: Discussion: big groups vs small, focused groups

Paul Wouters <paul@nohats.ca> Wed, 22 October 2025 17:23 UTC

Return-Path: <paul@nohats.ca>
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 345587A7469D for <dns-at-ietf@mail2.ietf.org>; Wed, 22 Oct 2025 10:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=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=nohats.ca
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 RnBqP8tiy66w for <dns-at-ietf@mail2.ietf.org>; Wed, 22 Oct 2025 10:23:58 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.85]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 370147A74693 for <dns-at-ietf@ietf.org>; Wed, 22 Oct 2025 10:23:58 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4csGH02wtcz5JD; Wed, 22 Oct 2025 19:23:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1761153836; bh=o2nbEParjrudo0gwUV1bqcha4/Vf4fuYp3iE9vfFf4A=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=fEYpIZpy8C7rNpB8RxKpHMCuWWqwVROnDCBISP1WfM0Bc9+sXIb1AdXKqcl6cymxv bZDq39ngrDX28HLQdEw+tgNJ13lWCTB2E5xkoQLzGYuEhmD2ZL6qI79rG6Uo9zeevf MF3J/GzzYzlwUzGrejyZIQVGVChRDq3YdauDf9lQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id hKa-3ZBKA052; Wed, 22 Oct 2025 19:23:55 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 22 Oct 2025 19:23:55 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 4283C1778DD0; Wed, 22 Oct 2025 13:23:54 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 3EBE31778DCF; Wed, 22 Oct 2025 13:23:54 -0400 (EDT)
Date: Wed, 22 Oct 2025 13:23:54 -0400
From: Paul Wouters <paul@nohats.ca>
To: Wes Hardaker <wjhns1@hardakers.net>
In-Reply-To: <yblldl574tx.fsf@wx.hardakers.net>
Message-ID: <923be35d-fe70-0443-4ea2-8c0752f290a3@nohats.ca>
References: <ybl5xci8pp7.fsf@wd.hardakers.net> <7C7F3527-766A-42CF-ABC7-D7F1B1609770@fugue.com> <1b1708ad-8e77-4194-9047-2fb6058b28cd@lear.ch> <yblo6q9639k.fsf@wd.hardakers.net> <c879ee9b-cf32-4480-a8d1-982cd8ae11e0@lear.ch> <ybl5xch628j.fsf@wd.hardakers.net> <61bcd7e8-0a5e-469b-8ba6-17690e4eebc8@lear.ch> <7286F00A-8085-4322-AE15-50CBD9791130@rfc1035.com> <197ac10c-0fc6-e29e-92aa-220cb8dc5516@nohats.ca> <yblldl574tx.fsf@wx.hardakers.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-ID-Hash: T3N3EZJFQWVD4TGFQH7MONLKAUL5VJL2
X-Message-ID-Hash: T3N3EZJFQWVD4TGFQH7MONLKAUL5VJL2
X-MailFrom: paul@nohats.ca
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
CC: Paul Wouters <paul=40nohats.ca@dmarc.ietf.org>, dns-at-ietf@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dns-at-ietf] Re: Discussion: big groups vs small, focused groups
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/Q0BNnCuQhl9021Wbxej3lhfh6Lc>
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>

On Mon, 20 Oct 2025, Wes Hardaker wrote:

> One clarifying question:  If the primary point of a split in half is to
> increase the speed of some of the drafts, how would the split
> functionally accomplish this if the agenda time between the two groups
> remained the same?

Like I said in my previous email, having a more strict "issue
discussion" process and less "presenting new ideas" time should free
up time I think.

I also believe multiple lists will reduce the distractions of the "one big
list with all DNS topics" that kinda always seem to burn / drown out other
threads.

> Or do you envision dnsop maintaining the current
> two-session reservations and adding a third for your dev group?

Either could be possible depending on the workload after documents would
get (re)assigned to either group.

> Or do
> you think the split itself will increase the time for some drafts
> because the weighting will not be 50/50 and, if so, then one group will
> end up being slower to get things done right while the other (the
> operational side) becomes faster?

I would expect dnsop to become faster. Whether or when they could go
back to one session instead of two, I couldn't predict at this point.

> TL;DR: I understand the rational for the split but not how it itself
> would achieve the goals.

I think its more the contained focus on the mailinglists that would
create this. Recent example is the subtag discussion which would be
fine for the "devel" group, but wouldn't take time and focus on out
of dnsop. But I also think it does need to go hand in hand with
chairs steering concrete draft open issues per email thread, and keep
slow feeding this into dnsop.

Paul