[DNSOP] draft charter for new DNS WG

Jim Reid <jim@rfc1035.com> Mon, 02 November 2026 11:05 UTC

Received: from shaun.rfc1035.com (shaun.rfc1035.com [46.235.229.98]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 8AFA846; Mon, 02 Nov 2026 11:05:50 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=none; spf=pass (mx.ietf.org: domain of jim@rfc1035.com designates 46.235.229.98 as permitted sender) smtp.mailfrom=jim@rfc1035.com; dmarc=none
Received: from smtpclient.apple (gromit.rfc1035.com [IPv6:2a00:a600:60a:1::169]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 1DA47260E79; Mon, 02 Nov 2026 11:05:41 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.10\))
Message-Id: <D8883F08-769B-4218-B96A-E74D2F9F4E9F@rfc1035.com>
Date: Mon, 02 Nov 2026 11:05:40 +0000
To: Working Group DNSOP <dnsop@ietf.org>, int-area@ietf.org
X-Mailer: Apple Mail (2.3826.700.81.1.10)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (shaun.rfc1035.com); Mon, 02 Nov 2026 11:05:41 +0000 (UTC)
X-Spamd-Bar: ------------
Message-ID-Hash: YYS6DXQ4QKS76LJJ4VQF6RMMMBKUY5OT
X-Message-ID-Hash: YYS6DXQ4QKS76LJJ4VQF6RMMMBKUY5OT
X-MailFrom: jim@rfc1035.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-dnsop.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Reply-To: Working Group DNSOP <dnsop@ietf.org>
Subject: [DNSOP] draft charter for new DNS WG
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6oQgF_HjtCrXzBwtKrq_uwl5W4g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Here's the draft charter for the proposed WG which will focus on DNS protocol maintenance and update, leaving dnsop to do DNS Operations. If/when there's consensus on the proposed charter, the dnsop charter will need to be updated. Which should be a no-brainer: just delete the 2 paragraphs that mention DNS protocol maintenance.

The name-to-be-decided WG is responsible for maintenance, updates and extensions to the DNS protocol. This includes defining, updating and deprecating DNS protocol elements, their wire formats and their processing rules. The WG is also responsible for documenting and updating the DNS architecture.

DNS operations are out of scope for the name-to-be-decided WG.

The IESG will decide whenever some aspects of DNS protocol activities are best carried out in other WGs. When this happens, those topics will be out of scope for the name-to-be-decided WG. 

The name-to-be-decided WG will engage with relevant WGs and other appropriate organisations  especially for WG adoption and Last Calls. It will instruct IANA whenever changes are needed to its DNS-related registries.

Milestones

* March 2027: Submit “Signalling a Zone Cut to Nowhere in the DNS” to the IESG.