Re: [Resolverless-dns] Load-balancing concerns

Dave Lawrence <tale@dd.org> Thu, 08 November 2018 09:44 UTC

Return-Path: <tale@dd.org>
X-Original-To: resolverless-dns@ietfa.amsl.com
Delivered-To: resolverless-dns@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23ACB12D4E7 for <resolverless-dns@ietfa.amsl.com>; Thu, 8 Nov 2018 01:44:53 -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 Y-3ptaoMZeAM for <resolverless-dns@ietfa.amsl.com>; Thu, 8 Nov 2018 01:44:52 -0800 (PST)
Received: from gro.dd.org (gro.dd.org [207.136.192.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F9E01293FB for <resolverless-dns@ietf.org>; Thu, 8 Nov 2018 01:44:52 -0800 (PST)
Received: by gro.dd.org (Postfix, from userid 102) id 470AD32AC2; Thu, 8 Nov 2018 04:44:51 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23524.1427.267084.889272@gro.dd.org>
Date: Thu, 8 Nov 2018 04:44:51 -0500
From: Dave Lawrence <tale@dd.org>
To: resolverless-dns@ietf.org
In-Reply-To: <CAN-AkJs0j4cwBXjK-Q16D4cHgdU_ncO4hu373JYsU_VdvSuzjw@mail.gmail.com>
References: <CAN-AkJtKbgy0RNf6c5TZd3j5SsjaYe4CwtkaQzYA=FhrrAvJAA@mail.gmail.com> <8849CBF3-1950-44BB-95C9-16F35F79E350@rfc1035.com> <CAN-AkJs0j4cwBXjK-Q16D4cHgdU_ncO4hu373JYsU_VdvSuzjw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/RW4vVJ_bKbxYUx4LOLz-YDtU-k8>
Subject: Re: [Resolverless-dns] Load-balancing concerns
X-BeenThere: resolverless-dns@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Resolverless DNS <resolverless-dns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/resolverless-dns/>
List-Post: <mailto:resolverless-dns@ietf.org>
List-Help: <mailto:resolverless-dns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 09:44:53 -0000

Justin Henck writes:
> How is a "resolverless" (unrequested resolution?) solution here any
> different from sharing a recursive, if we use ECS or if the primary
> service is widely deployed?

The landscape is complicated.  In many cases it will offer the same
results.  In some cases it will be demonstrably more bad.  In some
cases it might even be a bit better.    There are a lot of variables
to suss out here.

> E.g. it seems to me that there are three scenarios:
> 1) really large globally distributed services implementing will act like
> geographicaply distributed resolvers, which some of them also are

Right this one probably ends up looking largely like a regular
recursive resolver now, so is basically fine.

> 2) small single-datacenter services won't produce enough traffic to matter

I think maybe we shouldn't be cavalier with "to matter", because
it could very well matter quite a lot to the clients here.

> 3) large single-datacenter services might cause a problem

Yep.

> Are there other negative scenarios? I suppose 1 but not very well
> distributed?

Yep,