IETF Logo Mail Archive

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

Jim Reid <jim@rfc1035.com> Sun, 01 June 2025 16:53 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 7C47C2F6B0AA for <dnsop@mail2.ietf.org>; Sun, 1 Jun 2025 09:53:20 -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 uO7C6EHAMdUs for <dnsop@mail2.ietf.org>; Sun, 1 Jun 2025 09:53:20 -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 E33112F6B0A3 for <dnsop@ietf.org>; Sun, 1 Jun 2025 09:53:19 -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 70E51242123F; Sun, 01 Jun 2025 16:53:18 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Message-Id: <1F621010-4B45-4BFE-AB7C-B1AF8DB0131A@rfc1035.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A3FF9B2D-C68B-47E3-902F-4DE4A16E92AC"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Date: Sun, 01 Jun 2025 17:53:16 +0100
In-Reply-To: <A1464E84-0CE6-4B1E-B5B2-4DDDA891C42A@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
References: <2C06E83A-950C-4665-BC50-AEB516B7CD1B@rfc1035.com> <A1464E84-0CE6-4B1E-B5B2-4DDDA891C42A@icann.org>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: HZJE4LL6DV6XXXEIMBXWNBNRUTY4P5MA
X-Message-ID-Hash: HZJE4LL6DV6XXXEIMBXWNBNRUTY4P5MA
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
CC: Working Group DNSOP <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] 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/42e1AMlkuawswjebppQy-ikYwPo>
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>


> On 30 May 2025, at 19:13, Paul Hoffman <paul.hoffman@icann.org> wrote:
> 
> - "The DNSOP WG is also responsible for maintenance, updates and extensions to the DNS protocol." There has been growing discussion that there should be a DNS development (DNSDEV) working group that works on new developments; the quoted wording prevents that.

Only if you assume (incorrectly) a WG charter never, ever changes.

If/when the expected dnsdev WG emerges, the above sentence will be deleted from the dnsop charter. Until that happens, dnsop will pretty much be the only place at the IETF for doing maintenance, updates and extensions to the DNS protocol. [Apart from deleg of course.] That means changes to the DNS protocol need to be in the dnsop charter and in scope for the WG until a more suitable home for that effort is established. Which probably means there will be another (minor?) rechartering of dnsop at that point.

v2.45.0 | Report a Bug | By Email | System Status