Re: [Doh] [Ext] Fallback to untrusted DOH servers

Tom Pusateri <pusateri@bangj.com> Mon, 23 April 2018 19:46 UTC

Return-Path: <pusateri@bangj.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 7B2DF12D7E4 for <doh@ietfa.amsl.com>; Mon, 23 Apr 2018 12:46:10 -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, HTML_MESSAGE=0.001, 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 uIsku2QUKQwZ for <doh@ietfa.amsl.com>; Mon, 23 Apr 2018 12:46:07 -0700 (PDT)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE88A126B6E for <doh@ietf.org>; Mon, 23 Apr 2018 12:46:07 -0700 (PDT)
Received: from [172.18.245.14] (pool-108-18-165-70.washdc.east.verizon.net [108.18.165.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id C659FE3F; Mon, 23 Apr 2018 15:45:18 -0400 (EDT)
From: Tom Pusateri <pusateri@bangj.com>
Message-Id: <BF72EBFC-ACFB-49BE-BE7F-5F1AA81E73B0@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2C822F5B-D6F2-43B2-A036-73E4F7388572"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 23 Apr 2018 15:45:59 -0400
In-Reply-To: <CAHbrMsBHV5z5oNJrTvmvAPO79PRSufgGSY_NFePz34xNX4R+vQ@mail.gmail.com>
Cc: Paul Hoffman <paul.hoffman@icann.org>, Mateusz Jończyk <mat.jonczyk@o2.pl>, DoH WG <doh@ietf.org>
To: Ben Schwartz <bemasc@google.com>
References: <f17cbdf0-cd88-9fa9-c83d-26e2cf13b8c1@o2.pl> <21B4DD30-46B0-4E63-833E-FDE66EF28F95@icann.org> <765e9e5a-9b8c-fa1c-85b5-da824807e609@o2.pl> <CAOdDvNrC6VGQtCYgLOoRvwCGn0kRJuchncFj4m5r_KZ-ig7=NA@mail.gmail.com> <28678acd-f67d-7f95-273f-26ed1115d3ee@o2.pl> <75B0BB57-A222-4328-A155-E5C351DEB7CC@icann.org> <3457562c-5576-18ea-a764-d485d870b5ea@o2.pl> <CAOdDvNqft5RwHcf1Ds-nzCZ=ha1weBTwbP4KzMLoHHwJQt0bVQ@mail.gmail.com> <46145a1e-99a9-405f-9f5c-4b85005feaf9@o2.pl> <BFBE3B13-15DF-45D5-8E8A-A4DC5B476357@icann.org> <CAHbrMsBHV5z5oNJrTvmvAPO79PRSufgGSY_NFePz34xNX4R+vQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/GlB-QhTOEzxXb1iljnpwmAph7wk>
Subject: Re: [Doh] [Ext] Fallback to untrusted DOH servers
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 23 Apr 2018 19:46:10 -0000

Willem Toorop and I are working on a DHCPv6 draft for discovering DNS-over-TLS, DNS-over-DTLS, DNS-over-DoH. We have been experimenting with different ISC DHCP options to make it as easy to introduce as possible.

Thanks,
Tom


> On Apr 23, 2018, at 10:42 AM, Ben Schwartz <bemasc@google.com> wrote:
> 
> Mateusz, I'm glad you're thinking about how to discover a DOH service via DHCP.  (I would recommend including DNS-over-TLS and RDNSS too.)
> 
> I don't think your goal conflicts with the existing text, so we can keep the current draft as is.  The concept of trust is complex and depends on the situation; the current text is a broad warning that we can easily adjust and refine in future drafts.
> 
> On Mon, Apr 23, 2018 at 10:11 AM, Paul Hoffman <paul.hoffman@icann.org <mailto:paul.hoffman@icann.org>> wrote:
> On Apr 23, 2018, at 5:56 AM, Mateusz Jończyk <mat.jonczyk@o2.pl <mailto:mat.jonczyk@o2.pl>> wrote:
> > 
> > What I am discussing here are modifications to DOH so that adding support for
> > discovery would be possible without modifying the future RFC.
> 
> Updating RFCs for reasons like this happens all the time in the IETF.. Given that we don't know when such an update will happen (and I still believe it will take a long time to reconcile all of the DNS resolver discovery methods), it is better to leave the wording as-is and then update it when the complete document comes out.
> 
> --Paul Hoffman
> 
> _______________________________________________
> Doh mailing list
> Doh@ietf.org <mailto:Doh@ietf.org>
> https://www.ietf.org/mailman/listinfo/doh <https://www.ietf.org/mailman/listinfo/doh>
> 
> 
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh