IETF Logo Mail Archive

Re: [Add] Mozilla's DoH resolver policy

Vittorio Bertola <vittorio.bertola@open-xchange.com> Sat, 13 April 2019 08:19 UTC

Return-Path: <vittorio.bertola@open-xchange.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 1CF711200C4 for <add@ietfa.amsl.com>; Sat, 13 Apr 2019 01:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 V6k5c_oMunWJ for <add@ietfa.amsl.com>; Sat, 13 Apr 2019 01:19:18 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 76390120092 for <add@ietf.org>; Sat, 13 Apr 2019 01:19:18 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 759D86A264; Sat, 13 Apr 2019 10:19:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1555143556; bh=E3IKoYjOdOi8LZpz5T5G/qwPitgRtB6995QyGKRFxtk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=05DKDj8UBN5grvw2zKYL80hMpj1IJ0lKba0dDOGhkyP8TpiRY67FiTiYWvSCZ7huq lcOUm4v5fXew7in1G9uh/ZFUSD5Gf9YQ5ublmoM7Ri//RLYwQg0OOUOo3JPua5U8E1 za+HLniPAW3lOf1woC3KtHuMXJL38VAIZoqi5VznNqlKiov2PYxS6RFY0hLrKifBYn D4RfrfIM58g1JCfR6M/o0tOChq5haHmf2vLRg2u5QFw3SaVqN5pNr47orDHe1dIQHI kOCZt9hBMcwma4eiuR6JArp/sLGeWSJU/O0HPsa1hu5e3HI+FXJDaJTljWAWPzQA8f N1DAPYul3MSKQ==
Received: from appsuite-gw2.open-xchange.com (appsuite-gw2.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 692AF3C036E; Sat, 13 Apr 2019 10:19:16 +0200 (CEST)
Date: Sat, 13 Apr 2019 10:19:15 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: add@ietf.org
Message-ID: <1888048494.23821.1555143556369@appsuite.open-xchange.com>
In-Reply-To: <yblr2a651zv.fsf@w7.hardakers.net>
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> <CA+9kkMAobw2giYO=8pbLVi4ms0Ru+nYwhV5DGxLCwaUdX6EQyQ@mail.gmail.com> <yblv9zj5591.fsf@w7.hardakers.net> <CA+9kkMBMehkz3NbytL+vfDh+SwhW9At_q7oBL8a7XSEiSSrNwA@mail.gmail.com> <yblr2a651zv.fsf@w7.hardakers.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.1-Rev10
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/X2b6UXEcuxBsymqmdFHtXx_AqqY>
Subject: Re: [Add] Mozilla's DoH resolver policy
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: Sat, 13 Apr 2019 08:19:20 -0000

> Il 12 aprile 2019 alle 23.48 Wes Hardaker <wjhns1@hardakers.net> ha scritto:
> 
> Like most "triangle-like" choices, there is likely no perfect balance of
> metrics you could pick from and each of us would likely pick different
> solution points.
> 
> The three big ones that are coming back time and time again are:
> 
> 1. latency
> 2. privacy
> 3. authenticity
> 
> Right now, most web-browsers (as you point out) are optimizing for (have
> always been in a race for) latency.  

The policy problem of optimizing only for latency is that in many cases an operator can lower the latency of their service almost at will by throwing more money at it, so if someone has a lot more money to throw than the others and is determined to use it, any algorithm only focusing on latency will always pick their service and you will get full centralization, which is deadly for privacy.

Ciao,
-- 

Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com
Office @ Via Treviso 12, 10144 Torino, Italy

v2.23.0 | Report a Bug | By Email