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

Brian Haberman <brian@innovationslab.net> Wed, 24 March 2021 11:20 UTC

Return-Path: <brian@innovationslab.net>
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 A071A3A2AC5 for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 04:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=innovationslab-net.20150623.gappssmtp.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 q20dhCCm5-WH for <dns-privacy@ietfa.amsl.com>; Wed, 24 Mar 2021 04:20:02 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 A6DB63A2AC4 for <dns-privacy@ietf.org>; Wed, 24 Mar 2021 04:20:02 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id q3so17558613qkq.12 for <dns-privacy@ietf.org>; Wed, 24 Mar 2021 04:20:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovationslab-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=4pGFKU2v9Q/e2ZLgxfCplR/37n1R/LlaCV5eTSbEO8s=; b=oWoOOSS6LQ8EZWbirTH3vSGibgOsZ6YH3FKzjdgoDjkEtHMJBD8qXMlC6BhkVBkmza OXhHRNCfNIQxFE9Fes3huyeisSoNCQhIZ0YhgqN4puXpsT4NE8LA9P7E33VgAPZii6F2 8iAK+sMnf98b9CpDYRKrEOYClBXpqfVPzJmt5OCujMzcv2KHJs3SOZM7+jJ+wjQRjYDU /vbmnnPp/b0cXT75KCOjmokPG/n+wQhmh0C1wQxan0qkkz605FtxVJtnEkMF/WUB18si vqm9wChsD4EYvUS5p6lyRKiVM7KOrk+fQfQc5D0pry4qyqXvjiy6cqvYyMAsdAbwC+1r qW8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4pGFKU2v9Q/e2ZLgxfCplR/37n1R/LlaCV5eTSbEO8s=; b=LGyBAsdeiElqYBBM6w0Ljl0mqRPacPp/5GqswB5yDaJSth8oLTqHoIgfqzm+0wodoz XzgqmgefQQcIVMVxktk3lGlM446dPUjxL3A1cmr6I6hYHrHLx1b22wBDXNf967QtthNh v1a6dTTR8SgRDwFAzLNgJsRVlU+s7JS4/ORjGw1igG9I4fuAkh7k+/M704aklMRkTc9u lR1ecPFKSljM1JCG3kTdR+tjdeO404dgTik5QQ5x4F9NsR0zs645ijzrr96loJpa3Hpb KG5ksokUezWgRP9OlSQDu291yj78MiLalqJATbYjtVE4s5Rm6rXpgD/YK5+guCOps2hh Lyjw==
X-Gm-Message-State: AOAM533DngCon3j6JOSca2GoW6/zNsqKKjZwLjyCKyltQkzAU983nVMa nRV7A7oVQy0YSSQAzq05N9ffpptgfp7stYqN
X-Google-Smtp-Source: ABdhPJwfFtkC8lrEdNFx9xRdFsB7HbMSSIoVX6vDFOI0SCAWlzimGCNI61PyopGIv4ibfC609u2Amg==
X-Received: by 2002:a37:4553:: with SMTP id s80mr2418301qka.167.1616584800940; Wed, 24 Mar 2021 04:20:00 -0700 (PDT)
Received: from clemson.local ([2601:5ce:300:84e:2098:a680:2bea:11c]) by smtp.gmail.com with ESMTPSA id l129sm1387682qkd.76.2021.03.24.04.20.00 for <dns-privacy@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Mar 2021 04:20:00 -0700 (PDT)
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
References: <edd165f702ad4a9c87c70fdf28057835@verisign.com> <9e10aec3-0bb3-a1ed-1bad-9da6995e9db9@innovationslab.net> <fb3e7c07c76f41c6b1ee8d002cc685d3@verisign.com>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <c5860872-64f8-38b9-54fc-4fb2be0580c4@innovationslab.net>
Date: Wed, 24 Mar 2021 07:19:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <fb3e7c07c76f41c6b1ee8d002cc685d3@verisign.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/8lXqObumJwJ4AqNyaySqosWBb90>
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:20:06 -0000

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?

Regards,
Brian