Re: [Resolverless-dns] Load-balancing concerns

manu tman <chantr4@gmail.com> Thu, 08 November 2018 06:44 UTC

Return-Path: <chantr4@gmail.com>
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 E5B8D130DC8 for <resolverless-dns@ietfa.amsl.com>; Wed, 7 Nov 2018 22:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bIRvhEFuyths for <resolverless-dns@ietfa.amsl.com>; Wed, 7 Nov 2018 22:44:29 -0800 (PST)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 400BA130E04 for <resolverless-dns@ietf.org>; Wed, 7 Nov 2018 22:44:29 -0800 (PST)
Received: by mail-it1-x136.google.com with SMTP id k206-v6so161963ite.0 for <resolverless-dns@ietf.org>; Wed, 07 Nov 2018 22:44:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YAoysYwL1CpgBshH9vJx8xXdyhSekivEaYBVQjSsSCU=; b=CWBpsFpmXTOBbjsBJmJhkzklzB39dfxmS4P/Ie+roizhm7OooCS5P/JdkRrYhhqwuo ozQwinfIOyu726AtHrNOctlxkAWH3xaODPws+CZLylUuFvMheQ1lLuSUVPohQB74BCMC hUEIctF2h5nSAxb7RBIglDKLRjMGUY3BXA2mlul8MKIxBwtoLTFmKAddAhojbDXpsHGd aKNmNrCpmBFJ9sZ3ZfVOap2LshA6t5dc5wZvaH2CE+M6cYyA9wcqlUM2sQkEQdSdvIoe ngFCvNXvoHaSSO4ch8EdEPlRDO+uJtLWJAMKWIb9syxnCnG9uDfLFj932XV8zkonJtz1 iYng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YAoysYwL1CpgBshH9vJx8xXdyhSekivEaYBVQjSsSCU=; b=Pw/7tO4d837BbBvwLPzmqvGjiJcpgxgd9g1AydREIQ27OdIoTbHWbpge2UO1Y0LlIz f3mB5cmhr9B6fWvXh84JhAE1oZUlIrMC6jORZmDzzxCkI4T/4qojm7OiqELFtj+V5meE /g7/k2ZHDFAxVG5XCKPlXwie3t7CwQj+jyUU5emGf+LNFB9zr83cB1q+OXG5Wth4rb+T poBLvW1CJYd4VCnAERng05ftsmoNa6hI+c3M5ShCmj8AQFxXq8LHgt4fAxyr8GV5q51i UANnV4+EwwbBHzvvw1s9dThSIAh4g6LS8yTgBa/vfahUCpwSlqSPxeyEX+TxE7mPuEmE 4L/Q==
X-Gm-Message-State: AGRZ1gJVmIR7D19WWw2h0BsYsA6dhqqfj8K3WnGkzXIDWV4ug1RX3NDZ r1evo5+UemuYl7gC4vmSMccYkWRL4KYtLo3Df6/+pu8X
X-Google-Smtp-Source: AJdET5fDhx9yi0HcnqT7bhI9IFX2Q+uKElTCE9q00bS6isB0s512L7ufj7lLBtILGUfsznh7jFYbZodkdPtYyJ294qg=
X-Received: by 2002:a02:94d:: with SMTP id f74-v6mr3214869jad.85.1541659468411; Wed, 07 Nov 2018 22:44:28 -0800 (PST)
MIME-Version: 1.0
References: <CAN-AkJt=Oe5oO19Zu-fKqzHvTD5P4PcrGq8t8Hg3rNkUQxC8WA@mail.gmail.com> <23523.55497.532269.465187@gro.dd.org>
In-Reply-To: <23523.55497.532269.465187@gro.dd.org>
From: manu tman <chantr4@gmail.com>
Date: Thu, 08 Nov 2018 13:44:17 +0700
Message-ID: <CAArYzrLR52xtoCLs4S7wATXnERs_ea5CCz8ovC-8P5DSv7peng@mail.gmail.com>
To: Dave Lawrence <tale@dd.org>
Cc: resolverless-dns@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fabaa8057a219064"
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/39rTEqO-PgqhVNkch5NekV3krXE>
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 06:44:31 -0000

On Thu, Nov 8, 2018 at 1:33 PM Dave Lawrence <tale@dd.org> wrote:

>  If the DoH server can't do ECS or
> otherwise have mapping information from the authority, any customized
> answers it gets will be resolver-mapped just like a client talking to
> any traditional non-ECS resolver.


> Except that it will be based on the IP of the DoH server and not the
resolver of the client, which in most cases will be more representative of
the actual network location (ISP or subnets of ISP) of the client.

The DoH server will most likely be mapped to the “best” location for the
majority of the clients using the service at the cost of totally bad
selection for the ones that don’t fall in the majority bucket and its
neighbors.

Manu