[DNSOP] draft WG chapter: 30/6/25

Jim Reid <jim@rfc1035.com> Fri, 30 May 2025 17:50 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4A15B2EE1B52 for <dnsop@mail2.ietf.org>; Fri, 30 May 2025 10:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 jZ8mXn4iGG-J for <dnsop@mail2.ietf.org>; Fri, 30 May 2025 10:50:04 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (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 865842EE1B4B for <dnsop@ietf.org>; Fri, 30 May 2025 10:50:04 -0700 (PDT)
Received: from smtpclient.apple (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 841D4242123F for <dnsop@ietf.org>; Fri, 30 May 2025 17:50:03 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9198A5FF-C3F4-46D3-AC83-ED932F3B1211"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Message-Id: <2C06E83A-950C-4665-BC50-AEB516B7CD1B@rfc1035.com>
Date: Fri, 30 May 2025 18:49:59 +0100
To: Working Group DNSOP <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: R6XDQ54A3JMG4GR4ZO2MS46RJWKALHVN
X-Message-ID-Hash: R6XDQ54A3JMG4GR4ZO2MS46RJWKALHVN
X-MailFrom: jim@rfc1035.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; 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: [DNSOP] draft WG chapter: 30/6/25
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_EyLjFyR9vl3kGRyhaJ1y-f0-kc>
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 proposed new charter for the WG. Please speak up on the list if you have comments or suggestions on how to improve the text.

It's intentionally terse in the hope we can avoid rat-holing and spending too many edit cycles over long lists of stuff that's in/out of scope. If the charter just focuses on the high-level principles it should mean the WG has the flexibility to handle new DNS developments without the need for frequent rechartering.

Two points:

1) The target is to reach WG consensus on stable charter text by 12/06 or so: ie ~2 weeks from now. If this can be reached, the text will go for internal IESG review by 26/06 and then go for IETF review and hopefully the IESG review in the telechat of 10/07. All being well, the new charter should be in place for IETF123.

2) The proposed milestones are sort of placeholders. I'm told WG charters must include milestones and the IESG rejects ones that don't have them. It won't be necessary to recharter the WG whenever milestones get added or removed. The milestones below aren't part of the charter, so please don't get too hung up on them. Some could well be dropped. The dates for these milestones are still to be decided. BTW it's Med, our new AD, who said the charter text had to include milestones. I'm just doing what I'm told.

Here's the charter text:


The DNSOP WG defines and documents the deployment and operational considerations for the DNS protocol. The WG also provides guidance and elaborates best current practices for DNS deployment.

DNSOP provides a venue for DNS operators and other interested parties to engage in discussions around the operational requirements of DNS and publish documents. Specifically, the WG welcomes insights from those who wish to share operational experience and challenges as well as discuss other DNS-related matters that are within scope of the working group.

The DNSOP WG is also responsible for maintenance, updates and extensions to the DNS protocol.

The WG will engage with relevant WGs and other appropriate organisations whenever collaboration is needed. DNSOP will liaise with IANA on the management of IANA's DNS-related registries.


Milestones

   • $DATE: Submit Structured Error Data for Filtered DNS to the IESG
   • $DATE: Submit Delegation Revalidation by DNS Resolvers to the IESG
   • $DATE: Submit Clarifications on CDS/CDNSKEY and CSYNC Consistency to the IESG
   • $DATE: Submit DNS IPv6 Transport Operational Guidelines to the IESG
   • $DATE: Submit Domain Control Validation using DNS to the IESG
   • $DATE: Submit Using DAN with SVCB and QUIC to the IESG
   • $DATE: Submit Greasing Protocol Extension Points in the DNS to the IESG
   • $DATE: Submit An update of DNS Security Extensions (DNSSEC) to the IESG
   • $DATE: Submit A Roadmap for DNS to the IESG