IETF Logo Mail Archive

Re: [Add] Comparative DoH Discovery DNS RR Types

Paul Wouters <paul@nohats.ca> Wed, 01 July 2020 01:05 UTC

Return-Path: <paul@nohats.ca>
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 DB0E23A085A for <add@ietfa.amsl.com>; Tue, 30 Jun 2020 18:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 U7tayLeEUqQz for <add@ietfa.amsl.com>; Tue, 30 Jun 2020 18:05:00 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 636B03A0859 for <add@ietf.org>; Tue, 30 Jun 2020 18:05:00 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49xNLJ4h5YzLkX; Wed, 1 Jul 2020 03:04:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1593565496; bh=nyVrdb2WZeinMXZ6uLuR6wafAgknOxET0K5fJevJYgE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=dP9gpy6QD5oMw9HxFjRvAryM05QpUO/foSC79YFFB++4Qn9YQ39xU1eRmGHV+zCrC fSFo/L51molp4zRVIULQ2FRVZEETZAs6eR/D9V/yMw7IWh1UhN8InVIWvNZPEcru2F KLyWAjqYg0erZRd/Gbz5RAR2t04POFjyeNDACiSQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id hiB6AAtOAYOx; Wed, 1 Jul 2020 03:04:55 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 1 Jul 2020 03:04:55 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id B9CFE6020EE7; Tue, 30 Jun 2020 01:09:21 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id B16E666ADE; Tue, 30 Jun 2020 01:09:21 -0400 (EDT)
Date: Tue, 30 Jun 2020 01:09:21 -0400
From: Paul Wouters <paul@nohats.ca>
To: Martin Thomson <mt@lowentropy.net>
cc: add@ietf.org
In-Reply-To: <10fa5a67-1894-4bc5-9090-4d4f5aeb2242@www.fastmail.com>
Message-ID: <alpine.LRH.2.23.451.2006300105350.141755@bofh.nohats.ca>
References: <7325C546-587D-4CD9-8059-0887C33F3503@cable.comcast.com> <26559974.PdTMpzyJZD@linux-9daj> <18350.1593475069@localhost> <516fcd85-2d67-e853-03b5-49220df9d878@huitema.net> <10fa5a67-1894-4bc5-9090-4d4f5aeb2242@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/SAYQUjXoyeDfRdwh_-55DrJakb8>
Subject: Re: [Add] Comparative DoH Discovery DNS RR Types
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, 01 Jul 2020 01:05:02 -0000

On Tue, 30 Jun 2020, Martin Thomson wrote:

> I'm not super close to this, but my understanding is that we now have two resolution paths: one native and one for DoH.

That would be unfortunate if true. Making the resolving code and results
different based on the _transport_ of the same DNS data is asking for a
lot of complicated bug reports and confused users.

Imagine needing to tell your users for some websites you need to enable
DoH and for some websites you need to disable DoH.....

Paul

v2.23.0 | Report a Bug | By Email