Re: [Doh] [DNSOP] New I-D: draft-reid-doh-operator

Jared Mauch <jared@puck.nether.net> Fri, 22 March 2019 18:59 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA43D1314CC; Fri, 22 Mar 2019 11:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 z_G2iJ9Bql4E; Fri, 22 Mar 2019 11:59:37 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C3B81314C7; Fri, 22 Mar 2019 11:59:37 -0700 (PDT)
Received: from [100.170.95.150] (unknown [172.56.7.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id EFFB9541209; Fri, 22 Mar 2019 14:59:34 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <CAH1iCir4A9Af5FfG4YqiqxjEHDYmqdFZLwa6+Y6HJwLTM0id8w@mail.gmail.com>
Date: Fri, 22 Mar 2019 19:59:29 +0100
Cc: Jacques Latour <Jacques.Latour@cira.ca>, Ted Hardie <ted.ietf@gmail.com>, DoH WG <doh@ietf.org>, Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, Ralf Weber <dns@fl1ger.de>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D770C50-FDF8-481F-AFE8-642020A77694@puck.nether.net>
References: <155218771419.28706.1428072426137578566.idtracker@ietfa.amsl.com> <1914607.BasjITR8KA@linux-9daj> <CA+9kkMAYR19CCCLN00A5Oy_=9Z97FQogCz-vdC=M7Ffn47fTgQ@mail.gmail.com> <1900056.F7IrilhNgi@linux-9daj> <CA+9kkMCgmzjbPM+DTUYuS3OsT+wOCmsyaGPg6fPu=w-ibL=NrA@mail.gmail.com> <5F768C24-4ECF-4369-9D51-B90C4426409B@fl1ger.de> <428d5ff2b5704cdf956a5919e330e4dc@cira.ca> <CAH1iCir4A9Af5FfG4YqiqxjEHDYmqdFZLwa6+Y6HJwLTM0id8w@mail.gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/LczpfU2ejx-jVtXmDfxWCSgLgdk>
Subject: Re: [Doh] [DNSOP] New I-D: draft-reid-doh-operator
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2019 18:59:39 -0000

> On Mar 21, 2019, at 11:29 PM, Brian Dickson <brian.peter.dickson@gmail.com> wrote:
> 
> I realize, expressiveness adds complexity. However, it does avoid assumptions and overloading.
> 
> The main criteria is agreement on client vs server (i.e. standardize this stuff), and possibly also add the network as another party involved (for upstream transit ISP vs local ISP), if they have differing policies for allowing offsite/third-party DoH or DoT.

So my thoughts on this real quick: one of the reasons many people are using centralized services like 8.8.8.8 (for example) is its complex to run these servers properly. 

I’m worried about this additional complexity breaking the camels back, or deployment being relegated to those of us that may have overly complex home networks. 

The options and matrix add in complexity when a simple approach is likely desired or needed. 

The small networks that do not run their own servers won’t change. The medium where it’s on the bubble will further centralize. Is this what is needed in the community?

- Jared