Re: [dmarc-ietf] ARC vs reject

Michael Thomas <mike@mtcc.com> Sun, 06 December 2020 00:42 UTC

Return-Path: <mike@fresheez.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 440263A074E for <dmarc@ietfa.amsl.com>; Sat, 5 Dec 2020 16:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc-com.20150623.gappssmtp.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 yeLR5CgX0_PE for <dmarc@ietfa.amsl.com>; Sat, 5 Dec 2020 16:42:04 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 D95F73A0644 for <dmarc@ietf.org>; Sat, 5 Dec 2020 16:42:00 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id lb18so2733682pjb.5 for <dmarc@ietf.org>; Sat, 05 Dec 2020 16:42:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=pMCXJ16nlBFokIixnbPZc/ZMrG8Y1tAnlZigLxIRNDY=; b=K/oewfmCTXhAvDAjX5yCXuo/H3lSdfcJAgm78/1ihCCwEyHWIUqwqdAPRumdy90y/F fRH+FccugfJcxuVCMSDQxeTqCLA1KmdZyrNdWsuYVaJUIGqBqLwIxyyfDcG9TjgNRY5X /gOKc8tjJ1E0Pg05bIUa1pxdgoFOgQtwHeiurQP9yTlmrJxXCCvqc393vIJWTWAKtobO 6/xxZJeinW+lseKEOff2ccPrPUpQTsMRv1mutjwRuILOTA2lQpn9WtRvcUjcRbeMcTr0 Uu1XLSYgKWGF4kcaA8WLGl3EA2ca+0EnhDajAEW2TqN4YFgQ4QZUm/qyD95vrA6oKzfj 1xOg==
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=pMCXJ16nlBFokIixnbPZc/ZMrG8Y1tAnlZigLxIRNDY=; b=j6LazKiBeKipUnGJsHZao/L8Ya0vPPbK0NTA+4FEU9pOxVfw8ndUEujgnp8ba0t96N WdkAChIvRzQjDLpx/GA5V+QGpOPHYShSoFqemRzrJB8ho08p2r0zoch+LAbYqArU/Lv2 kUBYTdtypFtnCVexYgxY2DOOP3fzr9nyi4DkyBqzGh+HYZ/oOhMdMMDrdPCGqr7E9728 O9TrO9t8YU6j4WMenRyEaSH/u5VpPBFeGppByKd29VlVBZjpurKpczjYk1saaLORihjl xyF93mrZsaf2fvFgkQLUvYfWLfBcHeu8rGWHWUnIc7Yi+GNVxQPfoI3nmnnLyOroEgh5 c8MA==
X-Gm-Message-State: AOAM531M/ye7erXzZNaq/o0kSDQztPjPw64COPAJt4WVc28BfpJ5/oTd 4eTuHLt7OdoCXXNDe3D9YXEk4DHx8W8r/g==
X-Google-Smtp-Source: ABdhPJx3CzRXUGJfEhd/RKYM6G083BidvP7ykOdY3uPDyN0pXV6fF4Vi4FZfHXwmOzi8gKEnxWnsnA==
X-Received: by 2002:a17:90b:388:: with SMTP id ga8mr774319pjb.108.1607215319632; Sat, 05 Dec 2020 16:41:59 -0800 (PST)
Received: from mike-mac.lan (107-182-42-33.volcanocom.com. [107.182.42.33]) by smtp.gmail.com with ESMTPSA id p21sm9149319pfn.87.2020.12.05.16.41.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 05 Dec 2020 16:41:58 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20201205231059.2BA23290EDCD@ary.qy> <b437a23a-7e7e-f70d-04dc-49810d002c43@mtcc.com> <b6950472-599b-d0a7-c0d1-82db099fb99b@gmail.com> <7ae42764-176d-11a8-e084-b10b6f676944@mtcc.com> <cb526017-c198-44f1-7282-986e5a810d6a@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <8142f18c-ac79-1f94-97d1-2704f0b4ceb6@mtcc.com>
Date: Sat, 5 Dec 2020 16:41:57 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <cb526017-c198-44f1-7282-986e5a810d6a@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/2b6j7FAg_PiM9HekARMUDEjf6PY>
Subject: Re: [dmarc-ietf] ARC vs reject
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: Sun, 06 Dec 2020 00:42:05 -0000

On 12/5/20 4:21 PM, Dave Crocker wrote:
> On 12/5/2020 3:37 PM, Michael Thomas wrote:
>> "You can say, no I am smarter than those guys and I REALLY REALLY 
>> mean it, but see 2) above."
>>
>> This is really not about questioning my intelligence. eye roll. If I 
>> said the same thing to you, you'd be screaming bloody murder to the 
>> chairs to try to get me banned again.
>
> Note that what you have just done is, in fact, an ad hominem and 
> arguably does violate IETF participation rules.

How can me pointing out that you would call that an ad hominem, become 
ad hominem?

This is the bizzarro world that caused me to leave the last time.

>
> Again, the response you are objecting two exactly followed the 
> linguistic form of the setup you offered.  As such, the response was 
> not directly at you, the author of the posting, but at the 
> hypothetical person you formulated.

Oh yeah, I just missed the implied royal you in the reply directed at me 
from somebody who has a long history of antagonism to me including petty 
5xx messages from direct mail to him. Whatever was I thinking in the 
Panglossian world we live in?

>
>> If the publisher of the DMARC record cannot accurately state its 
>> desires/policy, that is a deficiency in the protocol. Reject means I 
>> want you to reject it. It doesn't carve out exceptions. ARC is trying 
>> to carve out exceptions. If it wants an exception, the originating 
>> domain should have a say in whether it desires the receiving domain 
>> to carve out an exception one way or the other.
>
> The domain owner might want all sorts of unreasonable things. Having a 
> way to let the domain owner publish demands that are widely ignored 
> indicates a seriously flawed semantic model. And that is, indeed, the 
> current reality for DMARC.
>
You are fixated on what the receiver must or must not do. I never said 
anything about that. That is a strawman. I'm pointing out that ARC is 
trying to get two states out of reject where there only is one. It is 
certainly not unreasonable for my bank to say "please reject anything 
that is not by the letter of the law". I don't want somebody to figure 
out how to game all of this ARC stuff to phish me from my bank. That is 
far from unreasonable.

But you can say, no I am smarter than those banks and I REALLY REALLY 
mean it, but I don't care.

Mike