Re: [DNSOP] Global DNS architecture changes, "the camel", and so on

Paul Vixie <> Tue, 21 August 2018 04:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52BD7130DF6 for <>; Mon, 20 Aug 2018 21:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kQ9hMAJAArOA for <>; Mon, 20 Aug 2018 21:18:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4D0531292F1 for <>; Mon, 20 Aug 2018 21:18:55 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:9061:ce0d:93bf:336d] (unknown [IPv6:2001:559:8000:c9:9061:ce0d:93bf:336d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id BF876892C6; Tue, 21 Aug 2018 04:18:52 +0000 (UTC)
Message-ID: <>
Date: Mon, 20 Aug 2018 21:18:48 -0700
From: Paul Vixie <>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: George Michaelson <>
CC: Andrew Sullivan <>, dnsop WG <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] Global DNS architecture changes, "the camel", and so on
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 Aug 2018 04:18:57 -0000

George Michaelson wrote:
> I am less sure the UDP/TCP thing reduces to "no"
> I see no reason any more to assume session cost is too high for a
> globally deployed DNS.
> I suspect what DNSOPS and a hypothetical directorate thinks about DNS
> is less impactful (sorry, hate that word) than what embeds in Android
> devices.
> ...

i don't think there's any decision support coming from those 
observations. the internet is still older and larger than the web, and i 
expect this condition to continue, but if i'm wrong, it will still never 
be small enough to ignore, or indeed, small in any way.

we should support android, and the web. that won't change what the rest 
of the internet needs to keep doing, for reasons of its own, for at 
least the lifetimes of the children of all members of this mailing list.

let me illustrate. a shell user on a virtual container somewhere, in 
2049 let's say, who needs to pull down an update in single user mode so 
she can get out of single user mode, will need to do a dns lookup. yes, 
we have proven that we can use persistent/stateful initiators in that 
use case, and that we can parse json. but can that become mandatory, 
because the web came, and was large, and didn't need datagram transport?

i say no. the internet predates the web and might outlive it.

P Vixie