IETF Logo Mail Archive

Re: [Add] Followup from ADD session today

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 24 July 2019 20:50 UTC

Return-Path: <stephane@laperouse.bortzmeyer.org>
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 8E3F9120637 for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 13:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LXJvQI63iCkK for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 13:50:12 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (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 5A89D12060C for <add@ietf.org>; Wed, 24 Jul 2019 13:50:12 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 06CA4A052F; Wed, 24 Jul 2019 22:50:11 +0200 (CEST)
Received: by godin (Postfix, from userid 1000) id 52522EC0AFD; Wed, 24 Jul 2019 22:46:50 +0200 (CEST)
Date: Wed, 24 Jul 2019 16:46:50 -0400
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Bret Jordan <jordan.ietf@gmail.com>
Cc: Arnaud Taddei <Arnaud.Taddei.IETF@protonmail.com>, "add@ietf.org" <add@ietf.org>, Barry Leiba <barryleiba.mailing.lists@gmail.com>
Message-ID: <20190724204650.GD5078@laperouse.bortzmeyer.org>
References: <WWG1Fgpd10sfGeSNhDiKMUmG4HAaAQVIVcAKP8tgh3SSVpqoZ0OUeW6ItVKBS68AgMAZ_YgwPKaaiJ0GIxyylNJBjPE1A95SP_YpCkJUJ8s=@protonmail.com> <06B41162-5936-4BF7-A9D6-3D864BB93ED2@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <06B41162-5936-4BF7-A9D6-3D864BB93ED2@gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 18.04 (bionic)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/4WN63EppRMiZKbCtUTaR5DDYupo>
Subject: Re: [Add] Followup from ADD session today
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: Wed, 24 Jul 2019 20:50:14 -0000

On Tue, Jul 23, 2019 at 10:14:55PM -0400,
 Bret Jordan <jordan.ietf@gmail.com> wrote 
 a message of 334 lines which said:

> Imaging an app being installed on a device that allows a user to
> browse the web. It has a hard coded DoH server that it wants to use,
> that points to the DoH server of its choice.  The app can add as
> many other headers it wants to ensure that it can fully track that
> user and application, no matter where they are.  So no matter where
> that client is, you will always be able to have a perfect telemetry
> of everything they have done and when they do it.

Imagine an app being installed on a device that allows a user to
browse the web. It uses a lot of trackers and send a lot of data to
many actors everywhere.

You have just described the vast majority of apps that one can found
today on Google Play or App Store. (See
<https://exodus-privacy.eu.org/>.)  In what way is it a DoH issue?
Apps can send tracking data and they actually do it, and they did it
long before RFC 8484. Why was there no complaint? Why using this as an
anti-DoH argument?

v2.23.0 | Report a Bug | By Email