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

Dave Crocker <dcrocker@gmail.com> Mon, 01 February 2021 18:19 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 1482D3A1387 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 10:19:44 -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 ljvvvzKgI-Fo for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 10:19:43 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (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 DEEE03A1386 for <dmarc@ietf.org>; Mon, 1 Feb 2021 10:19:42 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id v1so17254692ott.10 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:19:42 -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=iLeS+mcDrIyzuR6cQlzMhGkFl0D7dW4TuOuNstGmUkw=; b=c2YPvXcP1IldviwMcMuMk1n3+Ic0vqUA2z5j3H9gyTbpcS0kpl3Z4QWb0+1zoUAWCM 0VGV1fCAeM+IhGUt9vUDwTlE7uQEQcP9Rwu1y2rAS5VusD1jBNMA7zEhVyS7Au+uonm/ 5lLYBB4925qfvtPKSXDmrzlaasT3/DaYa5b/VSpqUqdoEq5UnDaDJflFNn30JOPfp9+A 4bxKvC0suQUW2v9MXwJxVQ6rA5rQXjxBRy3I3iFNKrsoxArXzhwq6WpyMmSXwLIHjdKV inDlKgxhKuzzU2wErjCbY8Mb6errncDWjOO4gwIy3dL3Vt9j5NtPLekmH8cUvj5xBcjd JNoQ==
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=iLeS+mcDrIyzuR6cQlzMhGkFl0D7dW4TuOuNstGmUkw=; b=C/OsElxk+NovFKVQqS9JgvbdYrnHDl3iGujHB/r1kEqyilr7sjbh2PbvL83r9lCPwZ 9Com2/KnoYWyw0zQb/xW3whXufLbgQXDeM5xT091xdI6OAUHQNgJH6kz5eeoAEA/G8Gz s0cKnpReuXSqV+B/OK5xTvO6E44eRwPgMQyNdo/eemxsAoolKo5BApL+Tv41QN02PNgL fpx+pk3X+FdCdKQeuu6i0vsuXj5G0AEG95Z257fPESRig5lFHKozV8RqJbme61NLqNyN 5xd6elPZuGu+4q6cHcCL8n/GhSJ+jRecidAeAK3nPlnJeFdSwVMuGcXHib7ecugeSHgj 5FQg==
X-Gm-Message-State: AOAM533m5ip9zUXeo69+iKpQ3FbuUvqPgSMVFCBi19RpCpefKinIbDnl Pnkw32YAot0pToLGODR3+4pS2DnvMrxIYQ==
X-Google-Smtp-Source: ABdhPJz62XTR2V8em4B45x8ZEPl8B9AllU3tH29CguNNTOKFdTfzZcJ21Cj9WXK5PXw6+w6oTu7l3w==
X-Received: by 2002:a05:6830:15cc:: with SMTP id j12mr12703004otr.145.1612203581976; Mon, 01 Feb 2021 10:19:41 -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 v77sm4218331oie.16.2021.02.01.10.19.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:19:41 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com> <6af16adc-eae4-9800-92cf-6a7daf6e5064@gmail.com> <413b657b-bbbf-854c-649c-f14c5f0272cd@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <ccda986e-5eab-83a2-3a7a-e629902e78bb@gmail.com>
Date: Mon, 1 Feb 2021 10:19:40 -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: <413b657b-bbbf-854c-649c-f14c5f0272cd@mtcc.com>
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/NmIoXgWe4xbXtnuLvar47e8dpfc>
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 18:19:44 -0000

On 2/1/2021 10:15 AM, Michael Thomas wrote:
>
> On 2/1/21 9:25 AM, Dave Crocker wrote:
>> So, it's probably a good thing I emphasized:
>>
>> "It should take a very, very substantial record of reporting problems 
>> to justify such a barrier."
>>
> Meanwhile in 2021, the internet is a dangerous place where the default 
> posture is to assume that if something can be gamed it will be gamed.


Perhaps you'd put that comment into both a cost/benefit tradeoff 
consideration and in technical and operational terms that reflects 
practical limits?

d/

-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

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