[DNSOP] Stub resolvers and A+AAAA (was Introducing draft-vavrusa-dnsop-aaaa-for-free)

Shane Kerr <shane@time-travellers.org> Thu, 24 March 2016 13:50 UTC

Return-Path: <shane@time-travellers.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC94812DB3B for <dnsop@ietfa.amsl.com>; Thu, 24 Mar 2016 06:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 eCEG3a9ibtd7 for <dnsop@ietfa.amsl.com>; Thu, 24 Mar 2016 06:50:51 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B499F12DB37 for <dnsop@ietf.org>; Thu, 24 Mar 2016 06:49:29 -0700 (PDT)
Received: from [2001:470:78c8:2:224:9bff:fe13:3a9c] (helo=pallas.home.time-travellers.org) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1aj5de-0007Ww-9n; Thu, 24 Mar 2016 13:49:26 +0000
Date: Thu, 24 Mar 2016 14:49:20 +0100
From: Shane Kerr <shane@time-travellers.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20160324144920.64065eb3@pallas.home.time-travellers.org>
In-Reply-To: <20160323131144.GB798@mx2.yitter.info>
References: <20160322002647.E1C4644C86BB@rock.dv.isc.org> <CAC=TB12xXJNbmexMA4w5oLU+xhQbh=tKH=d7yKBLqEKLVsJikg@mail.gmail.com> <20160322010533.74A3244C8CF8@rock.dv.isc.org> <56F0A5F4.1050504@redbarn.org> <20160323131144.GB798@mx2.yitter.info>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; boundary="Sig_/ZObx_ei0hwyGQ6aX/U/eyD0"; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/do9GNpEgOA5RHoM8J8lllUq0OVo>
Cc: dnsop@ietf.org
Subject: [DNSOP] Stub resolvers and A+AAAA (was Introducing draft-vavrusa-dnsop-aaaa-for-free)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 13:50:54 -0000

Andrew,

At 2016-03-23 09:11:44 -0400
Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> On Mon, Mar 21, 2016 at 06:55:00PM -0700, Paul Vixie wrote:
> > i think we have to start planning for a world in which EDNS0 never reaches
> > 75% penetration due to middleboxes having the high ground.  
> 
> Well, you could get most of the way there for this proposal by having
> just recursives do it.  End users are mostly going to do happy
> eyeballs anyway, so if a recursive gets the AAAA with the A its own
> load goes down because it can answer more stuff from cache.

I'd like to argue that supporting A+AAAA on the stub side is
potentially huge.

Given that 90%+ of a recursive resolver's time is spent reading stuff
out of cache, being able to get the data to clients with fewer queries
seems huge to me. This is a big, fat win for resolver operators.

It also seems not hugely complicated.

On the stub resolver side, it should be relatively simple to discover if
this functionality is supported, and use it if it is. We could add a
special query for this that a host can use for this, or any of 100
other methods.
 
On the recursive resolver side, it should not impact performance, as no
additional searches should be required to get both the A and AAAA data
for a recursive resolver. While there is additional logic to handle this
approach (because of issues of collecting A and AAAA together into a
single reply), it's not hugely complicated (at least not compared to all
of the other the crap that resolvers have to do while talking to the
authoritative world).

Cheers,

--
Shane