[DNSOP] Re: Mahesh Jethanandani's Block on charter-ietf-dnsop-04-00: (with BLOCK and COMMENT)
Jim Reid <jim@rfc1035.com> Wed, 25 June 2025 20:51 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 C39C8397B993; Wed, 25 Jun 2025 13:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 j4DZYPiLxodC; Wed, 25 Jun 2025 13:51:23 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (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 1787E397B988; Wed, 25 Jun 2025 13:51:23 -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 CE7B52420E4A; Wed, 25 Jun 2025 20:51:21 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Message-Id: <55915183-AFA4-44BF-A6F6-9D04A81A2DBA@rfc1035.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E4520AF-DC59-464C-9347-7DCC9BC9D74E"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Date: Wed, 25 Jun 2025 21:51:21 +0100
In-Reply-To: <175088394368.727853.6218720019293243254@dt-datatracker-6754d69b7c-p2xd7>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
References: <175088394368.727853.6218720019293243254@dt-datatracker-6754d69b7c-p2xd7>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: ORPOVQGA74JCVF5BQBJQPQFSLVFBN5QS
X-Message-ID-Hash: ORPOVQGA74JCVF5BQBJQPQFSLVFBN5QS
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: The IESG <iesg@ietf.org>, dnsop-chairs@ietf.org, dnsop@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Mahesh Jethanandani's Block on charter-ietf-dnsop-04-00: (with BLOCK and COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zFQ0fZLWwxOsxZTdtGTyVoPWi6U>
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 25 Jun 2025, at 21:39, Mahesh Jethanandani via Datatracker <noreply@ietf.org> wrote: > > "DNSOP", paragraph 0 >> The DNSOP WG is also responsible for maintenance, updates, and extensions to >> the DNS protocol. > > Thanks for the pointer to the email that describes the sentiment behind why the > WG is undergoing a recharter. In that sentiment is the desire to split the WG > to move some of the protocol work out to another WG while keeping the focus of > this WG on operations. How does the above statement jive with that sentiment? The dnsop WG is pretty much the only place to do DNS protocol work until that new WG gets formed. Which means protocol work has to be in scope for dnsop until that happens. Once that new WG is created, we drop the above sentence from the dnsop charter: one quick, clean tweak. dnsop would then just be responsible operational stuff and the new WG takes charge of development and maintenance of the DNS protocol. > What are the milestones that have to be achieved before the split can happen? I think this might have to wait until the deleg WG is just about done. It's probably a bad idea to have "too many" DNS WGs on the go at the same time. YMMV.
- [DNSOP] Mahesh Jethanandani's Block on charter-ie… Mahesh Jethanandani via Datatracker
- [DNSOP] Re: Mahesh Jethanandani's Block on charte… Jim Reid
- [DNSOP] Re: Mahesh Jethanandani's Block on charte… Michael De Roover