Re: [Resolverless-dns] Paper on Resolver-less DNS

"John R Levine" <johnl@taugh.com> Thu, 15 August 2019 22:21 UTC

Return-Path: <johnl@taugh.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 BB6191200C7 for <resolverless-dns@ietfa.amsl.com>; Thu, 15 Aug 2019 15:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=iXtPurcl; dkim=pass (1536-bit key) header.d=taugh.com header.b=Obifwhsz
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 ZPHyxVUmMaR5 for <resolverless-dns@ietfa.amsl.com>; Thu, 15 Aug 2019 15:21:41 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274F91200E7 for <resolverless-dns@ietf.org>; Thu, 15 Aug 2019 15:21:41 -0700 (PDT)
Received: (qmail 75322 invoked from network); 15 Aug 2019 22:21:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=12638.5d55daf4.k1908; i=johnl-iecc.com@submit.iecc.com; bh=zByuNvnxAmWiPXxS5IikXfsAYyw6Y5GXuvxied6EEII=; b=iXtPurclc0Zm8IPq3x8t+ayBGffMZSvbIKPW8jUNvX7QKxEyf2PIotDz9FReiglwjCZHPLn3lqQBHOBKv/cNSf0EBJF8EtTZglJnv8cpqyJCG7zLi9ErdePn91b1DXWrgKn8KqLd1o+nCRhJveigVEc1lunu6EHNljuyqrqr0GtHHn1KE3Ak3IQ2VfGmja3m+EHK3bRy2ogz9co5EURhmeX6NDHt/nLOi1jWkHuSBmsMTSr0Mb8GjjMv1Whj8nwL
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=12638.5d55daf4.k1908; olt=johnl-iecc.com@submit.iecc.com; bh=zByuNvnxAmWiPXxS5IikXfsAYyw6Y5GXuvxied6EEII=; b=Obifwhsz/5GWVtpP4k6T+FN+9CTrS6EkUnoeaTZ014+tuqKBeu0G5bKQEQGE8O7VQoS+/Q4Gw3QGyMCama5BaY4rvEfxYFwiDXI4AV5dZniIy+aF14061ZJhPOyTFnqpv7D9gO24iEGmohRfPR+dCKxgeGJ9jnd45gfXu4saUyE18o0XXY1nNigI0BJ5qwZNbRvi26R9RnZvKoFz7JfNxQXZ1/5k2mU6/9waZo2IGqWvtHn4IIDBMIC0v3ly2GB+
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 15 Aug 2019 22:21:39 -0000
Date: 15 Aug 2019 18:21:39 -0400
Message-ID: <alpine.OSX.2.21.9999.1908151819550.63257@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Eric Orth" <ericorth@google.com>
Cc: resolverless-dns@ietf.org
In-Reply-To: <CAMOjQcEnhov9AZMQSpDoF2k06P36bce0SNjKoLcquyDZk1q+KA@mail.gmail.com>
References: <CAHbrMsBhR1yaLxQk7wZk54Jdf5nvkS03KC3UTae0Famu2+SV8g@mail.gmail.com> <20190815163938.CF9CB85D108@ary.local> <CAMOjQcEnhov9AZMQSpDoF2k06P36bce0SNjKoLcquyDZk1q+KA@mail.gmail.com>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/8SjTb9FnOnSNtgoEW6EEBENVMTc>
Subject: Re: [Resolverless-dns] Paper on Resolver-less DNS
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, 15 Aug 2019 22:21:43 -0000

On Thu, 15 Aug 2019, Eric Orth wrote:
> My initial thinking is that we would then ideally only use
> resolverless DNS if we had knowledge that the in-use recursive resolver is
> not doing significant filtering.  But such a signal does not currently
> generally exist, so would we be limited to only doing resolverless DNS when
> the resolver is on a hardcoded list of non-filtering resolvers?

It's hard to imagine how you could get such a signal in a way that would 
be useful.  Who's going to publish "yeah, sure, bypass me, I don't care"?

There are heuristics like looking to see if it's one of the popular 
n.n.n.n public resolvers, but I wouldn't want to push it too far.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly