[Last-Call] Re: Last Call: <draft-hardaker-dns-wgs-at-ietf-06.txt> (Community considerations on DNS WG structures at IETF) to Historic RFC
Michael Richardson <mcr+ietf@sandelman.ca> Sun, 12 April 2026 19:56 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: last-call@mail2.ietf.org
Delivered-To: last-call@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2B2FBDAD63C4 for <last-call@mail2.ietf.org>; Sun, 12 Apr 2026 12:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776023787; bh=uNoMermqgBc59/h3ezjRa/zGAmZFDd/API77DNOX8mc=; h=From:To:Subject:In-Reply-To:References:Date; b=koCXONvxZEFShNyEBpH1bDz0gmA/NlYs3XCelVK4bOKGmMgYNwe5OYwhz+TKgrWjl 9Csy2S0j3NMkwRKBeAmO0htEQXeMNHoZfzJty5MZAubZqhO+/wusgQ+uHarMYRVjhY eeBrTLQHDMIOgUEc4buXwzPPkG9wqN9YB0yMfHFE=
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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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 (2048-bit key) header.d=sandelman.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 b0hvAyuufEhQ for <last-call@mail2.ietf.org>; Sun, 12 Apr 2026 12:56:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8D0ADDAD63BC for <last-call@ietf.org>; Sun, 12 Apr 2026 12:56:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 321A41801A for <last-call@ietf.org>; Sun, 12 Apr 2026 15:56:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id ITkrQLLg1Zmq for <last-call@ietf.org>; Sun, 12 Apr 2026 15:56:24 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1776023784; bh=lcGaaTcuxbTprDgv54zGbJqJSC1CDWnOYsRVptkLTkM=; h=From:To:Subject:In-Reply-To:References:Date:From; b=ZmdrU1K6jU3Yn+BSvzaUxwEwsNyHHV8dQkwex1gte4XzkPWy6NvlNW5M3I26HQILH hP+Zki7mA/VZSQ3c2xIsFPfZbbPwl0oMmY40y3KMpuJ4bWDYqHZerWCwlEJJEyyoRT +zCubJj6a+yHbe5pX+VMhY/Sz31T+mQnIP36JsxlNL1OPc933H8TXWsASBm0B+qcbs SSvKlUYRpPKhaKCbLTVAQzCgfO4pu5VgZz8OklYgDoVUMSXCR0+28gUsM6W5amRaEv tkpRZuwYMXT0UxSOlc6Wh8S44dgyCLxfUeksor0KO8PUm98N+SJu4XQ4evbPdGz9wd 0NUyko3PEszEg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8DD5518019 for <last-call@ietf.org>; Sun, 12 Apr 2026 15:56:24 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 89D081CD for <last-call@ietf.org>; Sun, 12 Apr 2026 15:56:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: last-call@ietf.org
In-Reply-To: <CABcZeBN-8wTecQauRE38QB8SkJOiDL+=qj5K66D10Tcq5jCzkQ@mail.gmail.com>
References: <177583799702.85121.468194718179666209@dt-datatracker-647897bf7-7f2k5> <CABcZeBN-8wTecQauRE38QB8SkJOiDL+=qj5K66D10Tcq5jCzkQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 12 Apr 2026 15:56:24 -0400
Message-ID: <31014.1776023784@obiwan.sandelman.ca>
Message-ID-Hash: 4VKQSOIWTZ27UKQEB22Y7CGC7IM7ZNKN
X-Message-ID-Hash: 4VKQSOIWTZ27UKQEB22Y7CGC7IM7ZNKN
X-MailFrom: mcr+ietf@sandelman.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Last-Call] Re: Last Call: <draft-hardaker-dns-wgs-at-ietf-06.txt> (Community considerations on DNS WG structures at IETF) to Historic RFC
List-Id: IETF Last Calls <last-call.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/Lmfe_wi2HvAeAkjXg41RT3xYz08>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Owner: <mailto:last-call-owner@ietf.org>
List-Post: <mailto:last-call@ietf.org>
List-Subscribe: <mailto:last-call-join@ietf.org>
List-Unsubscribe: <mailto:last-call-leave@ietf.org>
I wanted to again thank Wes, Joe and Lars for this work. We do not do this
kind of thing often enough.
Cleaning CC.
I don't agree with all the conclusions of the documents.
(In particular, I would enfranchise DNS-OARC and the RIR's various dns-wg more)
Eric Rescorla <ekr@rtfm.com> wrote:
> I do not believe that this document should be published as an
Ditto.
> plenary -- but I do not think that this kind of background artifact
> should be published as an RFC, especially when, as here, there's not
> even a claim that the contents reflect IETF consensus. It's just
> a report of some consultation.
I think the IESG could also conclude that it shouldn't be published, but it
might be that asking the IESG to ballot it is also a good way to get the IESG
to think about this problem as a whole and endorse a specific plan.
So, I agree that this should not be published as an RFC, but rather turn into
some kind of wiki/overview-of-DNS organization web page.
I'm not sure if there was a better way to get to this place.
My impression over 25 years of DNS* WGs is that requests for new RR requests
come in waves. I think we are just in mid-peak for this "decade"{%%}
Getting new RRs used to be pretty much impossible until the proper
unknown-RR support got deployed. RFC4025 was among the
first "new" ones... as I recall, we spun up an entire WG to do that.
That was ... very challenging at the time.
I concur with the impossibility of scheduling things like DNSDISPATCH.
(I still think we screwed up the ALLDISPATCH experiment)
But I think that actually, that's the feature of it.
The point of DNSDISPATCH is to be a Gong Show{%}. But, more polite.
(Note how "running jokes" is actually part of our informal process)
I would **prefer** it did not take up plenary week time.
I acknowledge EKR's point that virtual interim meetings do not get the same
mix of people, but I think it's okay in this case.
Not everyone need be there; if a WG/BOF is recommended, then it gets prime
scheduling time. Like SIPPING did for SIP 20 years ago, the point was to
deal with the many really bad ideas from genuinely well intentioned people
without taking up everyone's time.
I am not a fan of the decadal cycling of DNS WG names.
DNSEXT,DNSIND,DNSNEXT... and this seems like another such cycling.
Thus I'd like to keep DNSOP.
---
{%}- https://en.wikipedia.org/wiki/The_Gong_Show
The Gong Show is an American amateur talent contest created by Chuck
Barris in 1976 and franchised by Sony Pictures Television to many
countries. Each performer was evaluated by a panel of three celebrity
judges who could strike a gong to end a performance they disliked. A small
cash prize has typically been awarded to each episode's winner. The Gong
Show is known for its absurdist humor, and often features amateurish, racy
or questionable performers interspersed with more legitimate acts. The
actual competition was typically secondary to the outlandish acts, and the
series is also known for its free-form style which featured various
interruptions, digressions and running jokes.
{%%}- what happened to the pyschohistorians^Wsociologists who used to examine us? Maybe
there is thesis here.
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
^---child of two sociologists, one being an SPSS/360 alpha user
Sandelman Software Works Inc, Ottawa and Worldwide
** My working hours and your working hours may be different. **
** Please do not feel obligated to reply outside your normal working hours **
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Phillip Hallam-Baker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Pete Resnick
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… S Moonesamy
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Martin Thomson
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Michael Richardson
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Joe Abley
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Salz, Rich
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Phillip Hallam-Baker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Wes Hardaker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Eric Rescorla
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Wes Hardaker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Wes Hardaker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Joe Abley
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… mohamed.boucadair
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Eric Rescorla
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Phillip Hallam-Baker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Pete Resnick
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Peter Thomassen
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Pete Resnick
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… mohamed.boucadair
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… S Moonesamy
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Salz, Rich
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Phillip Hallam-Baker
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Adrian Farrel
- [Last-Call] Re: Last Call: <draft-hardaker-dns-wg… Warren Kumari