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, 2 Nov 2026 11:05:40 +0000
To: Working Group DNSOP <dnsop@ietf.org>,
 int-area@ietf.org
Message-ID-Hash: YYS6DXQ4QKS76LJJ4VQF6RMMMBKUY5OT
Precedence: list
Reply-To: Working Group DNSOP <dnsop@ietf.org>
Subject: [DNSOP] draft charter for new DNS WG
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/dnsop/6oQgF_HjtCrXzBwtKrq_uwl5W4g>

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.=20

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 =E2=80=9CSignalling a Zone Cut to Nowhere in the =
DNS=E2=80=9D to the IESG.