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

Wes Hardaker <wjhns1@hardakers.net> Thu, 06 November 2025 12:03 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 EC3B68442E17 for <dns-at-ietf@mail2.ietf.org>; Thu, 6 Nov 2025 04:03:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_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 b3MGSbHr63e1 for <dns-at-ietf@mail2.ietf.org>; Thu, 6 Nov 2025 04:03:38 -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 59ECA8442E12 for <dns-at-ietf@ietf.org>; Thu, 6 Nov 2025 04:03:38 -0800 (PST)
Received: from localhost (rtr-guestwired.meeting.ietf.org [31.133.144.1]) by mail.hardakers.net (Postfix) with ESMTPA id 596E520ABC; Thu, 06 Nov 2025 04:03:36 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 596E520ABC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1762430617; bh=XLSDMZ/p9fgsl9SBL4rUzJ6TCxxB0EfRtZRygWsrMiw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hX10xZ3KoCh4QJR2edFz3XNavfAffjRIWJb5BVBam1JMkfS3aCYwEvf0etLxNEETR LgIutIgXJYRbC5s6DcikVWLIqe9cMwFxtNwEWcZnDasnnxp6Qr38uXKVYJhfIzG23+ 1giVezvlOehWDxOX94D0WlNdie0JmHvykcyYJYIE=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Petr Špaček <pspacek@isc.org>
In-Reply-To: <f2cebc5e-2f52-4eca-acbf-54d9180bd8eb@isc.org> ("Petr Špaček"'s message of "Wed, 5 Nov 2025 19:56:55 -0500")
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> <f2cebc5e-2f52-4eca-acbf-54d9180bd8eb@isc.org>
Date: Thu, 06 Nov 2025 04:03:35 -0800
Message-ID: <ybl4ir7bc6g.fsf@wx.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: K25QVEJ223KXJXGM2SYSECNXPXY7VH6D
X-Message-ID-Hash: K25QVEJ223KXJXGM2SYSECNXPXY7VH6D
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
CC: 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/ri9B9Vmp3sd_EIYSW9l61CpFRm8>
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>

Petr Špaček <pspacek@isc.org> writes:

Thanks Petr,

A quick follow on:

> Can we try do BCPs @ DNS-OARC for couple years and see how it goes?

[disclaimer: I'm a big fan of DNS-OARC generally, but the questions
below are really how to make this potentially work if this is the
direction chosen]

1. DNS-OARC doesn't yet have a publication stream at all, aside from a
blog, which can certainly be remedied by creating one.  Certainly it
fits within their current description under the "Information Sharing"
category.  My recollection is that occasionally (very rare) do have
"membership only" meeting slot; how would those potentially affect a
published BCP if they were related as that differs from the always-open
model of the IETF?

2. If DNS BCPs were to be written at DNS-OARC, then we may have to
reference external publications from our IETF streams at times.  This
already happens so seems possible.  But do you foresee any complications,
especially if we have cases of timing dependencies, or, worse, circular
dependencies that are handled right now through internal clustering?

3. How do we ensure enough IETF folk are participating in the external
body (which is membership driven though has open lists)?  Or do you feel
that operators are the ones to write BCP and thus protocol experts
aren't as needed?  (that wasn't intend to be as leading of a question as
it came out, but I'll leave it anyway)

4. How do we ensure DNS-OARC publications are widely recognized as
authoritative?  This is really a problem for all new bodies to widely
publicize their intent to create new authoritative streams, and isn't
really specific to OARC.

[5. I actually had one more but now I've forgotten it...]

-- 
Wes Hardaker
Google