Re: [DNSOP] Draft for dynamic discovery of secure resolvers

Paul Vixie <paul@redbarn.org> Sun, 19 August 2018 00:37 UTC

Return-Path: <paul@redbarn.org>
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 D5779130F58 for <dnsop@ietfa.amsl.com>; Sat, 18 Aug 2018 17:37:15 -0700 (PDT)
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 JADumd_5fMu0 for <dnsop@ietfa.amsl.com>; Sat, 18 Aug 2018 17:37:14 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E78D3130E08 for <dnsop@ietf.org>; Sat, 18 Aug 2018 17:37:14 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:1c6f:2fd8:8c7b:9a62] (unknown [IPv6:2001:559:8000:c9:1c6f:2fd8:8c7b:9a62]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 69493892C7; Sun, 19 Aug 2018 00:37:14 +0000 (UTC)
Message-ID: <5B78BBB9.2070608@redbarn.org>
Date: Sat, 18 Aug 2018 17:37:13 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
CC: =?windows-1252?Q?Marek_Vavru=9Aa?= <mvavrusa=40cloudflare.com@dmarc.ietf.org>, dnsop <dnsop@ietf.org>
References: <CAC=TB13mUH2SDxFb4c3rOz0-Z6PE_r9i84_xK=dmLxiVr45+tA@mail.gmail.com> <CAPt1N1=-792WkQmbTigPdqOh0dONykYycG0hheOecoQa4ai=Hw@mail.gmail.com> <5B7893C9.7000703@redbarn.org> <CAPt1N1nj=g0nOsgHNvCosBg2va9pj228hKArpsukAzQ3jtX-gw@mail.gmail.com>
In-Reply-To: <CAPt1N1nj=g0nOsgHNvCosBg2va9pj228hKArpsukAzQ3jtX-gw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yMIN4u33nERXI5cPQ9geffzi9X4>
Subject: Re: [DNSOP] Draft for dynamic discovery of secure resolvers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 19 Aug 2018 00:37:16 -0000


Ted Lemon wrote:
> How will you block it?

at work we'll probably firewall all outbound tcp and require the use of 
proxies, which will do some kind of payload inspection.

at home i don't know yet but i'll likely just blacklist every known DOH 
endpoint, and tell my family, if you want netflix, go get a hotel room.

i will _not_ have my security policy dictated to me by mozilla and 
cloudflare. "my network; my rules" is how it was when people were suing 
me for publishing the MAPS RBL back in the 1990's, and it's how it'll be 
today.

-- 
P Vixie