Return-Path: <tjw.ietf@gmail.com>
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 65AB1869698B
	for <dns-at-ietf@mail2.ietf.org>; Sun,  9 Nov 2025 11:19:38 -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, FREEMAIL_FROM=0.001,
	HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
	SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key)
	header.d=gmail.com
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 q9FmTH6-zRBM for <dns-at-ietf@mail2.ietf.org>;
	Sun,  9 Nov 2025 11:19:37 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com
 [IPv6:2a00:1450:4864:20::531])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by mail2.ietf.org (Postfix) with ESMTPS id 2914B869697B
	for <dns-at-ietf@ietf.org>; Sun,  9 Nov 2025 11:19:37 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id
 4fb4d7f45d1cf-640bd9039fbso4788044a12.2
        for <dns-at-ietf@ietf.org>; Sun, 09 Nov 2025 11:19:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1762715976; x=1763320776; darn=ietf.org;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=6WSeqbXXTXxFE/yi5Aoaj1RlDXIvQkXhZkl7/+1fy8A=;
        b=CkDiDsJ/zOdAQsz5N0NBMKYtQhsP40r+uVjMmw+TemBueuv57e7oLvbD3PMt3aFhaW
         4zf6P9IbbrJLuheMrsT/PmpERGIaSQY707Sz8a6X4oOhauWwHhm3UXzhHrv/8bunh8m6
         kMjmSp7RnD772UpK7FQ08D+9SEfkvz8CPd90CXXJrs2Bn+fei+R+1ABLFwjrIcGJHp4X
         FVjo0OIlgTGySGXRDE/D5vpproHh1d+Eu78OMai9tKf0foE2bBpNgxBOIYl2ja8998Vf
         KX1TX2QGBgZZg/JjDH6hpaiEMBXwJzmCSBDtQiMmjb8VNy7vM24xfzcyg2fRwgG+UO2u
         ZaWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1762715976; x=1763320776;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=6WSeqbXXTXxFE/yi5Aoaj1RlDXIvQkXhZkl7/+1fy8A=;
        b=C4j0icWo2g+bc5hh7z4QJ4FScNCaYtGsEtczmiL/uF6fX9UbCiHcZfzIGHLgkl9vgk
         iPlIp81T2ohTKMzExRmryD2rf1kjPvAuQawW/NTiNIpgzZm61IHAlsX1SusQPa9qVLNH
         xatnuwB8+NA9rUwLiZccAE+ApIlpyMdhwu3M1lYUZ5a1vFzX5GYKwFVfU5lyHd45qWnZ
         DE/5yAWzWjwiKV/Dqj0c4Z6AhiJR0FYi05hKQ/3PXOJEIJ4FBH/FbLLQjTW0vPuvrS32
         tIC2NiDafHrS1YkpfpRIdnoM/mTkaWgW6SMUF++/0UT69zoGaF2Xvi4gO25x2t+8B2zc
         GL9g==
X-Gm-Message-State: AOJu0YycB7N6X6aJjTjNbbY4pf++RwTTJl4AfyTQAbnKSv+xOD36uTzf
	bkzTQpMXq8vf/vGnqCs5eVVRomXrNYrbqKMT9s+/NGYAZzPwrJ3mUcTB/HGbiwarort/8Cj54zj
	5BVUo4LvBSOs14BxI8XiGvFF7ISvyBaRZ4w==
X-Gm-Gg: ASbGncvRt0V/0ofPHX1QUSTzgwiDyn34/dpBjhjoK15QSg/g9NMFF1Ay27mE6YJwQih
	kQbiIj8+AynOmdIJ3SxLQv+KUrsxqmO2h34zC0q2ZXzXSpl0mKZizDgczcfUBvimEol1HPTkTWx
	BKDb+CBwsg/JKL9PgiDTXboO77EWbSbU1Keh4MHw0qZQEw9NAZTGXv5KIqzcMmFxurpuW+OntnO
	irxexR0Z75pBvIEZBmx25eH+orFIexCARDKSiI4NCquzvMgJCijIYesuUTQJlSLbOEp65heeWJk
	uFY7SVTOoy8feV1amDOejiJDLTLdqHViFIrluJC6bW1UkDQ=
X-Google-Smtp-Source: 
 AGHT+IHvfuOoolWDCLPpycABrBRBfvSyz9X3vot+wgM1CLqWJMYoWUwLSGk4oFsT8FwYqAsjpUIn4X5SIcGDhz6pO54=
X-Received: by 2002:a05:6402:21d5:b0:640:b247:fee6 with SMTP id
 4fb4d7f45d1cf-6415e825a5cmr4232985a12.38.1762715975843; Sun, 09 Nov 2025
 11:19:35 -0800 (PST)
MIME-Version: 1.0
References: <984e69a4-06f8-47a7-8b62-8dc2533994ff@isc.org>
 <32DBCB21-3ECF-4AC0-86DF-CBDE629B9BA1@nohats.ca>
 <m1vIAF1-0000N4C@stereo.hq.phicoh.net>
