Re: [dns-privacy] Working Group Last Call for draft-ietf-dprive-bcp-op

Sara Dickinson <sara@sinodun.com> Fri, 04 October 2019 09:36 UTC

Return-Path: <sara@sinodun.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 F01B0120911; Fri, 4 Oct 2019 02:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sinodun.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 ftTyKBn3B-lB; Fri, 4 Oct 2019 02:36:43 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 8A6951208D3; Fri, 4 Oct 2019 02:36:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sinodun.com ; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=hReGHtgYovIFPDSTC1kEvXrje8cxf6v956vh0qH2hDg=; b=G5tXSBbc5Gkj1lfHx08+0UBYZo sH5GwrMd/4ciFM2XjYubIBkwOoJTpukhYWxolJDUiztDSgT9dC9EDOtKtRlLAFqREWk6uuMz6x7jA jJynr7lffBWP0DPuKFyzC9/x3TP3EWrfbdA3zB19KxrIH9IG04O3YtF3/VLEEte9WNg/2lBZwHf/A 0dMDPiEJEm8JjGjCzNcDqUXAHy13BtVvaFpzTjWEoeCn9aGdPLKt2nu3VILPBfvKNBuGaUBGAEmPi Njfa90qhNtgVVgnXL604O38PXt5io66kvDX8WGioCyrBau4bVyHb0rfSm0bWps6VgSpAoKJyXpzbf 8/5pQ9jw==;
Received: from [2a02:8010:6126:0:3c99:99c2:edb2:fa1c] (port=61246) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <sara@sinodun.com>) id 1iGK0r-0008H8-Qy; Fri, 04 Oct 2019 10:36:41 +0100
From: Sara Dickinson <sara@sinodun.com>
Message-Id: <A727E4F6-D382-42FE-869B-1281DB3A5F7F@sinodun.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D40A78B3-5E68-47AD-A953-8A0A3F7D1B8D"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 4 Oct 2019 10:36:31 +0100
In-Reply-To: <CAJm22JZ-WbmPDjoq+uf8vCzLgFcLW_Yq8yZXiUF2Lf2pbNEKDQ@mail.gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dns-privacy@ietf.org, dprive-chairs@ietf.org
To: Shivan Sahib <ssahib=40salesforce.com@dmarc.ietf.org>
References: <CADyWQ+GUivgm7ghErR4dhp4L2rB_hBK4yLMhaAQHYw1_xsmm4w@mail.gmail.com> <CAJm22JZ-WbmPDjoq+uf8vCzLgFcLW_Yq8yZXiUF2Lf2pbNEKDQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/LMdr_RxoiTPYdUB3mYkbmAKw6FE>
Subject: Re: [dns-privacy] Working Group Last Call for draft-ietf-dprive-bcp-op
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: Fri, 04 Oct 2019 09:36:56 -0000


> On 6 Sep 2019, at 06:31, Shivan Sahib <ssahib=40salesforce.com@dmarc.ietf.org>; wrote:

Hi Shivan, 

Thanks for this review.

> 
> This is a bit late, and I'd sent some comments to Sara off-list (and I wanted to actually contribute some text but haven't yet gotten the time :(), but figured would send a quick note on-list as well. 
> In general I support the publication of this draft, though I echo Stephen's comment about it needing a sample DPPPS? DROP? document. Minor comment: In Section 5.2.1, pseudonymization and access control is mentioned, but might be worth adding some text combining the two. I believe it's a fairly common technique in practice, to comply with GDPR et al, where an employee has to follow a process (either legal review or have a customer case or something) in order to obtain access to unencrypted logs.

I’ve added some extra text to that section specifically about restricting access to full logs.

> Ryan Guest's talk at PEARG at IETF 104 on log anonymization might be a good resource for additional techniques (though I think most of them are covered in Appendix B): https://datatracker.ietf..org/meeting/104/materials/slides-104-pearg-ryan-log-data-privacy-00 <https://datatracker.ietf..org/meeting/104/materials/slides-104-pearg-ryan-log-data-privacy-00>
I _think_ we have all these, even if we have used slightly different terminology for some.

Best regards

Sara.