IETF Logo Mail Archive

[DNSOP] Re: 4 documents for consideration about the future of LocalRoot behavior.

John Levine <johnl@taugh.com> Sat, 24 January 2026 19:26 UTC

Return-Path: <johnl@iecc.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 8EA87AC832F6 for <dnsop@mail2.ietf.org>; Sat, 24 Jan 2026 11:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.384
X-Spam-Level:
X-Spam-Status: No, score=-4.384 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, HEADER_FROM_DIFFERENT_DOMAINS=0.017, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="Wp9K0fth"; dkim=pass (2048-bit key) header.d=taugh.com header.b="CKocZFYa"
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 gEDPG0XWniNY for <dnsop@mail2.ietf.org>; Sat, 24 Jan 2026 11:25:59 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 69870AC832C8 for <dnsop@ietf.org>; Sat, 24 Jan 2026 11:25:59 -0800 (PST)
Received: (qmail 10550 invoked from network); 24 Jan 2026 19:25:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=293469751cc6.k2601; t=1769282748; x=1769628348; bh=rV1Pm9jWbR1LtC4tTMF2s4zfkTo9KM5aCjMXrw9a+pg=; b=Wp9K0fthk1wyXYFqD6zuZGuBXBI209fqfy4vgeI9YrAHy8Gb/4vJcY0aaXC41o8Oi7UvjutxUwNvjb8d1VyqhjGtq9aR0JQXUvCE8/CQ72T0+3YIaoi4TZqasan1Vj1aE7V71JflDv6YXtyK/vlewX3YjMwpIc/97xpfgRygZdi8XdsmrLN9VMUFOnpYo1NFD3ZaDpr0NAakNFDshwFsZ2Fzze9wbdh4Ky9+kvEj276bl2gejR1xdAvBCZ8IbCSDWJxXLlLXhJLdIv9FGDlpzMxQPYdHtqJAKw5LnlmR9xODK92Ks3PRCBCgmUmyht8TzjaW+yQMItn0gLy7RToXxw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=293469751cc6.k2601; bh=rV1Pm9jWbR1LtC4tTMF2s4zfkTo9KM5aCjMXrw9a+pg=; b=CKocZFYaWVaGJN5sgjn78eu3En5iUx+h7dkpZAvAq8YZOQqtyRnQ5H4REqsG6+VxUlj/D90amHExdzVmrotKySHCgHwG0G9qZZ9Y+yQl/xQEYSssvfz/bOhx45bxmzJ5PPoaKG6WnOdl80YGTOqQI+XonN08Wrn3/PzMq7BVJzzt0lRIe7TZfV+ez32+AorReAtX3eCJj3obR49D/0tdWkXvegjQTkcHP64k8fl0ENn+20vNK0iSyNjLgQFWkD5+IjMqKegSTnlwv9LO+pvYxf5p8PS/rb7dHV6b3FlioUCnTo3dlmmcX8Hg/nE6jLUCH098JSnySYsA+R4vguBXBg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 24 Jan 2026 19:25:58 -0000
Received: by ary.qy (Postfix, from userid 501) id 22CF0F2FF659; Sat, 24 Jan 2026 14:25:57 -0500 (EST)
Date: Sat, 24 Jan 2026 14:25:57 -0500
Message-Id: <20260124192558.22CF0F2FF659@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CAKr6gn2vJS7RagqFbYjikmnnKE==EAbTM8Vx4rMjmf27CYXLmA@mail.gmail.com>
Organization: Taughannock Networks
References: <ybla4y6lwjf.fsf@wx.hardakers.net> <234729DC-6EFD-4D22-B3B4-EA143CDC2430@fl1ger.de> <yblldhohck9.fsf@wx.hardakers.net> <76252438-9F03-4C5E-878A-980006C95380@fl1ger.de> <22208.1769187954@obiwan.sandelman.ca> <ybltswbejnt.fsf@wx.hardakers.net> <CAKr6gn2vJS7RagqFbYjikmnnKE==EAbTM8Vx4rMjmf27CYXLmA@mail.gmail.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: YWYSF36UUACELGE3WDIGA5C6ADANCXYO
X-Message-ID-Hash: YWYSF36UUACELGE3WDIGA5C6ADANCXYO
X-MailFrom: johnl@iecc.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: ggm@algebras.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: 4 documents for consideration about the future of LocalRoot behavior.
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4fMCKR7X5rd3aEbCED5D12wD4hI>
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>

It appears that George Michaelson  <ggm@algebras.org> said:
>-=-=-=-=-=-
>
>This is true, but browsers now may make htttp:// an almost deprecated
>protocol and invoke warnings and burdens to fetch.

I dunno about you, but I am having trouble coming up with a scenario
where my DNS cache uses a browser to fetch the zone file. wget and
curl like http just fine.

But this is bikeshedding.  Any CDN can serve both http and https.

The question as I said several messages ago is about building AXFR
CDNs vs. adding http(s) fetching to DNS software.  Or maybe both.

> It could be equally be XoH, AXFR-over-DoT.

I agree that AXFR over anything nore than regular TCP is overkill for this
particular application.

R's,
John

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