Re: [DNSOP] Alissa Cooper's No Objection on draft-ietf-dnsop-dns-capture-format-08: (with COMMENT)

Alissa Cooper <alissa@cooperw.in> Wed, 21 November 2018 15:31 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E870130F50; Wed, 21 Nov 2018 07:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level:
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ORwteORD; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iVXiOtcc
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 aInF39QeVJyn; Wed, 21 Nov 2018 07:31:11 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A2EA130E5F; Wed, 21 Nov 2018 07:31:11 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5E93322238; Wed, 21 Nov 2018 10:31:09 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 21 Nov 2018 10:31:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm1; bh=BFVHjSgIlSnGlvaZ2arHVNc LuSbIQDxhz/LV82tSTdw=; b=ORwteORDINYASf1T+R3M0C7ljw/3mMQDslBFnUZ xyMNVvJNDe72H1PbUMg27eQRD13bL/yvlXgrCTjg88Q1tI3PpOI1G1CQPJPay5h1 ZT5NYnfSrcLF3hSLuvs272QtW8q/1d/8xtXdRKAWNPCg9EnD2ovwKDC2Bx6PlIa0 jNX1of1bFOP0Ia+Us2ox0LBEk3SOsSLqfr1crjTpKvGIxil5hTrTEjpcT+h9gAd/ hXchF2zz0zRY8Na72d7o1rypuQiA4Kb5By9Dy7LjHA26M67oESk0t7S6/akgpxbk bYYS9zqqkmb3VTRlF6D8wAj131Yp4pTyW99SaWr9gePjXow==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=BFVHjS gIlSnGlvaZ2arHVNcLuSbIQDxhz/LV82tSTdw=; b=iVXiOtccGaO1+cxnVzpusV 6Ksp4zBv3SLPwAOn5YKzIwcLUKzLTDBIgJMxIF74jEpYRYUtl3rydcKAY19RJ4dw B/WhNTSP3NujAPs91H7UOsLPG/3BHoxTUfTe7FwdDM+8wEKGmnFRJGLlo5YWrLY6 jCAzrGTb+fFyKtti7fJZkr+DWAKa3eAZ3IpdsiB/QPkic57iqum53dUtcTbPdJnu r2tDgbfsoBCvspV1ntHZThjBq6M1ojXboAoE+e2nCdqU8+LIWNSdStRccCxBf/67 hxtfRZFuqKgn2CXjgflKKuhzR+8TCLdJRv0LrUL1sgTQJ67e5QhxoSY28RDCXmZA ==
X-ME-Sender: <xms:PHr1W3-BRyu33vJFCLtOcOSmrdJ1wOFPyBotpIbAmxo4-diKFkIWYA>
X-ME-Proxy: <xmx:PHr1WwYOAOwJHO9Aoqw_o7owt0b92TtKn_-qq12l4jSElb6qgPRH3g> <xmx:PHr1W2FRCX_e74Z8If2BW6vwHDyDWYXPwZgJQHIUVjL55i_uFNJGvQ> <xmx:PHr1W-9OSztT-oWxFUBnVol0AIa2YcoDKa5xa_nFm0hgZxVgH6UweQ> <xmx:PHr1W7Wh6ypP4nqUXwgahmK0Kf0htSa15jEvCW3u7h40D5GbhVhM9Q> <xmx:PHr1W6bdmKZIIn7br8U86M2cCQMbIu6_7hS6aUbBQ564ogXyByHk-g> <xmx:PXr1W43dgxGkLVnipKFMFKY9zQAuZjWIm8d-Y0Kue_n0z7yeXVebrA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.92]) by mail.messagingengine.com (Postfix) with ESMTPA id D75AFE4939; Wed, 21 Nov 2018 10:31:07 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <9C6F7367-B9DF-40BE-8B32-42BC3587AE3A@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0CEBF6D7-3BF6-4542-9E84-AE761413A4A6"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 21 Nov 2018 10:31:06 -0500
In-Reply-To: <A21FC3A4-037D-45AB-9D79-2CEB35F06BD3@sinodun.com>
Cc: Joe Abley <jabley@hopcount.ca>, IESG <iesg@ietf.org>, tjw.ietf@gmail.com, dnsop@ietf.org, dnsop-chairs@ietf.org, draft-ietf-dnsop-dns-capture-format@ietf.org
To: Sara Dickinson <sara@sinodun.com>
References: <154276310324.29833.13160462343514423529.idtracker@ietfa.amsl.com> <CAJhMdTPTJp3Xk8EjVD2juTU1yF3A__Oez52BweNp4Nu6myV5FA@mail.gmail.com> <8EB6F0B2-BE11-4408-A7F5-403161D70855@cooperw.in> <A21FC3A4-037D-45AB-9D79-2CEB35F06BD3@sinodun.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/i189vil3tV8NPl6dzdRm1JN7tgY>
Subject: Re: [DNSOP] Alissa Cooper's No Objection on draft-ietf-dnsop-dns-capture-format-08: (with COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2018 15:31:25 -0000


> On Nov 21, 2018, at 10:11 AM, Sara Dickinson <sara@sinodun.com> wrote:
> 
> 
> 
>> On 21 Nov 2018, at 10:58, Alissa Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>> wrote:
>> 
>> 
>> 
>>> On Nov 20, 2018, at 9:01 PM, Joe Abley <jabley@hopcount.ca <mailto:jabley@hopcount.ca>> wrote:
>>> 
>>> Hi Alissa!
>>> 
>>> On Nov 20, 2018, at 20:18, Alissa Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>> wrote:
>>> 
>>>> I support Benjamin's first DISCUSS point. In addition to documenting the
>>>> privacy considerations, I think it's important for this document to be crystal
>>>> clear about who is meant to be doing the data collection -- namely, the server
>>>> operator. There are some statements in the document that otherwise could be
>>>> construed to be encouraging third-party passive monitoring of DNS traffic
>>>> without explaining why, which seems like a problem:
>>> 
>>> I think it may be worth exploring why that's a problem.
>>> 
>>> I think a capture format should be oblivious to the circumstances of
>>> the capture;
>> 
>> Ok. This document is not at all oblivious, though (see Section 3). I read the document to be implicitly assuming the server operator to be doing (or at least in control of) the data collection, which is why the two statements I pointed out seemed so striking for their lack of declaring that limitation. If the document was meant to be oblivious, it shouldn’t make normative (in the dictionary definition sense) claims about what is ideal, optimal, or necessary. 
> 
> Hi Alissa, 
> 
> If we update the statements as below to clarify the context would that address your concern?
> 
> Section 1:
> OLD:
> "There has long been a need to collect DNS queries and responses on
>   authoritative and recursive name servers for monitoring and analysis.”
> 
> NEW”
> “There has long been a need for server operators to collect DNS queries and responses on
>   authoritative and recursive name servers for monitoring and analysis.”
> 
> Section 3:
> 
> OLD:
> "In an ideal world, it would be optimal to collect full packet
>   captures of all packets going in or out of a name server.”
> 
> NEW:
> “From a purely server operator perspective, collecting full packet
>  captures of all packets going in or out of a name server provides the 
>  most comprehensive picture of network activity.”

Yes, thank you.
Alissa

> 
> Sara.