Re: [dmarc-ietf] reporting documents, Ticket #55 - Clarify legal and privacy implications of failure reports

John Levine <johnl@taugh.com> Mon, 28 December 2020 18:49 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C362E3A0CF5 for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=iecc.com header.b=FYNhju4u; dkim=pass (2048-bit key) header.d=taugh.com header.b=Tsib9WQT
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 LPAJfQsj0lFo for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:49:20 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 4FEB33A0CF4 for <dmarc@ietf.org>; Mon, 28 Dec 2020 10:49:19 -0800 (PST)
Received: (qmail 2463 invoked from network); 28 Dec 2020 18:49:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=99d.5fea28ad.k2012; bh=xcAdg5TjHBiMMr5iFVdSatsRo+83LfQIAQSHwvKXbL8=; b=FYNhju4uvZqmbaiUg9lSgWZgMQ5mhnracnSuFNA7A/QVtnVdPFXTXskMZDRk5ZjmR12MiHI/t/mrJ0SmkDWXbZWNE3Ohp6okFzJKCkQpw3LyKGp3mfKUBhLjEjxz+ZqvfoIZKoJGJo9cBUNypXYkierWmZjxyaaU8KydCgxycUYJZ3znWifLHLXBhlLdFbkLuNkAB3B/ly5U24XXHJrlst7hCBRQmp5WQDArGZfn1XJmxK0MvfxIq9owaKn/AsjTP2Ng/JJD6LJxWV4oY5mvWfpA0OhzOSCnWtQ3vyQQm5KlR+eWozrm8RXS2JppkPV4garbHSq8XBWdcJDtDauHNg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=99d.5fea28ad.k2012; bh=xcAdg5TjHBiMMr5iFVdSatsRo+83LfQIAQSHwvKXbL8=; b=Tsib9WQToebYqMfVeUaOY+YrgAz3AiogvnDIiJE5TL/KiH9qfiVV3lgKSY8i3VUn57rPktDFdH3Yaa2Rc4psnechjvV1HdjbgpWcRikwoEDfvYApaELX1vUFNJhKBwXP2QCqVAXQXC+wGtUFgH+UsxBeKx9ro5+BtucXcciIx7pTmOo6rsODrU/EIWwaBurdpJMVFDKW4W/Kb1hj3JGW6uIpqR1NXgSG0JY21grY6wgwjXCQfZqVnepLV+XxQ320laBhwfgPVxqEfiTT1q/KMx2oT0VBIa/vjgBeW4AZwojHToZSIjquHvfh/w49wGpfpxMiauuFKlOPGyVyziajog==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 Dec 2020 18:49:16 -0000
Received: by ary.qy (Postfix, from userid 501) id D190730262B7; Mon, 28 Dec 2020 13:49:15 -0500 (EST)
Date: Mon, 28 Dec 2020 13:49:15 -0500
Message-Id: <20201228184915.D190730262B7@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: seth@valimail.com
In-Reply-To: <CAOZAAfOuYft5f7JjXi57chBzJwPu1nWb_XUP5iPJPxu5gu2Zgg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/uBbBYF66F0jXZHd6wYLFumcAiaY>
Subject: Re: [dmarc-ietf] reporting documents, Ticket #55 - Clarify legal and privacy implications of failure reports
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Dec 2020 18:49:22 -0000

In article <CAOZAAfOuYft5f7JjXi57chBzJwPu1nWb_XUP5iPJPxu5gu2Zgg@mail.gmail.com> you write:
>-=-=-=-=-=-
>Aggregate reports and failure reports get used in wholly different manners,
>have fundamentally different use cases, are implemented in wildly different
>ways, and have completely different privacy and security considerations.

All true, but the actual specs overlap quite a lot. For example, where
does section 7.1 about verifying external destinations go? If the
answer is that it's copied into two documents, that is bad.

I think we've seen that for failure reporting there is nothing to
change beyond updating the privacy considerations, so leaving all the
reporting in one document is unlikely to cause schedule problems.

R's,
John