Re: [dns-privacy] draft-ietf-dprive-phase2-requirements: The User Perspective and Use Cases

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 24 March 2021 11:59 UTC

Return-Path: <shollenbeck@verisign.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 541813A2B91 for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 04:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.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 nDQc4zgKQNhE for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 04:59:00 -0700 (PDT)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D2F73A2B92 for <dns-privacy@ietf.org>; Wed, 24 Mar 2021 04:59:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2146; q=dns/txt; s=VRSN; t=1616587140; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=K40BsIspnSDDdJqlzf6D4gS+Ct/ZhwuzHBEBiGta5O0=; b=D0HvfKMGicQnII42aNm8kYiVm9G44BYIrRGz/PTte9ueFSH9M15+XAzo OaygemM6tc+IzcpMzkKxY9cnQuBSgtvOBjVDIL45F0erOwv1kPpJgRWwJ g6pBP9zTJ/JsVNE4dVX/rPp5R0Sb+azrWTfUljPuyEOIMFWSoomJVEU8X UaE6Ms+oRtIjSUOHB1uwWHD+Vg8o83IFd3p2UCyRjaRxSNtXEQrJYVVd7 rfF2Q+kMPpvD7Mqi/6FmE5rii2Bpi/QL8daRCLCtINI/aHGtpQGYvoM+c t7KGexFQxi/ax3sqdmBqbCOzYJRgEO8LKwRSxNHmx6tPB1evdjFnLc8c0 Q==;
IronPort-SDR: Vui0GNd0czh3k4Fyql3XaFzMOc5pRkvB3kzXHrx+uJ7mNzGpQlwvYmYLDFCcTKLkaFVvp4me5Z naMA5M6R6bK/4DTlGAdU93RmrVkWt+I7I7JZu7FBihEGY7mgfX5SOZnRE+S2SFwBliUeiGIxyM HFASy3KDnSmWf+k69mb48NMQWIvzSBlGuAnwWV2Z3XYcIMEj6S3661UVuiXSsn5LWdvgcPfLoA jFjPGAO+YZ+MMyKsa4ekQg0ZWGyhCmwyFDLc7P+Hbj17ZSt+8UfK/BlxLsFDzmU2AmZXEfAt/j OUk=
IronPort-HdrOrdr: A9a23:0rZoQ69rznkLX7tyiINuk+HGdb1zdoIgy1knxilNYDReeMCAio SKlPMUyRf7hF8qKRQdsPqHP7SNRm6Z0JZz75UYM7vKZniDhEKDKoZ+4Yz+hwD6Eyrl+eJHkY tmea5yCNr/ZGIK9vrSyg++Dtom3Z274Lml7N2ut0tFYAl2Z8hbjjtRJR2cFiRNLjVuJZ18L5 aE49oCmjzIQwV0Uu2eJl0oG9fOvMfKkpWOW299OzcC5BOVhT2lrJ7WeiL54j4kXzlCwagv/A H++mST2oyZv/620RPa3WPIhq4m++fJ8MdJB8CHl6EuRgnEtweyaIxtH52EsTwlydvA1H8Wkc LBqxplAsJr63m5RA6IiCbqsjOM7B8er1vZjX6Rmz/KvNHwTjNSMbsnuatpNj/ir3cGkP45+q RRxG6dv4dQFnr77ULAzsmNUQprmEqyqWcjluBWj2U3a/pmVINs
X-IronPort-AV: E=Sophos;i="5.81,274,1610427600"; d="scan'208";a="6061580"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 24 Mar 2021 07:58:58 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.2176.009; Wed, 24 Mar 2021 07:58:58 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "brian@innovationslab.net" <brian@innovationslab.net>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [EXTERNAL] Re: [dns-privacy] draft-ietf-dprive-phase2-requirements: The User Perspective and Use Cases
Thread-Index: AdccsGYrdqLwH3WvQl6guRcy0JfyLQDX4Q8AAAYO/KAAJkA6gAAHOY3Q
Date: Wed, 24 Mar 2021 11:58:58 +0000
Message-ID: <4a1fa7efc7654e178a0819053be0d462@verisign.com>
References: <edd165f702ad4a9c87c70fdf28057835@verisign.com> <9e10aec3-0bb3-a1ed-1bad-9da6995e9db9@innovationslab.net> <fb3e7c07c76f41c6b1ee8d002cc685d3@verisign.com> <c5860872-64f8-38b9-54fc-4fb2be0580c4@innovationslab.net>
In-Reply-To: <c5860872-64f8-38b9-54fc-4fb2be0580c4@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/5o_yT6EZ42ESdpchzfV82ME0eDI>
Subject: Re: [dns-privacy] draft-ietf-dprive-phase2-requirements: The User Perspective and Use Cases
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: Wed, 24 Mar 2021 11:59:05 -0000

> -----Original Message-----
> From: dns-privacy <dns-privacy-bounces@ietf.org> On Behalf Of Brian
> Haberman
> Sent: Wednesday, March 24, 2021 7:20 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] draft-ietf-dprive-phase2-
> requirements: The User Perspective and Use Cases
>
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
> Hi Scott,
>
> On 3/23/21 11:26 AM, Hollenbeck, Scott wrote:
>
> >> >From the pure user perspective, do they even know that their "DNS
> >> server" is an intermediary?
> >
> > [SAH] For most people, probably not.
> >
> >> What phase 2 requirement can be derived from the above?
> >
> > [SAH] There isn't one. This text appears in the Appendix, which (I believe)
> helps set the context for the requirements that appear in the sections that
> precede it without including additional requirements. If there's an intention
> to include requirements in Section 9, it might help to call it something other
> than "Appendix", to move it up higher in the document, and to think about
> where normative language is needed. My preference is to leave it where it
> is, use it to provide background information, and not include normative
> language.
>
> Sorry, I didn't word my question clearly enough. I agree that there shouldn't
> be requirements in the appendix. It does serve the purpose of providing
> context, but does not appear to have a direct link to any requirements that
> have been documented. So, my question is does this context lead to any
> specific requirement that should be captured in this document?

[SAH] I don't think it does, and that's just as important to recognize as the other perspectives that appear in the appendix that might lead to a specific requirement. Right now, the draft leaves the question about requirements derived from the user's perspective open. I'm suggesting that we modify that text and note that the user's perspective does not introduce requirements.

Scott