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

Dave Crocker <dcrocker@gmail.com> Mon, 01 February 2021 23:23 UTC

Return-Path: <dcrocker@gmail.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 D5C6C3A1588 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 15:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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=gmail.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 fNHU0BwlzUnn for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 15:23:39 -0800 (PST)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32183A1587 for <dmarc@ietf.org>; Mon, 1 Feb 2021 15:23:38 -0800 (PST)
Received: by mail-oi1-x230.google.com with SMTP id m13so20757266oig.8 for <dmarc@ietf.org>; Mon, 01 Feb 2021 15:23:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=HeaPL2jUggnNDB+mrLlJyl0OeT2AJ9GBsa34ZNCd3t8=; b=rgAlTQAAvkD7QmFuz/fzlpCP7hiViBGkzhGt4xQOxC1lMS0zGnPx8PNXP7iS2G+Vv1 N1fAdQq1B9fl9BY9qjteeN1f0u+VSRiQ7VsjG0XUqTFQKKATfw5jQUtQAVqixeqJdU9Z Ad+ujLgKl06FqoVfpc5AFV7LjUwkHjKaOdpd/4EFyhTlBXna60dCLUOdxqVkdU/U5YQK LQLWq3HiNJ9mEB/nKC7/HgvNuwDl/9iLVnWVVKjM2nDFwOmXqicDdWIRBBtABwVzzyLL njOe2Pih6GOcQ8UULjGHdsP+N5bMTtCklGzA2mp4OK3Iycqyhr7FbH23ajdFWMHoZdeo pTVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HeaPL2jUggnNDB+mrLlJyl0OeT2AJ9GBsa34ZNCd3t8=; b=pM3n2aR5+j5/bRym/dC8cISu7Ul5xf2NBNdqfVuWbPZ6UUAklyUBYU/z+YVP0niQub tmqFFP0sK2ehJUZC5484d2lTkDTaUDv1Yj6utR47wdLENy3OzUCPLEBMrxAv4ck5e6Nb 8FC1sXUMzoPdvs779rC5Ie7SrF8UsCR9S2EuIdqCCJ+v3QS6I5C4SWO8s6gQy7fDkIdz 86U24aQ/6+fA7l+eEyZJ+gEr65v3wkMm+9Yi+XeCtsFde4tFTqUKZPW7ZC8liksWLqKn F7m/pcTxd9PUv69bLyCDKhHJDWCuEViQlcVxdIjx+iGaielwT805Zl5+0Kr39e9nl1fp yvLw==
X-Gm-Message-State: AOAM53110MJGuU5rEQ768RbEpgldfC7+fgmIfENsbrotxoqjg/13kPYg VnXHyN3QJWhxk2whpQXWCe6tHItUkxvCrw==
X-Google-Smtp-Source: ABdhPJwkLc7vxUKWyLI4bDbtS5hiVZxh9ORFgBKTpmLUtihwKTXZVvzyC+Z+xkmhmLd1CYjm7YyhWg==
X-Received: by 2002:a05:6808:4d7:: with SMTP id a23mr864558oie.38.1612221818069; Mon, 01 Feb 2021 15:23:38 -0800 (PST)
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id e20sm4256427otr.14.2021.02.01.15.23.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 15:23:37 -0800 (PST)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
Date: Mon, 1 Feb 2021 15:23:35 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <20210201232105.1931D6D20971@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/y9G4gybiAZqohvkx_o_JYZnpxgk>
Subject: Re: [dmarc-ietf] Forensic report loops are 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: Mon, 01 Feb 2021 23:23:42 -0000

On 2/1/2021 3:21 PM, John Levine wrote:
> I find it hard to believe that if you are going to enough effort to
> maintain the data to create and send reports, you can't figure out how
> to install an SPF record for your reporting domain.

Except that the tracking/reporting functions are completely separate 
from the 'signing' side of DMARC and could easily be different parts of 
a company.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org