Re: [Doh] [Ext] Re: Associating a DoH server with a resolver
Erik Nygren <erik+ietf@nygren.org> Sat, 23 March 2019 21:41 UTC
Return-Path: <nygren@gmail.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 8B8E212AF7A
for <doh@ietfa.amsl.com>; Sat, 23 Mar 2019 14:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25,
FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001]
autolearn=no 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 rzTpGdoqloJ2 for <doh@ietfa.amsl.com>;
Sat, 23 Mar 2019 14:41:33 -0700 (PDT)
Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com
[209.85.128.43])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id C819E128B36
for <doh@ietf.org>; Sat, 23 Mar 2019 14:41:32 -0700 (PDT)
Received: by mail-wm1-f43.google.com with SMTP id t124so5317171wma.4
for <doh@ietf.org>; Sat, 23 Mar 2019 14:41:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=m2isSoq6n6ZCdyV4vVvebZrBRH0i5RFhJl3QpHS+M3A=;
b=ip4WDqUmGW0FxvYkONmAgMMn71gFjW924LQfgAgrCdI33/L1VB2IjdQNUuQy2ozZ5m
ISFHDhbFLC7bptTueUz3DvMsGQM0j0bi8JMzOsNOlvXuUMfnPLFJhCCJ+Yqj6IocAuDT
owYHDfxn6j4zqEvRhPRuKWFFHUDa056fyU+gPczjP33a8bDJUWe58udDTqoY5Xj6jYMX
9+n1FnOJBYigWPTJfFrDLQTe0cDLL5z4QIni3DGhHsvJOOAOBm9j2G4L06UI0m0iTFMn
JnR9PLKVYeIHhrNh2LRijOtg3MJX73jaRD91+dxHiEd2q8py2S9e23hyKhh5v9N87mEX
jI+g==
X-Gm-Message-State: APjAAAX3H49BHitaf/oPHHXVFZxKas7rl1Hi134P/4GameEFXVCEVJyA
/04wWJWqDfUOHFr8d8CYvKe34GVB277KPrd9Ta8=
X-Google-Smtp-Source: APXvYqyEVjLajI1yZIr6lSkll3gmn+0AOlz9/zjVWxEHs6IxVIqBgkG8QiSe9EOBv+mk+Lr3eOFSQcIg4CW8sDD03Ww=
X-Received: by 2002:a1c:eb14:: with SMTP id j20mr1002885wmh.32.1553377291168;
Sat, 23 Mar 2019 14:41:31 -0700 (PDT)
MIME-Version: 1.0
References: <02C39DFD-9550-447D-B00E-702B441A88BE@icann.org>
<CABkgnnV2YMtcdOyMfE2NMH4L1ZbK4dcp1KQt3FttCfz-nfQd6A@mail.gmail.com>
<C82FBB08-8DAA-4C50-8934-576596C2532F@icann.org>
<CABkgnnVgZBp7bqv9u9iBbZAojQqbYAGWG54Ta5JKq_ycvaux1g@mail.gmail.com>
<CABcZeBNObxKQWkhD=jz8Z7CL7iVnEE-O_QF5DkADu=s1=ux_rQ@mail.gmail.com>
<2695a0e8-8373-8d33-7951-cfc5555ed254@nostrum.com>
In-Reply-To: <2695a0e8-8373-8d33-7951-cfc5555ed254@nostrum.com>
From: Erik Nygren <erik+ietf@nygren.org>
Date: Sat, 23 Mar 2019 17:41:19 -0400
Message-ID: <CAKC-DJjuv8fVXkEnUHwxoBx4SRLGbhfR-ZxTJGciuKeN6qUgpA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Martin Thomson <martin.thomson@gmail.com>,
Paul Hoffman <paul.hoffman@icann.org>, DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a471960584c9d51f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/P4N26AGMPf-IqZo36PYEnQI0ETA>
Subject: Re: [Doh] [Ext] Re: Associating a DoH server with a resolver
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: Sat, 23 Mar 2019 21:41:35 -0000
On Tue, Oct 23, 2018 at 11:40 PM Adam Roach <adam@nostrum.com> wrote: > > So, e.g., interested clients would query for a URI record of type > _doh._tcp.resolvers.arpa, and get back a full HTTPS URL as a response. > Reviving this suggestion after reading some recent threads, this approach (query your local OS-configured resolver for a URI record with a well-known name) seems like a reasonably cleanish way to opportunitistically get a DoH server URI associated with the currently configured resolver. It's arguably less of a hack than cramming things into a TXT record on a reverse DNS IP. (Martin asked on a more recent thread something along the lines of "why don't we just do a .well-known lookup against the network-configured resolver, and something like this seemed like the best equivalent.) For better or worse it would also work when a caching forwarding resolver is present in passing through the record from whatever the caching forwarding resolver (eg, dnsmasq in a home gateway) was pointing to. It also has the benefit that clients don't need to know the IP address of their resolver, they just need to be able to do a URI record lookup against a well-known name. Especially of the OS helps mediate DoH server selection (which would be beneficial long-term regardless) the exact OS APIs that exist today are somewhat less interesting. Erik (Purely for enterrainment value: this well-known name could be in some other class like CHAOS rather than IN, like some other recursive-resolver-synthesized names like "version.bind txt chaos". This is not meant to be a serious suggestion.)
- [Doh] Associating a DoH server with a resolver Paul Hoffman
- Re: [Doh] Associating a DoH server with a resolver Hewitt, Rory
- Re: [Doh] Associating a DoH server with a resolver Ben Schwartz
- Re: [Doh] Associating a DoH server with a resolver Martin Thomson
- Re: [Doh] Associating a DoH server with a resolver Martin Thomson
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Associating a DoH server with a r… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Martin Thomson
- Re: [Doh] [Ext] Re: Associating a DoH server with… Eric Rescorla
- Re: [Doh] [Ext] Re: Associating a DoH server with… Adam Roach
- Re: [Doh] [Ext] Associating a DoH server with a r… Tony Finch
- Re: [Doh] [Ext] Re: Associating a DoH server with… Patrick McManus
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Adam Roach
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Eric Rescorla
- Re: [Doh] [Ext] Re: Associating a DoH server with… Paul Hoffman
- Re: [Doh] [Ext] Re: Associating a DoH server with… Christopher Wood
- Re: [Doh] [Ext] Associating a DoH server with a r… Jim Reid
- Re: [Doh] [Ext] Associating a DoH server with a r… Tony Finch
- Re: [Doh] [Ext] Associating a DoH server with a r… Paul Hoffman
- Re: [Doh] [Ext] Associating a DoH server with a r… Adam Roach
- Re: [Doh] [Ext] Re: Associating a DoH server with… Eliot Lear
- Re: [Doh] Associating a DoH server with a resolver Kenji Baheux
- Re: [Doh] Associating a DoH server with a resolver Todd Hubers
- Re: [Doh] Associating a DoH server with a resolver Ted Lemon
- Re: [Doh] [Ext] Re: Associating a DoH server with… Erik Nygren
- Re: [Doh] [Ext] Re: Associating a DoH server with… Ben Schwartz