Re: [DNSOP] opportunistic refresh and Happy Eyeballs
Paul Vixie <paul@redbarn.org> Tue, 15 August 2017 19:51 UTC
Return-Path: <paul@redbarn.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 28EB81321F0 for <dnsop@ietfa.amsl.com>; Tue, 15 Aug 2017 12:51:00 -0700 (PDT)
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 JxS1zd8LB-RQ for <dnsop@ietfa.amsl.com>; Tue, 15 Aug 2017 12:50:58 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D380D1321EB for <dnsop@ietf.org>; Tue, 15 Aug 2017 12:50:58 -0700 (PDT)
Received: from [172.16.101.226] (96-82-111-94-static.hfc.comcastbusiness.net [96.82.111.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 99B6C61FF3; Tue, 15 Aug 2017 19:50:58 +0000 (UTC)
Message-ID: <599350A1.2050209@redbarn.org>
Date: Tue, 15 Aug 2017 12:50:57 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.16 (Windows/20170718)
MIME-Version: 1.0
To: Jared Mauch <jared@puck.nether.net>
CC: dnsop@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>
References: <alpine.DEB.2.20.1708150911470.3655@uplift.swm.pp.se> <9EED4C56-8B35-4013-861D-0B86F66483E0@puck.nether.net> <59932F2F.9030504@redbarn.org> <B6EEA868-368F-4C65-B40F-609C54C522C6@puck.nether.net>
In-Reply-To: <B6EEA868-368F-4C65-B40F-609C54C522C6@puck.nether.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kb2rvl65Xv0RGp9UJUMeIO__Ip4>
Subject: Re: [DNSOP] opportunistic refresh and Happy Eyeballs
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 15 Aug 2017 19:51:00 -0000
Jared Mauch wrote: >> we can specify that AAAA be sent as additional data for QTYPE=A, and >> that A be sent as additional data when QTYPE=AAAA. >> >> given identical deployment curves along both the ANYA and >> additional-data timelines, we will get identical results. > > As this is DNSOP, what implementations support this? of authorities, none. of recursives as initiators, most. of recursives as responders, none. of stubs, some. there are two measurable lobes here. one is now, where any authority who adopts this behaviour is likely to pre-seed the recursive initiator's cache with "the other answer" (among A and AAAA), and any stub who makes two queries in series (AAAA then A) will get a faster answer to the second query. the other is the future, where stubs are taught to notice the additional data section and begin to avoid the second query, and where recursive responders both ensure that they do cache additional data whose owner is the same as the effective qname, and begin to send additional data to stubs. so, the benefit begins immediately, but gets better over time, and there is no new signalling required, and nothing ever breaks, and it is never necessary to try-then-fallback (causing additional round trips.) have no fear. every few years this topic comes up, and i say what i'm saying, and we don't do it, and then people ask for QDCOUNT>1 again. so we are right on track at this stage of the thread. had the response to "resimprove" been better, i would have written this up before now. -- P Vixie
- [DNSOP] opportunistic refresh and Happy Eyeballs Mikael Abrahamsson
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Mikael Abrahamsson
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Jared Mauch
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Ted Lemon
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… fredrik danerklint
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Mark Elkins
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Vladimír Čunát
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Hoffman
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… 神明達哉
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Tony Finch
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Jared Mauch
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Viktor Dukhovni
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Bob Halley
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Mark Andrews
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Paul Vixie
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Warren Kumari
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Warren Kumari
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Mukund Sivaraman
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Ralf Weber
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Warren Kumari
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Petr Špaček
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Brian Wellington
- Re: [DNSOP] opportunistic refresh and Happy Eyeba… Vladimír Čunát