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

John R Levine <johnl@taugh.com> Thu, 24 December 2020 18:55 UTC

Return-Path: <johnl@taugh.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 8B3563A137E for <dmarc@ietfa.amsl.com>; Thu, 24 Dec 2020 10:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_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=ZbDfnRYJ; dkim=pass (2048-bit key) header.d=taugh.com header.b=JKkLe4rC
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 NpQRF7c1NHxj for <dmarc@ietfa.amsl.com>; Thu, 24 Dec 2020 10:55:11 -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 CB9503A07F0 for <dmarc@ietf.org>; Thu, 24 Dec 2020 10:55:10 -0800 (PST)
Received: (qmail 80058 invoked from network); 24 Dec 2020 18:55:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=138b8.5fe4e40c.k2012; i=johnl-iecc.com@submit.iecc.com; bh=5Wu06dzv8d9zIHwjCKbhvbtqF9W4HiFGq2wolIKlhRI=; b=ZbDfnRYJO2xgPpuIXeoExnpdxUPanRrUZhAMcnVrUc3lA2j+nUNasWrQRE25F1lDRKd1eIaMxNy0V9+6Yv0qY82EyBXcp+ydTlPVRPcCMqXyU35DZYtN0JZrnBCoXu5ySBWTQMleabgdZClLGHRSbtn7HDg6HexRLNDZAgtRlddKDt/Pv0LIZ0Qgjg9yJtOWvZNp+3UvYj2OpeK4lJIsBrofgI+q3cgdxna/MQe4a1UDzaNGT/GD0Pwz0VENvgzvY1UhSpJVrJbTICztycdw6Bhkd3hpEp+73Q1wQceNl/PyYBkhiggwEkAIH50YYZ2RNySrUBG9umEb1amNaQ9THA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=138b8.5fe4e40c.k2012; olt=johnl-iecc.com@submit.iecc.com; bh=5Wu06dzv8d9zIHwjCKbhvbtqF9W4HiFGq2wolIKlhRI=; b=JKkLe4rCH0AGvHZC6JkxtmXN97mCTWs4vC/f0dFf+pFhsk3q36Ppcif29JpffRynnSRmSPJIIzlUB97ZPDBW+H/74WItAOFCD6KOLADBUxJp8TUWRkBGFYLh9bgLOd/68gAazTLm5i2lO66fl7eegF3H7K1HzyY7TIC+7391znkN4Z3pKwrsH3uzWAOD0jUenpinjvni5e+EJEDRhDDRbqpYnpKY0Mqa/c4o/ItvPNLGb9qg4OzLkhRMO9ZwJItthOjLyhpylLW6AeSlMtZWbM0PgIpwfNtO+JoNjwuDXpsaB8kTnsoPjIuOS1f3eYwgB8etSCis76XtJPhIxRq4aQ==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 24 Dec 2020 18:55:07 -0000
Date: Thu, 24 Dec 2020 13:55:07 -0500
Message-ID: <8813331f-f5e4-faa5-c6d-11212fc25797@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Alessandro Vesely <vesely@tana.it>, Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <d4a00be5-bd61-0c05-3431-8d56b39a3550@tana.it>
References: <20201218023900.E73B82ACBB2B@ary.qy> <a323077-9b64-555b-3561-62cdc93819fd@taugh.com> <a8281e16-9417-5189-df73-79ea0a865fbd@tana.it> <c713b9ae-a364-1ae0-e79-55f61624aa3d@taugh.com> <3034face-b6fc-0ce2-fa1b-f59210bd6f5b@tana.it> <46339b38-3b24-bcb7-5e73-8a97038ed69@taugh.com> <3997c81d-3b30-0823-a752-fb1d60a44593@tana.it> <74a5c37-19a6-6f6f-a51d-6e5cca5b29e8@taugh.com> <CAJ4XoYdXWTgADpdL1eJuYGnpSY038vj-FW_x1f2rEp1JL0r2oA@mail.gmail.com> <01RTICXKLL3E0085YQ@mauve.mrochek.com> <c5f7413e-52c1-6710-16e5-63f59d2c24b9@taugh.com> <CAL0qLwYDeV9CmFg9qCCGPse00JV30WRiSC4orC-EitK=hiahgA@mail.gmail.com> <a79dd75-4d73-d1dc-d6b1-272de866b950@taugh.com> <CAL0qLwZXu3FxH7QGBS7PGbeDwfDTGmC=rbPEQidVV4eDJNHLUA@mail.gmail.com> <CAJ4XoYeK2cJb+easc=mqCi4ap1932LmbDdfxM1dFZKrdo2a2mw@mail.gmail.com> <acfe3d9e-97eb-50ee-26a2-568fdd8359dd@taugh.com> <CADyWQ+GJ62jt=dL9Gzuw_O7USNbS=86BqAzu8Rdv9sCb5OpCdw@mail.gmail.com> <d4a00be5-bd61-0c05-3431-8d56b39a3550@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BpkVs2bQeh6t4Tv6_3HxlEND2mw>
Subject: Re: [dmarc-ietf] 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: Thu, 24 Dec 2020 18:55:13 -0000

> On Thu 24/Dec/2020 03:39:03 +0100 Tim Wicinski wrote:
>> I Believe I agree with the current version, but can someone post what we 
>> think is the final text?

See below, with the two changes mentioned before and Mr Copy Edit's minor 
tightening up which I hope are not controversial.

Ale said:
> I posted it here:
> https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting

Hold it. I don't recall that we agreed to break failure reports into a 
separate document.  It makes more work and I see no agreement to change
anything beyond the security paragraph.  In particular, we have nothing to 
offer on what one might or might not redact.

R's,
Jobn

Security considerations

Failure reports provide detailed information about the failure of a
single message or a group of similar messages failing for the same
reason. They are meant to aid domain owners to detect why failures
reported in aggregate form occured. It is important to note these
reports can contain either the header or the entire content of a
failed message, which in turn may contain personally identifiable
information, which should be considered when deciding whether to
generate such reports.