In-Reply-To: <m1vIAF1-0000N4C@stereo.hq.phicoh.net>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 9 Nov 2025 14:19:24 -0500
X-Gm-Features: AWmQ_bn86viXoHGEH7EqYUASfMcbznrpQS8UWTl5te0IOR7JSUS6lRU8pvNsmPA
Message-ID: 
 <CADyWQ+FBkL32g_9yir-rKYPY+pPp9THL0LbgKZLYca24QD_2xA@mail.gmail.com>
To: Philip Homburg <pch-dns-at-ietf@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary="00000000000094822306432e4bb9"
Message-ID-Hash: 6R2VY2JVUAEWJBSSYNKJYBA3VF4PJRJG
X-Message-ID-Hash: 6R2VY2JVUAEWJBSSYNKJYBA3VF4PJRJG
X-MailFrom: tjw.ietf@gmail.com
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, Paul Wouters <paul=40nohats.ca@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5Bdns-at-ietf=5D_Re=3A_managing_workload_within_and_across_DNS_WG?=
	=?utf-8?q?s?=
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/vUBIzpj38PpsGbAds4fhvjiT8Ec>
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>

--00000000000094822306432e4bb9
Content-Type: text/plain; charset="UTF-8"

Paul W made a good point about .onion, .ZZ, .internal, etc - they sucked up
an amazing amount of WG time and energy.
Not for lack of trying, but it really points to a truth folks hate to
accept:

The Universe abhors a dingy painted bikeshed


As for advancing documents lacking implementations, we as chairs were given
guidance that it's fine to adopt a document
which does not currently have implementations, and are very happy to let it
drop if the implementations don't appear.
I see this in some of the v6 groups.

I will admit I personally held up the advancement of dns-structured-error
for more than a year waiting for more discussion on implementations
that we knew were done, but tucked away.  I am sure the authors were not
happy about this.
During our DNSOP chairs calls we regularly talked if certain drafts had
interest in implementing.
I found it useful to listen to Benno's guidance on these matters.

An early mistake we made in dprive was publishing DNS-over-DTLS where there
were no implementations, and the authors were *not interested* in working
on an implementation or attempting to work with developers on creating even
prototypes.

I feel like ADD had some similar issues with a few of their documents, but
my memory is hazy.

tim

(memories may be hazy)

--00000000000094822306432e4bb9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div><div class=3D"gmail_default" style=3D"=
font-family:monospace">Paul W made a good point about .onion, .ZZ, .interna=
l, etc - they sucked up an amazing amount of WG time and energy.</div><div =
class=3D"gmail_default" style=3D"font-family:monospace">Not for lack of try=
ing, but it really points to a truth folks hate to accept:<br><br></div></d=
iv><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><div><di=
v class=3D"gmail_default" style=3D"font-family:monospace">The Universe abho=
rs a dingy painted bikeshed</div></div></blockquote><div><br></div><div><di=
v class=3D"gmail_default" style=3D"font-family:monospace">As for advancing =
documents lacking implementations, we as chairs were given guidance that it=
&#39;s fine to adopt a document</div><div class=3D"gmail_default" style=3D"=
font-family:monospace">which does not currently have implementations, and a=
re very happy to let it drop if the implementations don&#39;t appear.=C2=A0=
</div><div class=3D"gmail_default" style=3D"font-family:monospace">I see th=
is in some of the v6 groups.=C2=A0</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D"=
font-family:monospace">I will admit I personally held up the advancement of=
 dns-structured-error for more than a year waiting for more discussion=C2=
=A0on implementations</div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace">that we knew were done, but tucked away.=C2=A0 I am sure the a=
uthors were not happy about this.=C2=A0=C2=A0</div><div class=3D"gmail_defa=
ult" style=3D"font-family:monospace">During our DNSOP chairs calls we regul=
arly talked if certain drafts had interest in implementing.=C2=A0 <br>I fou=
nd it useful to listen to Benno&#39;s guidance on these matters.=C2=A0</div=
><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div><di=
v class=3D"gmail_default" style=3D"font-family:monospace">An early mistake =
we made in dprive was publishing DNS-over-DTLS where there were no implemen=
tations, and the authors were *not interested* in working on an implementat=
ion or attempting to work with developers on creating even prototypes.=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br><=
/div><div class=3D"gmail_default" style=3D"font-family:monospace">I feel li=
ke ADD had some similar issues with a few of their documents, but my memory=
 is hazy.=C2=A0=C2=A0</div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:mo=
nospace">tim</div></div><div class=3D"gmail_default" style=3D"font-family:m=
onospace"><br></div><div class=3D"gmail_default" style=3D"font-family:monos=
pace">(memories may be hazy)</div></div>

--00000000000094822306432e4bb9--

