Re: [Add] What to do in this potential working group

Jari Arkko <jari.arkko@piuha.net> Wed, 21 August 2019 10:55 UTC

Return-Path: <jari.arkko@piuha.net>
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 5D463120041 for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 03:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 oWybWt1UEgLG for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 03:55:09 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 565A81200B4 for <add@ietf.org>; Wed, 21 Aug 2019 03:55:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ED9356600F1; Wed, 21 Aug 2019 13:55:06 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NrCwFkg5EVRT; Wed, 21 Aug 2019 13:55:05 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 9FB04660202; Wed, 21 Aug 2019 13:55:05 +0300 (EEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com>
Date: Wed, 21 Aug 2019 13:55:05 +0300
Cc: ADD Mailing list <add@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/8UpW28gMApfCEbc01GUajom-eYc>
Subject: Re: [Add] What to do in this potential working group
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, 21 Aug 2019 10:55:11 -0000

Ekr,

I fully realise that there will be differences of viewpoints when it comes to the trustworthiness of individual DNS service providers.

But I was trying to make a different point. While we may disagree which provider I’d like to use for the DNS service, I think it would be quite reasonable for us to agree that if all of us put our all our queries in one place (whatever that is) that this causes severe problems:

- That place becomes immensely valuable from a commercial data mining perspective. There’s a risk that it will at least at some point be used for data mining, despite whatever the intentions of the people who set this system up now is.

- That place becomes immensely interesting to for governments to tap. There’s a risk that this tapping is either already happening or will be happening going forward, despite best intentions of the people who set it up or who manage it.

- That places becomes critical infrastructure and a weak point that we do not need in the Internet.

As a result, I would like to suggest that the IETF actually concludes the above and recommends against this practice.

For whatever it is worth, I can understand some motivations for doing something like this e.g. in browsers. Some good reasons and potentially also some not so good reasons. But even with that background, it is difficult for me to imagine a worse act for the Internet than making browsers call home for every action of the user. The privacy impacts for the users are unimaginably bad.

A few years ago we realised that surveillance organisations were looking at people's traffic, and we managed to change the Internet to protect this traffic with cryptographic means. I think it is to think about the next step, and ensure that we don’t create an Internet architecture that puts everyone’s data at central location.

Obviously, encrypted DNS is still hugely important, as are global DNS services. However, the deployment model of using one (or a small number of) providers is just wrong. That would be fixable.

Jari