IETF Logo Mail Archive

Re: [Doh] New I-D: draft-reid-doh-operator

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 10 March 2019 10:59 UTC

Return-Path: <stephane@laperouse.bortzmeyer.org>
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 948001200ED; Sun, 10 Mar 2019 03:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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 UQLf57h-6tA0; Sun, 10 Mar 2019 03:59:08 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (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 6180C124D68; Sun, 10 Mar 2019 03:59:08 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 54BE6A052E; Sun, 10 Mar 2019 11:59:06 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id 622F4EC0B0D; Sun, 10 Mar 2019 11:58:15 +0100 (CET)
Date: Sun, 10 Mar 2019 11:58:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Warren Kumari <warren@kumari.net>
Cc: Jim Reid <jim@rfc1035.com>, dnsop <dnsop@ietf.org>, DoH WG <doh@ietf.org>
Message-ID: <20190310105815.GA16820@laperouse.bortzmeyer.org>
References: <155218771419.28706.1428072426137578566.idtracker@ietfa.amsl.com> <FACB852B-4BC4-4234-A728-9068708EFB10@rfc1035.com> <CAHw9_iKc5_i+rC-oOe3RJufFe_Jm3GmTN4UbQ6VLpcqodR8d9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHw9_iKc5_i+rC-oOe3RJufFe_Jm3GmTN4UbQ6VLpcqodR8d9g@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 18.04 (bionic)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/cQ_W7929Du9KuPBTgbbliWv1ix8>
Subject: Re: [Doh] New I-D: draft-reid-doh-operator
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: Sun, 10 Mar 2019 10:59:11 -0000

On Sun, Mar 10, 2019 at 03:48:52PM +0900,
 Warren Kumari <warren@kumari.net> wrote 
 a message of 281 lines which said:

> I think it would be very valuable to not conflate DNS-over-HTTPS
> (the protocol) with the "applications might choose to use their own
> resolvers" concerns.

I fully agree.

Applications using their own resolver is Bad, IMHO, but 1) it is
unclear what the IETF can do since it is outside of the protocol field
(may be documenting our concerns?) 2) it has little to do with DoH.

> Someone (it may have been Vittorio Bertola) coined the term DNS-over-Cloud
> (DoC)

Bert Hubert <https://blog.powerdns.com/2019/02/07/the-big-dns-privacy-debate-at-fosdem/>

> 3: "resolverless DNS",

I personnaly don't agree with "resolverless DNS". There *is* a
resolver, just not the "usual" one.

> Also, I think that this topic would be better discussed in the DNSOP
> WG -

Again, I fully agree, since it is not DoH-specific.

v2.27.8 | Report a Bug | By Email | System Status