Re: [dns-privacy] Review of draft-ietf-dprive-rfc7626-bis-03

Rob Sayre <sayrer@gmail.com> Thu, 09 January 2020 04:29 UTC

Return-Path: <sayrer@gmail.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 D8510120108; Wed, 8 Jan 2020 20:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 n8TdhVBhwdFK; Wed, 8 Jan 2020 20:29:00 -0800 (PST)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 97FCA120020; Wed, 8 Jan 2020 20:29:00 -0800 (PST)
Received: by mail-il1-x12d.google.com with SMTP id s15so4632387iln.1; Wed, 08 Jan 2020 20:29:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TL7tq1lL1csvhbRVy3OYxTo2cl8a7lYHrrA45CnlGPg=; b=gniqvYPvCgrRJmJSXDXT5tzG8xg+1QkYcnYZIUU9zdZNjf/QCafDUe9RkuAEgRtznc tj0IPuDLNY9jGefOnYks+G2sVYYxZWNjdT8SCn/nLtaNXa5Qyn8RE/M1IvQP5rrSS5E+ EJJEHqp8W88bkYuYbfJp/OdNripnamuoTzSsUL6QpPCeTEdjoY/gBH+B/sBQMuT8ecAU 5z4bNYV56s0GVk292URuCK0hv+lW7ySko/nsGwphU//Vl4cSUcIfrcmtPB+OGKe1LxUa DeP9z8hTUgQd2FKYLv6FLEAc30n2Vwp3nulq763Xocx+7Z3en1yH0Nh6dV7mPlIPLYcQ cpSQ==
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=TL7tq1lL1csvhbRVy3OYxTo2cl8a7lYHrrA45CnlGPg=; b=HfORX5hKDh/MYMT2m8afqPVyEbdFEx3IfGmNnFK0RiR4cPHCJrlF85rOqYuXhNZim9 mS0JPpr6McGU1ITfymHEZmKs5wRaGLLcQ/7D8vNvVqOdc4rIEpinBaPy8kzim6ha7fCY HazIC57ltq00aOUCJdc2H5cWGRvOLvOZKBE/+O3cyjygwBA63bVnjmk6p0UbVKQ0tX1w i+EdZ10gKS8hRLX8WpcLfX6Qq60lbMpEmysjnVN4lkTE9by3i75wk9mqnIDFPbqa+NY7 vEoWH2wXzx81xG70iSAfEsAJAW82Ia+K4enx1l+uBXZrcXp8Mj9JjAjwjer4I8XsoCny S06Q==
X-Gm-Message-State: APjAAAVWl0w7EB3RZ2e6AcG5ggSPfUZ4VGuVocvOYqSxO60/nYQz5LeR NdKL+d5F3TuTxMIQiPnjeixyHFwXrICtVt2Fars=
X-Google-Smtp-Source: APXvYqzJoLPUIOGqbxWkiw1SzQJrqQeZGJcJBXyENnL++afotnYY32MYrOwwpuywgmNbvKQNlXwTejOEeqrHwl4UDq0=
X-Received: by 2002:a92:498d:: with SMTP id k13mr6997050ilg.254.1578544139862; Wed, 08 Jan 2020 20:28:59 -0800 (PST)
MIME-Version: 1.0
References: <4639bd67-6fca-47d1-aaeb-85fcd0394f46@www.fastmail.com> <029D8BB9-CE93-486A-BDF2-6D0720E59109@sinodun.com> <18c8c298-e462-490b-b3a3-5d5904d98c25@www.fastmail.com> <18F59166-83B9-4402-8703-B90589B540F5@sinodun.com> <01b7df16-7917-4251-8daa-550262ce5461@www.fastmail.com> <CAChr6SwpPnBo0uf5+XJw7c998TgjDyQMdoD6g0OKwOBD9+JQ3Q@mail.gmail.com> <CABcZeBON_ADPXvim_Q6TUSqp-12ii2Gm3y55Oc0CGhqSQqc_kQ@mail.gmail.com> <cca5f51f-a1de-4a29-a048-3dd9aea326fc@www.fastmail.com>
In-Reply-To: <cca5f51f-a1de-4a29-a048-3dd9aea326fc@www.fastmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 08 Jan 2020 20:28:48 -0800
Message-ID: <CAChr6SzmZF+iM0Wue2x827q1doehhHAc_8njetyLJwWYJpmhLw@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: Eric Rescorla <ekr@rtfm.com>, last-call@ietf.org, DNS Privacy Working Group <dns-privacy@ietf.org>, Sara Dickinson <sara@sinodun.com>
Content-Type: multipart/alternative; boundary="000000000000b8074a059bad7251"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/q-4dLau3GuDVnMnPRuQxnZikBwk>
Subject: Re: [dns-privacy] Review of draft-ietf-dprive-rfc7626-bis-03
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, 09 Jan 2020 04:29:02 -0000

On Wed, Jan 8, 2020 at 6:06 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Jan 8, 2020, at 23:51, Eric Rescorla wrote:
> > On Tue, Jan 7, 2020 at 8:28 PM Rob Sayre <sayrer@gmail.com> wrote:
> > > Couldn't servers give out unique URI templates?
> >
> > DoH doesn't specify how the clients get the templates. At least for a
> > Firefox-style TRR program, what you describe can't happen because there
> > is a single fixed template.
>
> It is true that the potential for providing individualized endpoints for
> tracking purposes is an exposure.
>
...

> In the new work we are likely to undertake, this is something we'll have
> to consider, but I don't see it as a huge issue

...

> That is, in the context of pre-existing DNS discovery, I don't believe
> that this creates a new exposure to this style of attack.
>

I generally agree with this. I do think this concern is relevant in
discovered URI templates, and in assessing the value of TLS and Web PKI as
signals of trust.

thanks,
Rob