IETF Logo Mail Archive

Re: [Doh] [Ext] panel discussion on DoH/DoC

Ask Bjørn Hansen <ask@develooper.com> Thu, 07 February 2019 16:26 UTC

Return-Path: <ask@develooper.com>
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 CE9571271FF for <doh@ietfa.amsl.com>; Thu, 7 Feb 2019 08:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 fqpfv9oTb9g8 for <doh@ietfa.amsl.com>; Thu, 7 Feb 2019 08:26:23 -0800 (PST)
Received: from mbox1.develooper.com (mbox1.develooper.com [207.171.7.178]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D933B1289FA for <doh@ietf.org>; Thu, 7 Feb 2019 08:26:23 -0800 (PST)
Received: from mbox1.develooper.com (mbox1.develooper.com [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mbox1.develooper.com (Postfix) with ESMTPS id 73FD81760F3 for <doh@ietf.org>; Thu, 7 Feb 2019 08:26:23 -0800 (PST)
Received: (qmail 31079 invoked from network); 7 Feb 2019 16:26:23 -0000
Received: from c-98-248-50-174.hsd1.ca.comcast.net (HELO ?10.0.200.101?) (ask@mail.dev@98.248.50.174) by smtp.develooper.com with ESMTPA; 7 Feb 2019 16:26:23 -0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Ask Bjørn Hansen <ask@develooper.com>
In-Reply-To: <7A2202F4-FAE9-4282-BC0B-8229A9A6E016@icann.org>
Date: Thu, 07 Feb 2019 08:26:10 -0800
Cc: Ted Lemon <mellon@fugue.com>, DoH WG <doh@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0EC7D06-0EF1-4568-91CD-F311D8E1F0F0@develooper.com>
References: <20190207105106.GB1772@server.ds9a.nl> <C7C3BAF7-4BD4-4EE2-B3F2-1F8B49222980@fugue.com> <20190207130313.7g7hf4swaopnr75e@nic.fr> <FD7BFAFF-88B9-49BF-A652-3649ADCD53F9@fugue.com> <7A2202F4-FAE9-4282-BC0B-8229A9A6E016@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/ohLRboS7T10m7cLFbmydWAMWX_k>
Subject: Re: [Doh] [Ext] panel discussion on DoH/DoC
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: Thu, 07 Feb 2019 16:26:25 -0000


> On Feb 7, 2019, at 7:36, Paul Hoffman <paul.hoffman@icann.org> wrote:
> 
> You are probably misattributing, or misremembering, this discussion. It certainly wasn't me, and I'd be quite surprised if it was Patrick. Both of us were motivated to bypass network censorship. We *also* had a secondary use case, which was real DNS resolution by JavaScript applications (not "clients").

Another use case is to allow DNS server implementors to build on the significant investments being done in HTTP/QUIC/etc software and infrastructure.


Ask

v2.20.3 | Report a Bug | By Email