IETF Logo Mail Archive

Re: [dns-privacy] WG Call for Adoption: draft-pauly-dprive-oblivious-doh

Jim Reid <jim@rfc1035.com> Thu, 18 March 2021 16:10 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFCD3A2E99 for <dns-privacy@ietfa.amsl.com>; Thu, 18 Mar 2021 09:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 0ZpjWINYg6d1 for <dns-privacy@ietfa.amsl.com>; Thu, 18 Mar 2021 09:10:40 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E2163A2E97 for <dns-privacy@ietf.org>; Thu, 18 Mar 2021 09:10:40 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 9E5CE2420C28; Thu, 18 Mar 2021 16:10:32 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <AF91913A-42A1-4832-8113-F576C4AA4684@apple.com>
Date: Thu, 18 Mar 2021 16:10:29 +0000
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E546D21-9B96-42DA-A488-4BC0E8E7A4AB@rfc1035.com>
References: <1a1ef163-bef8-0726-8e51-e444e8fe6091@innovationslab.net> <86e54685-ab6e-83b5-e4f6-bbd71fc6dd5a@nic.cz> <CABcZeBOgE=ABFwErsYFrjSRWFXgcJp_JncVXbwcaiDf3iFs7RA@mail.gmail.com> <AF91913A-42A1-4832-8113-F576C4AA4684@apple.com>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/swatElPW4TNqX9lELPP_XZ_-yX0>
Subject: Re: [dns-privacy] WG Call for Adoption: draft-pauly-dprive-oblivious-doh
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Mar 2021 16:10:42 -0000


> On 18 Mar 2021, at 15:42, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> wrote:
> 
> Instead, cases where clients are particularly concerned about revealing client IP and identity to very large public resolvers benefit more from this.

There’s a much easier and far quicker solution for that problem. Clients who have those concerns can (and should be able to) point their queries elsewhere.

How about an RFC that says “don't use Quad-X if you’re concerned about revealing your IP address or identity to those services”?

I’m sceptical about Oblivious DNS because the use case and problem statement isn’t compelling enough, at least to me.

v2.23.0 | Report a Bug | By Email