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

"John R Levine" <johnl@taugh.com> Thu, 15 August 2019 19:09 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 F138B120127 for <resolverless-dns@ietfa.amsl.com>; Thu, 15 Aug 2019 12:09:19 -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=h3YF6hGG; dkim=pass (1536-bit key) header.d=taugh.com header.b=Fg8u9pbX
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 FPQq3GemMU88 for <resolverless-dns@ietfa.amsl.com>; Thu, 15 Aug 2019 12:09:17 -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 6D0EA120122 for <resolverless-dns@ietf.org>; Thu, 15 Aug 2019 12:09:17 -0700 (PDT)
Received: (qmail 40997 invoked from network); 15 Aug 2019 19:09:16 -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:content-id:user-agent; s=a022.5d55addc.k1908; i=johnl-iecc.com@submit.iecc.com; bh=RsbS2LUXDkLkyFxqxRPmxyEMFe3O0J1xKj9uBCg3ggU=; b=h3YF6hGGGVBwEGZu5UHbMkrAEZJo0dyRRneThe1EHkNmkRhA3rEfk8NqWy7dyoSP8s2cDhsUB9R9QBJXmXUbbzqP07qDVPlfd0MMlJofI3SoD3SDcjCYmF69gshC3sPuDPDNv7RpKbw5KaI4YAlDxMKy5iC06NsjUS1QTewgwFU/bRjQ9NcqlSL+LTUGEh9ZHHYcoh1eL1Ap89I5m3JDB+bxI+eEP1J9zct+U0YgCJaRxioYqQmhhiHuoJSC/oTy
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:content-id:user-agent; s=a022.5d55addc.k1908; olt=johnl-iecc.com@submit.iecc.com; bh=RsbS2LUXDkLkyFxqxRPmxyEMFe3O0J1xKj9uBCg3ggU=; b=Fg8u9pbXx18Ato8kso+Q7M7Dp9GYITsOCpIy4x9TWrh2vA5JC06AwTe3e5ulZJvy0UXr0WypE1FaLQtxFXnmgJzufrX5jbtCL/GafgNX/Pdn5yDCOOzCfUkmzLz+sT72o6K6Bu6KKqz/WnxZjAl4bISo3zkoFJjDCqc4js3W9VDiU+G0ymAk7zRuwFYfhJpiy5RWDnHDDtNLVmWrmM78wPt39Zi1iy+Y7/0yGLurTtpD4gzyh4zXcJHfwQquR4iR
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 19:09:16 -0000
Date: Thu, 15 Aug 2019 15:09:15 -0400
Message-ID: <alpine.OSX.2.21.9999.1908151419460.62452@ary.local>
From: John R Levine <johnl@taugh.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: resolverless-dns@ietf.org
In-Reply-To: <CA+9kkMDtGt0hMPv1szjoLuHsO1h5wPrsY-5LkJdDU5FcVKFSkA@mail.gmail.com>
References: <CAHbrMsBhR1yaLxQk7wZk54Jdf5nvkS03KC3UTae0Famu2+SV8g@mail.gmail.com> <20190815163938.CF9CB85D108@ary.local> <CA+9kkMDtGt0hMPv1szjoLuHsO1h5wPrsY-5LkJdDU5FcVKFSkA@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"
Content-ID: <alpine.OSX.2.21.9999.1908151445111.62272@ary.local>
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/_Xzq7WCWA0FtRFUAr9WOyWbBrfA>
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 19:09:20 -0000

I think I've seen rants that any interference with true DNS is evil (add 
DNSSEC to suit) but I think we can agree they're in the weeds.

> [ possible badness ] are:
>
> * new opportunities for circumvention for malware
> * increased likelihood for inappropriate exposure to distressing content
> (whether for adults or children)
> * new risks for regulatory or common imposition of other control surfaces

Not just distressing.  A lot of networks are inside organizations, and 
they have policy reasons to limit what things their employees can see, 
e.g., porn and gambling, or perhaps competitor's web sites if there's a 
risk of anti-competive collusion.  I've seen networks that force all 
outgoing port 53 traffic to their own resolver to more or less 
transparently enforce the policy.

> There is a further assumption that these risk go up as the level of
> sophistication for circumvention goes down.  I think many of these are
> predicated on an assumption that the non-local DNS has no filters, ...

Not at all, it's that the non-local DNS doesn't have the policy filters 
that the local DNS does.

> * new opportunity for a malicious configured service to provide false data
> to non-DNSSEC validating hosts or applications.
> * no opportunities for external services to provide access to split-DNS
> internal data.

That, too.  But the key point is that many networks do policy filtering 
and other people's DNS is unlikely to implement the same policy.

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