Re: [dmarc-ietf] Forensic report loops are not a problem

John R Levine <johnl@taugh.com> Sat, 16 January 2021 22:20 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 7ED143A19F4 for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 14:20:27 -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=cAGi1Ejb; dkim=pass (2048-bit key) header.d=taugh.com header.b=jXGcgGb3
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 fIYtH_VCTMkF for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 14:20:25 -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 66C413A19F3 for <dmarc@ietf.org>; Sat, 16 Jan 2021 14:20:24 -0800 (PST)
Received: (qmail 70202 invoked from network); 16 Jan 2021 22:20:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=11238.600366a4.k2101; bh=Zgcbv9j8/xHDavVrCaz6xQFwicBvB5KYFbcYLXbRfOE=; b=cAGi1EjbETPwGkwl0anO17E3cu0P/Cs7vzGRZZTCjO47h8ttOItgL4vs0PluaoToIfNPS0vdfixPcUCHB9p+ZsS8ki8WIgtb0Quwzv5QPhsRzVLic3/spjnT6CeXJXw/J8HARyYiXMT7uz2m/VVYK9A6mc1t9Kq0s16YkWgM5ce+4cf9bf2KTNFRSGhV70Cm8F9r5BikoWLAS3501LGJIXxopKu9JfkuEn2w4PXIaKMy0+KWOI7sNN0eAQLvAaHVAiTzi5f73+eArmji8u9BMk50lk7SKK49NVRJM+eZvxzkGLOMrEDUAra+GrntZzn3qmKsIcENKnZf1l3ZKdRlAA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=11238.600366a4.k2101; bh=Zgcbv9j8/xHDavVrCaz6xQFwicBvB5KYFbcYLXbRfOE=; b=jXGcgGb3J07hfiDF20w1YIukGzPgQZfdAhUuHNxQRsF2YxjvIUn3cuGnqGSJmN2ctVCqqwtKW4NxtH0wvEXzooeGeHjsfL+N3aIQUixYSlb30SD6kWSYL0eJtwkFqjnX9/bnxno4Xt/8iMSfYOJmyhdQvmaAqKchRewHwFk9aiN09vM2T55ocR3n54d2AhOyWkP3xWIZZJnSD5H02QayK2Sg7r2r+Z3ffYbGTGlfMW8CVtY+zZVseD6DZhjXNvZ67KFvNY9Mn29Tsm+JphXFNZUbiY3AYKenPXeooZI8fhlolHufG+iVilPK5+s83i5HZnIwLmJORYkKiNuTfWiNXg==
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; 16 Jan 2021 22:20:19 -0000
Received: by ary.qy (Postfix, from userid 501) id 7B1F46AEDD4B; Sat, 16 Jan 2021 17:20:19 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 7020C6AEDD4A; Sat, 16 Jan 2021 17:20:19 -0500 (EST)
Date: Sat, 16 Jan 2021 17:20:19 -0500
Message-ID: <3d6db975-4d52-94f0-5ca0-213234d53773@taugh.com>
From: John R Levine <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lrd9Z2jdoVT-lJODDWM8z6jXQ3w>
Subject: Re: [dmarc-ietf] Forensic report loops are not a problem
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: Sat, 16 Jan 2021 22:20:28 -0000

> What I'm concerned about is that since this has come up before N times
> (for, admittedly, some currently small value of N), we've seen enough
> disparate cases of it that we may be missing something bigger, and if so,
> doing something defensive in the specification would be prudent.  There's
> smoke here, and there may be fire.

OK, thanks.

My guess is that if we can track it down it is likely to be "my software 
is buggy so I want everyone else to work around it."

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly