Re: [Doh] Proposal for a side-meeting on services centralization at IETF 104 Prague

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 12 March 2019 09:01 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D157128678; Tue, 12 Mar 2019 02:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 gyMI9hm94GJp; Tue, 12 Mar 2019 02:01:44 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 59CD312B001; Tue, 12 Mar 2019 02:01:44 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D5F3A280298; Tue, 12 Mar 2019 10:01:42 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id CEA4628033B; Tue, 12 Mar 2019 10:01:42 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id C6AB5280298; Tue, 12 Mar 2019 10:01:42 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C0930663E720; Tue, 12 Mar 2019 10:01:42 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id B0C9840235; Tue, 12 Mar 2019 10:01:42 +0100 (CET)
Date: Tue, 12 Mar 2019 10:01:42 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, doh@ietf.org, dns-privacy@ietf.org, dnsop@ietf.org, hrpc@irtf.org
Message-ID: <20190312090142.s32hdimbozsrbovt@nic.fr>
References: <20190311170218.o5hitvysuefhjjxk@nic.fr> <1829067625.16839.1552327024048@appsuite.open-xchange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1829067625.16839.1552327024048@appsuite.open-xchange.com>
X-Operating-System: Debian GNU/Linux 9.8
X-Kernel: Linux 4.9.0-8-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000004, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.3.12.85117
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/AoiLMHtBuBIqq_mgGCtbZEoy270>
Subject: Re: [Doh] Proposal for a side-meeting on services centralization at IETF 104 Prague
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2019 09:01:47 -0000

On Mon, Mar 11, 2019 at 06:57:03PM +0100,
 Vittorio Bertola <vittorio.bertola@open-xchange.com> wrote 
 a message of 18 lines which said:

> Moreover, centralization is not the only Do*-related problem
> category that has been raised (my draft alone lists eight others).

IMHO, this is precisely the biggest problem with these three drafts:
they accumulate a lot of unrelated rants, and it is important to split
between issues that are really DoH-specific from more general issues.

Warren Kumari did a good job of sorting that out in
<https://mailarchive.ietf.org/arch/msg/dnsop/GaO9UDiVCeAzCKxbPt5V1D9N450>. I
quote him:

1: the protocol,
2: the deployment concerns,
3: "resolverless DNS",
4: the loss of visibility from encrypting the DNS

IMHO, this makes several side meetings. People are welcome to organize
more.