IETF Logo Mail Archive

Re: [dns-privacy] [DNSOP] [Add] Do53 vs DoT vs DoH Page Load Performance Study at ANRW

Paul Vixie <paul@redbarn.org> Mon, 22 July 2019 20:52 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1CD120120; Mon, 22 Jul 2019 13:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISPZzqp7F6qD; Mon, 22 Jul 2019 13:52:43 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A188712008C; Mon, 22 Jul 2019 13:52:43 -0700 (PDT)
Received: from linux-9daj.localnet (dhcp-9546.meeting.ietf.org [31.133.149.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 2494D892E8; Mon, 22 Jul 2019 20:52:42 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Cc: Andrew Campling <andrew.campling@419.consulting>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Puneet Sood <puneets=40google.com@dmarc.ietf.org>, Kevin Borgolte <kevin@iseclab.org>, DoH WG <doh@ietf.org>, "pschmitt@cs.princeton.edu" <pschmitt@cs.princeton.edu>, "jordanah@princeton.edu" <jordanah@princeton.edu>, "feamster@uchicago.edu" <feamster@uchicago.edu>, "add@ietf.org" <add@ietf.org>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>, Rob Sayre <sayrer@gmail.com>, "ahounsel@cs.princeton.edu" <ahounsel@cs.princeton.edu>
Date: Mon, 22 Jul 2019 20:52:39 +0000
Message-ID: <5018674.DSy9L6O0YW@linux-9daj>
Organization: none
In-Reply-To: <LO2P265MB1327B72D0D6ABCBEEA84D349C2C40@LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM>
References: <402781F4-33D8-4FD4-8087-FDCEFFF2D549@iseclab.org> <5F9202DE-ED2F-4F2A-8463-12334E54BC46@cable.comcast.com> <LO2P265MB1327B72D0D6ABCBEEA84D349C2C40@LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/aHCFnuAyqcqKuLmvLIScv9OVJQ4>
X-Mailman-Approved-At: Mon, 22 Jul 2019 14:19:16 -0700
Subject: Re: [dns-privacy] [DNSOP] [Add] Do53 vs DoT vs DoH Page Load Performance Study at ANRW
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2019 20:52:46 -0000

On Monday, 22 July 2019 20:45:43 UTC Andrew Campling wrote:
> ...
> 
> [AC] This would be helpful given it appears some (all?) DoH resolvers have
> indicated that they will not pass sufficient information to (rival) CDN
> vendors to allow geographic routing.  Clearly if this is commonplace then
> performance gains from DoH, if any, could be lost from an end-user
> perspective due to inefficient routing of content.  

several people have disagreed with my public statements that "everyone should 
run their own rdns, don't use quad-anything" on the basis of the blender 
effect. when i tell them about ECS they stop talking, which is too bad, 
because they then don't get to hear the stories of how /32 and /128 are the 
default ECS subnet size for many ISP resolvers.

apparently ECS creates problems for privacy, but _how could we have 
suspected_?

-- 
Paul

v2.23.0 | Report a Bug | By Email