[dns-privacy] Do53 vs DoT vs DoH Page Load Performance Study at ANRW

Kevin Borgolte <kevin@iseclab.org> Fri, 19 July 2019 04:34 UTC

Return-Path: <kevin@iseclab.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 9D6791200D7 for <dns-privacy@ietfa.amsl.com>; Thu, 18 Jul 2019 21:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iseclab.org
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 cmSZMlRGQ1cs for <dns-privacy@ietfa.amsl.com>; Thu, 18 Jul 2019 21:34:28 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2980C120043 for <dns-privacy@ietf.org>; Thu, 18 Jul 2019 21:34:28 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id t132so13860304pgb.9 for <dns-privacy@ietf.org>; Thu, 18 Jul 2019 21:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iseclab.org; s=mail; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:to; bh=FEiSa68TSfoWIvmJnTOkoMtzG6FmgGddpONsNVGbrmI=; b=BCkyqd2wuMLUyVHwZrOatDW0uxR5CiqGx2F3m0pIBHvpIprDxOqT2NmTkVd42zlwHy VuHEjNLdWJ9cuZcOCzPgdACm+itGtpPGTzNiHrGzj097iSltIPCmK6Sp03oJcxvzwrQ8 fWkjBO2jAfbiUvNILP2uLnDYNxvTWTg0/E8whDq4U4vaWGQJS+KHyu4YL9RwuwjLTxw8 wQkx1EI3SpiVE0GQRCWenBirKOQDBg0ukmqFR4ls62qxOVMiDS1RIoxmILuPj/TUYAvX KURbMt3hjp37xCYEmB/heVw734OdjREwiErYRTBbyCdvMAhfHMZ/4iS5XhfkO7qdzHoP LGCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:to; bh=FEiSa68TSfoWIvmJnTOkoMtzG6FmgGddpONsNVGbrmI=; b=iJlaeswzkvF3A8FPlaCpWtNsYhVBuiDE2WcaqgpuzxZTYnMlM3+6jBr+wPsAeOW0Hv KACj/jllmM1FwLZcgplZA6omc3ZcttXr0f6OEvqw/xUfD9T/yCueiUN066/fd+ZhXDH9 1ULtfBD2kQ2dpfVLgtA/fPCKvYO2vJXWUofEwiVK9tHtnr4ZAapTIB5VHe0HE8HvuFSf gyLXo9XruVIUF5u8HM6Wnq/vemoyJtLEjDFepxodEMfQgRIdsG5nSjvnXYNXLuEzEPHt k7M2Xe+AfoO1qUUoe5GTZjahHg+j0aA/QMbkqbLRW/65ZZ/j+jn5EN59+lXGox0kZcYa 5I9w==
X-Gm-Message-State: APjAAAUBa/nsqlHGjOndYigYAgQOIwxBqx2NQyE8aNPNjHEc2b2LAqAv JDA64nKCzgskeTwvQVJy4bze7g==
X-Google-Smtp-Source: APXvYqxE3Ys0iQKni4Bn7FgdO2g7GAtKF3lyeYggdSjnlDYHnbGUFWe3FCRH3NJ6jIfeffgPxg/WpQ==
X-Received: by 2002:a63:6f81:: with SMTP id k123mr52797721pgc.12.1563510867453; Thu, 18 Jul 2019 21:34:27 -0700 (PDT)
Received: from [192.168.201.137] ([103.23.203.130]) by smtp.gmail.com with ESMTPSA id w22sm30849413pfi.175.2019.07.18.21.34.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jul 2019 21:34:26 -0700 (PDT)
From: Kevin Borgolte <kevin@iseclab.org>
Content-Type: multipart/alternative; boundary="Apple-Mail-168790B2-08C6-469B-8CEE-A4893F4B12BC"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Fri, 19 Jul 2019 12:34:19 +0800
Message-Id: <1405FBF9-C2A3-44EF-8438-C9B37899221F@iseclab.org>
References: <402781F4-33D8-4FD4-8087-FDCEFFF2D549@iseclab.org>
Cc: ahounsel@cs.princeton.edu, feamster@uchicago.edu, pschmitt@cs.princeton.edu, jordanah@princeton.edu
To: dns-privacy@ietf.org
X-Mailer: iPad Mail (16F203)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/9bTq29wPrx3T4tWuceeumJI_I1Y>
Subject: [dns-privacy] 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: Fri, 19 Jul 2019 04:34:31 -0000

Please see below, I mistakenly sent it to dprive@ instead of dns-privacy@, which bounced. Please excuse if you are getting the email multiple times.

Begin forwarded message:

> From: Kevin Borgolte <kevin@iseclab.org>
> Date: July 19, 2019 at 12:26:40 GMT+8
> To: add@ietf.org, doh@ietf.org, dnsop@ietf.org, dprive@ietf.org
> Cc: feamster@uchicago.edu, pschmitt@cs.princeton.edu, jordanah@princeton.edu, ahounsel@cs.princeton.edu
> Subject: Do53 vs DoT vs DoH Page Load Performance Study at ANRW
> 
> Hi all,
> 
> we recently did a study on Do53/DoT/DoH performance on webpage load times in Firefox, which we wanted to share with you. Austin Hounsel will give a talk about our work at ANRW on Monday. Paul Schmitt and I will also be around (myself only Monday afternoon and Tuesday) if you’d like to chat about it in person. The extended pre-print of our paper is available here: https://arxiv.org/abs/1907.08089
> 
> We looked at the effect of Do53/DoT/DoH on page load times because we figured they will be a more interesting measure than simple DNS resolution times. We also looked at simulated mobile connections (4G, lossy 4G, and 3G). We found that DoH is on par with Do53/DoT if your Internet connection is good, and worse if it is not. The potential for DoH seems to be largely push. ADD can also make sense, or at least an extended/updated OS API would.
> 
> We think there are two opportunities to improve Do53 and DoT: better wire format caching and partial responses combined with multiple questions. Part of the improvements and issues we discovered we later found out (by talking to some of you) were mentioned in early working group drafts, but they never made it into published RFCs or mailing list posts (which is where we looked initially). We hope you can help and explain the thoughts that went into these decisions 15 to 20 years ago. Maybe it even makes sense to revisit the ideas from back then combined with our ideas, considering how the Internet has evolved?
> 
> We‘d appreciate any feedback on our work. Please also feel free to reach out to us directly (in person or by email) if you have any insight or feedback you’d prefer not to post to the list.
> 
> Best,
> Kevin
> 
> P.S. Please excuse the posting to multiple lists, but all seem relevant.