Re: [Add] meeting hum: should the IETF take up this work?

Neil Cook <neil.cook@open-xchange.com> Thu, 25 July 2019 07:57 UTC

Return-Path: <neil.cook@open-xchange.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8C3120326 for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 00:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 2i_0IzNgtmUT for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 00:57:28 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 A73DE120309 for <add@ietf.org>; Thu, 25 Jul 2019 00:57:27 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id DF1236A32E; Thu, 25 Jul 2019 09:57:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1564041442; bh=hEDiXEXLkPBXBQiDJAr3UPH2i1HHTZqbxtxnKK0nObc=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=88BwRhPC7PG3IGGtmNzmK4cGvRlKfwS/d8RDRqLafPfsSnGFYdOvhY7wTYPJQuDhp 1g2/UNAikOT8ZQKvf4sz93CFHKaNEvKYLR5+UHIn33TyCInkCpK80t+VvDujUJKaha Ipkm//1CNXgj5fIb4DyoeBjTK2STm5b0jeExaFC5hJKVAJy38MLb7uEk+D1RoMU8MH 7P2tF98UGuDOESODIigdtUnIjTLifVFkpuHxRT29gabnSfa9pSSMGfcigdRt1Mk2Lx p6wJU3Zy1iVd47OF+VMcDOThsHU3g4XlIdLnP8/qLBw3OBqlwtLUdiUwyKKzUiCw7z Lu8MYlORUaGxg==
Received: from [192.168.1.128] (host217-42-7-160.range217-42.btcentralplus.com [217.42.7.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id A32DB3C02A7; Thu, 25 Jul 2019 09:57:22 +0200 (CEST)
From: Neil Cook <neil.cook@open-xchange.com>
Message-Id: <821B448B-F7EA-46A5-837D-DA0E8C60643A@open-xchange.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F1DA972A-9CA4-4364-AF86-AE8CF771F598"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 25 Jul 2019 08:57:21 +0100
In-Reply-To: <20190724165951.GB29051@laperouse.bortzmeyer.org>
Cc: Jim Reid <jim@rfc1035.com>, add@ietf.org, Rob Sayre <sayrer@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com> <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com> <8F094057-DFBC-4732-9DA4-BE46E7914C8A@rfc1035.com> <20190724165951.GB29051@laperouse.bortzmeyer.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Pw2Ajez5KZW0VjfY69Pqt0IA6aE>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 07:57:30 -0000

Stephane,

> On 24 Jul 2019, at 17:59, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> On Tue, Jul 23, 2019 at 11:45:07PM +0100,
> Jim Reid <jim@rfc1035.com> wrote 
> a message of 16 lines which said:
> 
>> And FWIW the success of DoH deployment -- for some definition of
>> success -- seems to rest solely in the hands of a very small number
>> of dominant players.
> 
> It depends on us. Or, rather, on it depends on a more general group,
> the group of people who write, install and manage DoH resolvers. The
> more they will be, the less users will depend on a few servers.
> 
> My hope is we will see many DoH resolvers (not always public).
> 

Running a public resolver takes a large amount of money and time, with no monetary reward for your efforts. Very few companies can afford to do that. Thus it seems far more likely that we’ll end up with a small number of dominant players as Jim suggests.

But let’s say I decide to run my own non-public DoH  resolver on my network at home. Firefox won’t have it on their list of TRRs, and if as you suggest, the discovery drafts are pointless and so don’t proceed, no application will ever find out about it, unless I configure it manually on every single application and computer in my house (not even mentioning those IoT devices that I can’t configure). 

It is also possible that we end up with a large number of public DoH resolvers which mine your personal data for profit. Given the current business model of the internet that is entirely possible. 

Neil

> -- 
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add


Neil Cook
neil.cook@open-xchange.com

-------------------------------------------------------------------------------------
Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738
Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin 
Chairman of the Board: Richard Seibt

European Office: 
Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 
Managing Director: Frank Hoberg

US Office: 
Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA 
-------------------------------------------------------------------------------------