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

Neil Cook <neil.cook@open-xchange.com> Thu, 25 July 2019 14:16 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 9267E120071 for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 07:16:33 -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 c7mMOCFBqpbd for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 07:16:31 -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 36921120131 for <add@ietf.org>; Thu, 25 Jul 2019 07:16:23 -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 3EC2B6A34B; Thu, 25 Jul 2019 16:16:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1564064178; bh=Tu9yg3XxPJ45Dm63BXNhaF5tC4wEDSzhUYUlw9I6w8M=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=Vv5yEeOLomCw45EXWeOvfWAY01zc2bMPTEYyfhdPCmXlxXPrs5jpMSGtm3wWDQSqZ IKR3Hj/kbmeu01Wp/goqTcophJr6FuMFucMTnJTlg4RONYZHXk3B+us4vUWC4+kwrW OHfANf4VWSvYg2HatuoGyb4fhoGjToCJkrWljb6YfiaTQDx8vzTud9e2XTn35BiNMO sIID6iXUV+RZF6Kd4dFlPn1gdzrDohj7Lf0Kc51D+YsO4QxLo49tXG7TZr/Jp3go3B Ht+OyNoTCUJOI4KpUHCUejebF3FZMS+zKEdfQnT8q3TVXDiJRkuKi0wlMsBSMGLeRO C6Zdm+7mTkeAw==
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 C44253C042B; Thu, 25 Jul 2019 16:16:17 +0200 (CEST)
From: Neil Cook <neil.cook@open-xchange.com>
Message-Id: <5A359D3E-2272-4240-BD41-55646393BA9E@open-xchange.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_54557EAF-2599-477B-91F3-A9EB31A1A9D2"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 25 Jul 2019 15:16:16 +0100
In-Reply-To: <d653d422-4a71-9fab-fd2e-b8ddaa476f91@nostrum.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Jim Reid <jim@rfc1035.com>, add@ietf.org, Rob Sayre <sayrer@gmail.com>
To: Adam Roach <adam@nostrum.com>
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> <821B448B-F7EA-46A5-837D-DA0E8C60643A@open-xchange.com> <d653d422-4a71-9fab-fd2e-b8ddaa476f91@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Ur1d7rBPwlH0J6jxJZ01jZVcHf4>
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 14:16:34 -0000

Adam,

JFYI no connection was implied. I deliberately put the comment about data mining in a separate paragraph, and said “it is also possible”.

Neil

> On 25 Jul 2019, at 15:11, Adam Roach <adam@nostrum.com> wrote:
> 
> On 7/25/19 03:57, Neil Cook wrote:
>> 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.
> 
> 
> Since you mention Firefox's TRR list and then mention data mining (with an implied connection), I'd like to point out yet again that one of the key criteria for appearing on that list is an agreement to treat resolution data according to a strict set of privacy-protecting provisions. You can see, for example, Cloudflare's associated privacy policy at https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/
> 
> I'm going to pre-reply to a frequent response that the lack of direct contractual relationship between users and Cloudflare is problematic. Even if you don't trust Mozilla's contractual agreement with Cloudflare to provide protection here, I would think that FTC v. Facebook (2019) [1] should serve as a pretty vivid illustration of what happens when a US company operates outside its published privacy policy.
> 
> /a
> 
> ____
> [1] https://www.ftc.gov/news-events/press-releases/2019/07/ftc-imposes-5-billion-penalty-sweeping-new-privacy-restrictions
> 


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 
-------------------------------------------------------------------------------------