Re: [Doh] [Ext] DNS over HTTP/3?

Paul Hoffman <paul.hoffman@icann.org> Mon, 19 November 2018 15:39 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE62130DD3 for <doh@ietfa.amsl.com>; Mon, 19 Nov 2018 07:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 M1hSzo3cMhh5 for <doh@ietfa.amsl.com>; Mon, 19 Nov 2018 07:39:19 -0800 (PST)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F84A130DD8 for <doh@ietf.org>; Mon, 19 Nov 2018 07:39:19 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 19 Nov 2018 07:39:17 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Mon, 19 Nov 2018 07:39:17 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: bert hubert <bert.hubert@powerdns.com>
CC: "doh@ietf.org" <doh@ietf.org>
Thread-Topic: [Doh] [Ext] DNS over HTTP/3?
Thread-Index: AQHUgBpJDcHiU7C9TEuONF//QgGdoaVXwfYA
Date: Mon, 19 Nov 2018 15:39:16 +0000
Message-ID: <AB63D041-DF03-4137-8B8D-18A79CDD4208@icann.org>
References: <20181119100954.GA6704@server.ds9a.nl> <5BE15B68-1C61-4462-AE84-901E2CF0F9F9@icann.org> <20181119151209.GC11506@server.ds9a.nl>
In-Reply-To: <20181119151209.GC11506@server.ds9a.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_F1A79C9B-90F8-480D-8DF8-28D559885D5B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/MqBo6U_ItUeWY4UoEZTGhwx9ay8>
Subject: Re: [Doh] [Ext] DNS over HTTP/3?
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 15:39:22 -0000

On Nov 19, 2018, at 7:12 AM, bert hubert <bert.hubert@powerdns.com> wrote:
> 
> On Mon, Nov 19, 2018 at 02:12:18PM +0000, Paul Hoffman wrote:
>>> I've observed that the thousands of users of doh.powerdns.org (I also do not
>>> know how this happened) take around 22 packets per DNS query/response. 
>> 
>> It would be valuable to know if this is this because your DoH server kills
>> the entire connection after every DNS query, or because the clients are
>> doing so.
> 
> It does around 2 DNS queries per HTTPS connection on average dnsdist-doh
> keeps open an HTTP/2 connection for 10 seconds if it becomes idle.

Thanks, that seems to be your problem. Can the dnsdist DoH server package be configured to have an idle timeout that is more representative of typical browser use, such as on the order of minutes?

>>> Larger scale adoption of TLSv1.3 might improve this somewhat, but it is a
>>> big number.
>> 
>> DoH was designed for long-lived connections, so the number would normally be smaller after the initial connection.
> 
> I can only report what I measure based on several thousands of users.
> 
>>> I've also personally observed that a "slightly suboptimal" network
>>> absolutely kills browsing performance in Firefox Nightly using DoH.  A naive
>>> calculation shows that 0.5% packet loss turns into a 5% failure rate per DoH
>>> query, which then can cause Head of Line blocking for further queries, which
>>> cascades into "blank pages" getting rendered. 
>> 
>> When you say "naive calculation", do you mean this is observed in the
>> clients hitting your DoH server?  That would indeed be scary.  However,
>> the Mozilla numbers tell a very different story.  It would be good to know
>> which one is true.
> 
> My personal observation is that on a slightly bad network, turning off DoH
> speeds up things massively and makes the web useable again.  This naively
> makes sense, DoH uses way more packets and suffers from Head of Line
> blocking, unlike plain DNS.

Is that still true with a server timeout that is not so short?

> We have asked Mozilla to provide more details of their measurements, but
> these have not been forthcoming.

Noted. It would be *really* useful to the community if there was better communication from them.

> Note that the graph published on the blog misses the 95% and 99% bins,
> https://blog.nightly.mozilla.org/files/2018/08/DNS-over-HTTPS-Performance-Improvement.png
> and does not include details on timeouts.

Yep, and that would be useful too.

>>> And, perhaps somewhat more provocatively, should we maybe not start pushing
>>> DoH/2 if it leaves people with a sub-standard experience, causing them to
>>> disable DoH?
>> 
>> If the implementations on the client or server side make using DoH bad,
>> those implementations should be fixed.  If they don't get fixed, we'll
>> certainly hear about it.
> 
> There is already a Firefox ticket I think, but with Patrick and Daniel gone
> or gone soon, I am not sure who owns it now.

Hopefully he or she will decloak soon.

> 
>>> DoH/3 might be somewhat of a wait but it might prevent that
>>> sour taste from developing.
>> 
>> Without sufficient data, it's hard to say if there really is a sour taste.
> 
> Perhaps Mozilla can clarify further what they measured beyond the 7
> milliseconds slowdown.
> 
> I may do some induced packetloss experiments to see if the "experience" can
> be reproduced.

That would be grand, but it would also be good to have such experiments when the server has a more sensible timeout value.

--Paul Hoffman