Re: [DNSOP] opportunistic refresh and Happy Eyeballs

Mark Elkins <mje@posix.co.za> Tue, 15 August 2017 12:30 UTC

Return-Path: <mje@posix.co.za>
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 0734B1241FC for <dnsop@ietfa.amsl.com>; Tue, 15 Aug 2017 05:30:31 -0700 (PDT)
X-Quarantine-ID: <xb4HoJbd_h99>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
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, SPF_PASS=-0.001, URIBL_BLOCKED=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 xb4HoJbd_h99 for <dnsop@ietfa.amsl.com>; Tue, 15 Aug 2017 05:30:28 -0700 (PDT)
Received: from relay.vweb.co.za (relay.vweb.co.za [IPv6:2001:43f8:790:61::200]) (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 A1B9612008A for <dnsop@ietf.org>; Tue, 15 Aug 2017 05:30:26 -0700 (PDT)
Received: from [165.255.158.101] (port=49554 helo=mjelap.posix.co.za) by relay.vweb.co.za with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from <mje@posix.co.za>) id 1dhazF-00071H-I8 for dnsop@ietf.org; Tue, 15 Aug 2017 14:30:22 +0200
Reply-To: mje@posix.co.za
To: dnsop@ietf.org
References: <alpine.DEB.2.20.1708150911470.3655@uplift.swm.pp.se> <9EED4C56-8B35-4013-861D-0B86F66483E0@puck.nether.net> <aee0d624-dc18-25d2-1a40-e16b1a6d4a85@fredan.se>
From: Mark Elkins <mje@posix.co.za>
Organization: Posix Systems
Message-ID: <22432372-9229-0092-6a28-f6bd75c3a3a3@posix.co.za>
Date: Tue, 15 Aug 2017 14:29:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <aee0d624-dc18-25d2-1a40-e16b1a6d4a85@fredan.se>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ud70usy4RIg9R0dyUflZSp0MIuY>
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 12:30:31 -0000

The Query portion of the DNS protocol can probably ask more than one
question at a time. (I think I've only ever seen "QUERY: 1" in all the
digs I've ever done - but might be wrong).

Of course - if one were to ask  for both an A and AAAA at the same time
- one gets the same problem - how does one sort out whether there is an
AAAA if there is a valid answer to A, and visa versa.

"dig machine.domain.com a machine.domain.com aaaa" - actually works but
does this as two queries.

I think the cleanest way would be a new pseudo record (ANYA) as the
reply would have to be a single complete resource set of all the
possible answers (A's and AAAA's), all with one covering signature if
DNSSEC is involved. One would then programmatically know then what was
available.


On 15/08/2017 14:00, fredrik danerklint wrote:
>
>>
>>> What is the opinion of this wg on that topic?
>> There has been much discussion about doing away with any/255 and I
>> seem to recall some discussion of a ANYA type which would return AAAA
>> and A.
>>
>> This is something I see value in being implemented.
>>
>>
> Would it be easier in this case to implement this behavior instead of
> creating a new type?
>
> If a authority DNS server is getting a question type of A and it has
> both A and AAAA records, put both in the answer. The same for a
> question type of AAAA, if it has both A and AAAA records put those in
> the answer.
>
> If it got a question type of A and it doesn't have the A record but it
> has the AAAA record, what should the behavior be in this case? The
> same for other way around of course, question type AAAA but it does
> not have the AAAA record, only the A record. Should it add the known
> record or not at all?
>

-- 
Mark James ELKINS  -  Posix Systems - (South) Africa
mje@posix.co.za       Tel: +27.128070590  Cell: +27.826010496
For fast, reliable, low cost Internet in ZA: https://ftth.posix.co.za