Re: [Add] Draft on deployment models for Internet infrastructure

Rob Sayre <sayrer@gmail.com> Sun, 17 November 2019 03:34 UTC

Return-Path: <sayrer@gmail.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 96828120836 for <add@ietfa.amsl.com>; Sat, 16 Nov 2019 19:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 zWAaF0Z1VyTX for <add@ietfa.amsl.com>; Sat, 16 Nov 2019 19:34:35 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65582120835 for <add@ietf.org>; Sat, 16 Nov 2019 19:34:35 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id 1so14877365iou.4 for <add@ietf.org>; Sat, 16 Nov 2019 19:34:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/DC3dOWbEFUpX+H7FEvnm0E54OFKBkIyw1RpRV8XAUE=; b=RtdLGZRqlf9PsIAVD+SADEajs1jRARVDzQT8CEbMgcpLvi6LwKroRg1vgv97EqiTiL AcYHvA2j8GorU12CkrmKhWaOVh/GYapUq7ijB5ZpoG0bZiV7LNkqcFkydz1134Hdpf7K UZOO+c/4nWvxVW9Hn0JxRya6WvqN/4rU++s2OOPM79pVinfjCyT3oOm2h5WkwG+7k3Ds q9v3wfDMkycMlJpioVVWJziPFp5JimpeHENiVzh2MkrLseAGPNgu/0bUFMZVOHFbAk4o sYHTL2aSQ4r/HuQfSZdpCxC9X8XQiElWx0p9pHS7RdB4ITJ3a/8H/JN+pRy1/4REW627 p+0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/DC3dOWbEFUpX+H7FEvnm0E54OFKBkIyw1RpRV8XAUE=; b=R7QN8iQy7u+LIBgoKCRcpE8D0tn9nPHcljuBH1GTFuahdIXQ7VN+RXkPePl32XEvKP ylpMuh0PCmtA7N7/0/YXexXknTmSLMuO8gaE/wVqtV/oTiKT9vsbsp8xEnnvh3stRwFE Cfw6O+zzmHZ6h60a0RvT+uht8z6myBP7uRrFfB7cVpoT3yifPhBThFB//ns9PfSL3Bjd qJIAEDX4QGcCD+FngCjBfkMSf5/yYl53PeD7OLrzagF9DVw/kGq+GYRWYOptnl/PApSW yeYLOZj859YFJEj6LOjb8LGF/6VtXkK2A4ouJhMBqrjXmI552NZrKo5IEWIE3Z84bcSp wPbA==
X-Gm-Message-State: APjAAAXlomcRxMS11tXEq1rnSlQRbYV7dDli8CH1EAubSAjIM9sO2Ts0 c4BL5dsq8TEsfo5j0rzoWH/GHmZKqNKEogQDqytHmmAx
X-Google-Smtp-Source: APXvYqwu86PjT+Y/402OT4Crny1I+ovyQu0MLq3eeNih5F9uUGe8hPJr4H3Rxo3z1gbBZ6gCzDp3q7Dsn2rBJRx+Vek=
X-Received: by 2002:a5d:8b83:: with SMTP id p3mr744277iol.189.1573961674436; Sat, 16 Nov 2019 19:34:34 -0800 (PST)
MIME-Version: 1.0
References: <BFE6C273-41BF-4A4A-B25A-2F92DBA29357@piuha.net>
In-Reply-To: <BFE6C273-41BF-4A4A-B25A-2F92DBA29357@piuha.net>
From: Rob Sayre <sayrer@gmail.com>
Date: Sat, 16 Nov 2019 19:34:22 -0800
Message-ID: <CAChr6SznFn_sn07t_xCd451KxqASB_SiOZKj84m88_YNqDkVzA@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007eb33c0597828290"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Aeyu8nP44lbX-yOYSTRhA_AhZ24>
Subject: Re: [Add] Draft on deployment models for Internet infrastructure
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: Sun, 17 Nov 2019 03:34:38 -0000

On Sat, Nov 16, 2019 at 7:20 PM Jari Arkko <jari.arkko@piuha.net> wrote:

> I also wanted to point people to a draft that talks about centralised and
> other deployment models. This draft is about a broader topic than the
> DNS, more generally about anything in the Internet infrastructure. But
> it is also applicable for DNS. Comments and other observations are
> again appreciated.
>
>
> https://tools.ietf.org/html/draft-arkko-arch-infrastructure-centralisation-00


I've already read this draft, so I hope this response will not be viewed as
reflexive.

The idea that encrypted DNS will result in increased centralization is
unsubstantiated. For example, the way unencrypted DNS traffic enables
centralized surveillance at the network layer is well known even in
pop-science publications:

https://www.wired.com/2013/06/nsa-whistleblower-klein/

Encrypted DNS might change the locations of centralization. That is a
phenomenon that should be carefully studied, imho. It doesn't seem like a
structural weakness, but it could be neutral.

thanks,
Rob