[DNSOP] Re: Side Meeting - DNS Load Balancing

Paul Vixie <paul@redbarn.org> Mon, 01 July 2024 22:37 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88758C14F6FA for <dnsop@ietfa.amsl.com>; Mon, 1 Jul 2024 15:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redbarn.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGX0N0Obv8ls for <dnsop@ietfa.amsl.com>; Mon, 1 Jul 2024 15:37:39 -0700 (PDT)
Received: from util.redbarn.org (util.redbarn.org [24.104.150.222]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 9C315C151520 for <dnsop@ietf.org>; Mon, 1 Jul 2024 15:37:39 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.redbarn.org", Issuer "RapidSSL TLS RSA CA G1" (not verified)) by util.redbarn.org (Postfix) with ESMTPS id 079AD1A2926; Mon, 1 Jul 2024 22:37:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1719873459; bh=fSHrdTFp0OgdfpAihI4/9ZWKipjZDyb+0NHCyZGluPc=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=Efx5cKHx11BFQpIxS7xiub1YegFiNHwzPGsWK+C6eNEG6h0jqrpazHy8RiQ6xulKB PshMirwgxKK7Fza+dEFWkaLnIZfSyBeGcvPoVA0QoTsf8H2BEsv3M7F4oOwvuj6xQ0 +q/uUvdwlhPdaU8dxJpxGNw9A2Sa3oonNEZLcZkU=
Received: from heater.srcl.tisf.net (dhcp-176.access.rits.tisf.net [24.104.150.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPS id CA636C3F21; Mon, 1 Jul 2024 22:37:38 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Davey Song <songlinjian@gmail.com>
Date: Mon, 01 Jul 2024 15:37:38 -0700
Message-ID: <3319232.5fSG56mABF@heater.srcl.tisf.net>
In-Reply-To: <CAAObRXJr4r-jVX-p739oM2Z6AAnzzSTAw34rjo8Ot8yUDvFDow@mail.gmail.com>
References: <dda32a30-518d-40dd-b7da-a19e8e9b3d4d@bellis.me.uk> <5020268.31r3eYUQgx@heater.srcl.tisf.net> <CAAObRXJr4r-jVX-p739oM2Z6AAnzzSTAw34rjo8Ot8yUDvFDow@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Message-ID-Hash: FBBMXZAUCVPWXIJHTICRPA27VRLQXQS7
X-Message-ID-Hash: FBBMXZAUCVPWXIJHTICRPA27VRLQXQS7
X-MailFrom: paul@redbarn.org
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: dnsop@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: Side Meeting - DNS Load Balancing
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/m90jH4PuJHeIyInPhwa4Xm-aE4Q>
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 Monday, July 1, 2024 2:54:55 AM PDT Davey Song wrote:
> Hi Paul,
> 
> I’m sending this email off-list to respond to your comment.

in fact you cc'd the mailing list, so i shall do likewise in my reply.

> ... However, the fact is that DNS has been widely used
> as a direction system for a long time with lots of tricks though.
> Individual tricks build walls for interoperability.

sadly, no innovator ever earned equity by adding simplicity to a system. the 
continuous result has been a series of negative externalities ("complexity 
costs") for the rest of a community or industry.

> Our friend PVM  thought
> that DNS could contain not only data but also programs in the future. What
> do you think?

noting that at the time javascript was first prototyped, there were a number of 
existing languages intended for precisely this kind of embedding which were 
not considered, any of which would have matured faster than javascript has 
done. this should inform us that any language encoded into the DNS would be 
found not-innovative-enough for some future equity-earner, and that continuous 
re-invention will be the result no matter what then exists.

however, your question shows in-clarity in what i wrote earlier. i am in fact 
advocating for putting something-like-a-program into the dns, to be consumed 
by either recursive dns servers, or stub resolvers, or apps, or all three. 
whether this is some kind of policy that describes how to learn load levels of 
content mirrors, or how to learn CDN topology, or how to learn other metrics 
-- doesn't matter to me. SPF shows a way to express policy as rules, but if 
someone insists that it be tiny Lua or TCL or Scheme fragments, i won't treat 
it as a proposal to a different need, only a proposal in a different format.

i'll have more to say in my reply to joe.

vixie