Re: [Doh] Suggestion: The final endpoint should be able to temporarly act as a recursive DoH resolver

Dave Lawrence <tale@dd.org> Thu, 25 October 2018 19:42 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <23506.7319.938389.445190@gro.dd.org>
Date: Thu, 25 Oct 2018 15:42:15 -0400
From: Dave Lawrence <tale@dd.org>
Cc: doh@ietf.org
In-Reply-To: <001801d46b7d$3de32f50$b9a98df0$@sebbe.eu>
References: <001801d46b7d$3de32f50$b9a98df0$@sebbe.eu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/QEK4uBbqK_PktBJoTnQdoztLg2I>
Subject: Re: [Doh] Suggestion: The final endpoint should be able to temporarly act as a recursive DoH resolver
Precedence: list

Sebastian Nielsen writes:
> This could mean that once you reach a WWW server, theres no need for
> looking up domains like static.example.org and such since the result
> of such domains could be returned by the original HTTPS server over
> the same connection as the website traffic goes over.

Do note that even if you're talking to www.example.org,
static.example.org can be in a different authoritative domain.  It
shouldn't be exempted from DNSSEC.

[Doh] Suggestion: The final endpoint should be ab… Sebastian Nielsen
Re: [Doh] Suggestion: The final endpoint should b… Ulrich Wisser
Re: [Doh] Suggestion: The final endpoint should b… Sebastian Nielsen
Re: [Doh] Suggestion: The final endpoint should b… Ben Schwartz
Re: [Doh] Suggestion: The final endpoint should b… Dave Lawrence