Re: [Add] Mozilla's DoH resolver policy

"Ralf Weber" <dns@fl1ger.de> Thu, 11 April 2019 14:52 UTC

Return-Path: <dns@fl1ger.de>
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 43F85120372 for <add@ietfa.amsl.com>; Thu, 11 Apr 2019 07:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 JZOMCd23vPkj for <add@ietfa.amsl.com>; Thu, 11 Apr 2019 07:52:41 -0700 (PDT)
Received: from smtp.guxx.net (smtp.guxx.net [IPv6:2a01:4f8:a0:322c::25:42]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8881202ED for <add@ietf.org>; Thu, 11 Apr 2019 07:52:41 -0700 (PDT)
Received: by nyx.guxx.net (Postfix, from userid 107) id 44B505F40BE1; Thu, 11 Apr 2019 16:52:40 +0200 (CEST)
Received: from [172.19.152.251] (p4FF53610.dip0.t-ipconnect.de [79.245.54.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id 128E95F40499; Thu, 11 Apr 2019 16:52:39 +0200 (CEST)
From: Ralf Weber <dns@fl1ger.de>
To: Daniel Stenberg <daniel@haxx.se>
Cc: add@ietf.org, Martin Thomson <mt@lowentropy.net>, Valentin Gosu <valentin.gosu@gmail.com>
Date: Thu, 11 Apr 2019 16:52:38 +0200
X-Mailer: MailMate (1.12.4r5594)
Message-ID: <792D4346-DE43-4BFC-85D4-FC58366E38B5@fl1ger.de>
In-Reply-To: <alpine.DEB.2.20.1904111144200.31156@tvnag.unkk.fr>
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> <CACQYfiJa1i2LVgQDcHi_OknmDDKZiaw=++Y6imn34LcPULP3bQ@mail.gmail.com> <E0CA1520-74D4-4A41-9B44-10946FAB4534@fl1ger.de> <CACQYfiKeh=FgmB9RN=eJ-2tq4jyTg55fep4au9SeGe3U5VkMBQ@mail.gmail.com> <ED802588-CD5D-4F80-914D-CA25EE234424@fl1ger.de> <alpine.DEB.2.20.1904111144200.31156@tvnag.unkk.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/QP7tsei68hmLIEpDjovEX-_1F8g>
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: Thu, 11 Apr 2019 14:52:43 -0000

Moin!

On 11 Apr 2019, at 11:49, Daniel Stenberg wrote:

> On Thu, 11 Apr 2019, Ralf Weber wrote:
>
>>> To prevent disruptions to the user's browsing.
>> Again why do you think it will get better asking unencrypted? It is a 
>> nice
>> way to find out if someone is using DoH though ;-).
>
> How about not discussing application specific design decisions?
Isn’t that the topic of the mailing list (Applications Doing DNS)?

> I don't think anyone suggests it is better to ask unencryped, but when 
> the DoH server you have configured slowly dies or get DoS'ed or 
> whatever, users will appreciate a "way out". In this specific 
> application being discussed, it has a soft-fail mode that works like 
> this.
Yes and me being a user of that application (though not that function) 
thinks that this is bad. I found it odd that most DoH configurations 
I’ve seen by now are singular in what they give as a target, while 
most OS libraries allow multiple DNS server addresses and fail between 
them. Why are you not doing that with DoH?

The first time I saw more than one DoH server used for configuration was 
in draft-ietf-doh-resolver-associated-doh  ( 
https://datatracker.ietf.org/doc/draft-ietf-doh-resolver-associated-doh/ 
) and I think that this is good.

So long
-Ralf
—--
Ralf Weber