IETF Logo Mail Archive

Re: [Add] ECS privacy concerns, alternatives?

Paul Hoffman <paul.hoffman@icann.org> Wed, 17 April 2019 19:16 UTC

Return-Path: <paul.hoffman@icann.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 D98611200B8 for <add@ietfa.amsl.com>; Wed, 17 Apr 2019 12:16:54 -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 CwXVxkeYihDA for <add@ietfa.amsl.com>; Wed, 17 Apr 2019 12:16:53 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8BB912003E for <add@ietf.org>; Wed, 17 Apr 2019 12:16:53 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 17 Apr 2019 12:16:52 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Wed, 17 Apr 2019 12:16:52 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] ECS privacy concerns, alternatives?
Thread-Index: AQHU9VIczoYQ2gaYVUSW1kb/Zlej+w==
Date: Wed, 17 Apr 2019 19:16:51 +0000
Message-ID: <B09B3866-F3B2-4548-8FA0-D658BDE951D1@icann.org>
References: <297C80CE-F017-4F4A-80E2-79941E8B9E02@icann.org> <b64761dc-dfab-e4e1-4bfb-82d607efa590@riseup.net> <alpine.LRH.2.21.1904101324530.9940@bofh.nohats.ca> <64aeff58-6d68-4c4f-b991-2b2f62d193a0@www.fastmail.com> <90A5C5C4-373C-4B39-80C2-C115CD23CB4D@fl1ger.de> <994839978.18707.1554973716877@appsuite.open-xchange.com> <af5f5c76-0095-65a0-39d1-d29d4bb0e906@mozilla.com> <ybl36mn8b54.fsf@w7.hardakers.net> <f9d0cd98-db0c-7f42-d351-d9a5002c4765@mozilla.com> <21C5261E-9DE0-4CFD-A949-6E91DD0C2552@cable.comcast.com> <9FDAE487-6E98-4332-BB57-A626A02A6402@cable.comcast.com> <CAH1iCiqPqWCEmT0DSyzu-DRtna_p1SZXuiK15HHyTrjnX1iUaA@mail.gmail.com> <CAKC-DJgmb1J281Z2j4q1NbBgf+S5PmvkJfXPDkhfX_sT6cn_PA@mail.gmail.com> <CAH1iCiqMOJ0M1EiGKORf2VKysFEtWV69tP2G+W6M9CEPzf4QWA@mail.gmail.com> <E2CD69F8-1B6F-493F-B18E-918B4855E075@hopcount.ca>
In-Reply-To: <E2CD69F8-1B6F-493F-B18E-918B4855E075@hopcount.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CC9AF1304F274B46857A5BE1CDE065FB@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/S0shtu6tDjmlGXGSAsjFv0SxGVE>
Subject: Re: [Add] ECS privacy concerns, alternatives?
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, 17 Apr 2019 19:16:55 -0000

I propose that this thread could be moved to the DNSOP WG mailing list, where ECS originated. I say this because ECS is a privacy problem for non-ADD and ADD equally, and some uses of ADD (application does DoT to the user's normal external resolver) don't make ECS any worse.

The thread is indeed interesting, but it should probably be had where more developers are watching.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email