MIME-Version: 1.0
References: <dda32a30-518d-40dd-b7da-a19e8e9b3d4d@bellis.me.uk>
 <8C1D853F-17D4-4E2B-B281-F7FCA50DA8B3@strandkip.nl>
In-Reply-To: <8C1D853F-17D4-4E2B-B281-F7FCA50DA8B3@strandkip.nl>
From: Davey Song <songlinjian@gmail.com>
Date: Mon, 1 Jul 2024 11:49:10 +0800
Message-ID: 
 <CAAObRXL84d-BQWrPEDpps-4ghKGTiruTFe1vXOQSKrvp3gnUOQ@mail.gmail.com>
To: Joe Abley <jabley@strandkip.nl>
Content-Type: multipart/alternative; boundary="0000000000008c2451061c277b29"
Message-ID-Hash: IIS6RMPTQZEMYCGKYKBASHN55FQPFBYX
CC: Ray Bellis <ray@bellis.me.uk>, dnsop@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BDNSOP=5D_Re=3A_Side_Meeting_-_DNS_Load_Balancing?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/dnsop/2j2oxz-ZzdX8_uCnaK6IzKQyDb0>

--0000000000008c2451061c277b29
Content-Type: text/plain; charset="UTF-8"

People add tricks to DNS when DNS does not fit their needs. However, my
customers complained about the difficulties of deploying their DNS on
multiple platforms with different DNS tricks (GeoDNS for example) or
switching from one another.

I agree with Joe. DNS is a layer of indirection. If one indirection can not
solve the problem in a good manner, another indirection is needed. If we do
it in resolver like Paul suggest, another indirection protocol should be
introduced.  You can name it anything other than "DNS"...


> Names as a layer of indirection between applications and addresses
> represent dynamic data by design, and the idea that the manner by which
> that data can be managed must be rigidly constrained seems unnecessary and
> a bit out of touch with reality.



Davey

--0000000000008c2451061c277b29
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div>People add tricks to DNS w=
hen DNS does not fit their needs. However, my customers complained about th=
e difficulties of deploying their DNS on multiple platforms with different =
DNS tricks (GeoDNS for example) or switching from one another.</div><div><b=
r></div><div>I agree with Joe. DNS is a layer of indirection. If one indire=
ction can not solve the problem in a good manner, another indirection is ne=
eded. If we do it in resolver like Paul suggest, another indirection protoc=
ol should be introduced.=C2=A0 You can name it anything other than &quot;DN=
S&quot;...</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
Names as a layer of indirection between applications and addresses represen=
t dynamic data by design, and the idea that the manner by which that data c=
an be managed must be rigidly constrained seems unnecessary and a bit out o=
f touch with reality.</blockquote><div><br></div><div>=C2=A0</div><div>Dave=
y=C2=A0</div></div></div>

--0000000000008c2451061c277b29--