[DNSOP] Re: DNSOP[Ext] on the more general problem of delegating to other namespaces in the DNS

Wes Hardaker <wjhns1@hardakers.net> Fri, 20 June 2025 18:37 UTC

Return-Path: <wjhns1@hardakers.net>
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 EEBBF377BF72 for <dnsop@mail2.ietf.org>; Fri, 20 Jun 2025 11:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
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 qnTuY4coihMU for <dnsop@mail2.ietf.org>; Fri, 20 Jun 2025 11:37:00 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (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 5D7E3377BF61 for <dnsop@ietf.org>; Fri, 20 Jun 2025 11:37:00 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 371D3208F2; Fri, 20 Jun 2025 11:36:59 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 371D3208F2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1750444619; bh=sNkmR+ErifSeamUxHYDaj/SVB5e0hUBXVa4sivo9xLY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=UbUnG/WeJHbGFdumtSH1YUJbVZz+q5Loc3rHTPzkABZAB7Qdv5j3IkhV9cdwQ1lIP Ixz6H7k5j0HMTkCHdzCkrKA0vNLm08kp52clKEFV5mRW7+yqojXrqGe5RkklGu+ftG KOcm6vxrpQ84XLI19oQhwCA5NeBaamA/qBQAnPT4=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Joe Abley <jabley=40strandkip.nl@dmarc.ietf.org>
In-Reply-To: <6215983B-D210-4FB1-B64C-28691B421ACC@strandkip.nl> (Joe Abley's message of "Tue, 17 Jun 2025 19:54:41 +0200")
References: <761F6D32-25FE-4742-9682-819A338C8EC9@strandkip.nl> <96D1EC9A-DC37-4950-B391-E9C23B8C4686@icann.org> <6215983B-D210-4FB1-B64C-28691B421ACC@strandkip.nl>
Date: Fri, 20 Jun 2025 11:36:58 -0700
Message-ID: <yblmsa2l0ol.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: 2VAZRAE4NDLFVYWQ2Y5EWXFCJYC6G4GK
X-Message-ID-Hash: 2VAZRAE4NDLFVYWQ2Y5EWXFCJYC6G4GK
X-MailFrom: wjhns1@hardakers.net
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: Paul Hoffman <paul.hoffman@icann.org>, dnsop <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: DNSOP[Ext] on the more general problem of delegating to other namespaces in the DNS
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7SIiBGzmkpYKKmtgs3iIkYCkdtQ>
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>

Joe Abley <jabley=40strandkip.nl@dmarc.ietf.org> writes:

> We have paged the Science Officer. I understand Wes is in the process
> of reporting to the bridge.

Hope to have results done internally next week...  Will likely present a
highlight in DNSOP, and maybe significant more details at oarc or
something (mind you: assumes I'm going, which is not a safe assumption).
-- 
Wes Hardaker
USC/ISI