Re: [dmarc-ietf] auth-res vs. dmarc

Michael Thomas <mike@mtcc.com> Wed, 30 December 2020 16:38 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 EAC863A0AB4 for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 08:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.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 sW5M_fSANd2P for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 08:38:55 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 9B44C3A0AA0 for <dmarc@ietf.org>; Wed, 30 Dec 2020 08:38:55 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id v19so11607991pgj.12 for <dmarc@ietf.org>; Wed, 30 Dec 2020 08:38:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=ifIZAzNVT2B/i9XTJQsPRk+PU/9ItfXMKgm1r/uxjLc=; b=horA+I3jrfUNNmkKjI1iTQ/GmABXsuSyc4rHaSaJpJXoN5nuDM5V0SzadWY0Y8jqpU FOJaD2hP91/HHfrVtI+IQ2IgBGywsJW4HNCs/sEr0ij4u4oD3p1tjWUMsAFUOSIrCslV NBoxpZiZ7q7f/CfE4VE8QFcsf0+h3MfVeNN3jsiMzmRY+RZr5VwffLJ2jmcOCh1aVkxC AcdHPNIIS8Eh5g6tHum61ZGo6bUqXd08kos8p8Cpwb0wNMWie20RVWuP4/NK90XLQSl8 P92nzIF+QFayW6O4HwXeJXL1gGjHzPPoQnSXuP7yz3KKsqMfxhbIHlYotSzjG/idijgs Ec/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ifIZAzNVT2B/i9XTJQsPRk+PU/9ItfXMKgm1r/uxjLc=; b=HniVsPTVknlseFreRIKMBJVhfbikfxzL0GDLMNNVqIiP6caRRgMV8VeeyoVhNpYPX0 IUlStc1jUTdbyPfyyzu9pdW+GJTMAS+XU0pcjYXsKhxZPO8eRMH3wl54vH1tgwg6SyKB yEuv9EpFv5nFo+T0IcIsbJ0Mkso6TWkIoptWDkEXz9H6KDJso2wwi/UCP8aB79U3krJo vyNRC6ogrfMNRI25jRUMJumVuhaRR4bg3b6H9kE3T1vIH7shJC2wiSji6g8Xoidun2X7 IfHtNUweXM7qmDacj7j3RqN4oM0+YZ9Ep0fIvuPDnqHs6b7y+JJ/yRJoDSYUeiSyC7Tq YDsA==
X-Gm-Message-State: AOAM530WatPKI8XDfqOY/nj7qY5RwFnfc4Qmqpq107/QUf9sutAZ8xdP kgYqB6lWlq7P+ug82zpIu7tbuWKTHHMuXQ==
X-Google-Smtp-Source: ABdhPJzdaHTd+1SBbTo0W6LcCDwK/iB1VfJrZGws06cjtKGkLUqDKlkwccAx7ibZ3ZfIfjvw3vrcRw==
X-Received: by 2002:a05:6a00:885:b029:19b:9057:16f with SMTP id q5-20020a056a000885b029019b9057016fmr49019031pfj.80.1609346334568; Wed, 30 Dec 2020 08:38:54 -0800 (PST)
Received: from mike-mac.lan (107-182-45-95.volcanocom.com. [107.182.45.95]) by smtp.gmail.com with ESMTPSA id u14sm40223061pfk.111.2020.12.30.08.38.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Dec 2020 08:38:53 -0800 (PST)
To: Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <9f6782b1-e85b-1a9c-9151-98feff7e18ea@mtcc.com> <CAHej_8m0OWsTt+tcSgUh+Fxu=HH_57nsb2O1Q_fgA2453ceh4g@mail.gmail.com> <140485eb-020f-4406-3f2f-e2c475ea51e5@mtcc.com> <CAHej_8mApfoF2ORgL+DoYTanrdhMjvT9H27kORwLKCQc1C9sRw@mail.gmail.com> <5588dbbe-b876-ed80-c80f-792380e3718f@mtcc.com> <CAHej_8=kW_t_JkOxUud1Uz8+PrbMh5CfwfxZK=mhe0wjW8wQpw@mail.gmail.com> <54dd9978-bcd1-6757-ad27-dcef6db6e5f7@mtcc.com> <CAHej_8kCi=7oqojDH_rbjn7kRg-PTDJWLgcKTGK9z-baUnKeMw@mail.gmail.com> <ef32de1e-d47e-1d0f-3cec-5994c7fdb7ae@mtcc.com> <CAHej_8kjSsQK_XEbdjWzV5npa29YjGadzD06Fmx3QLB4p+n_Cg@mail.gmail.com> <937f1019-a028-308d-2a0f-1e720fd49dcd@mtcc.com> <d8014c2a-c1c9-9eac-e64a-5f285bab7fd3@tana.it> <CAHej_8mgYr9ERAxmup+keZT5u8L+qgCxcSLH7Z=BEuZLouttpg@mail.gmail.com> <72e20c17-e991-e82a-9120-a27097e3ac58@mtcc.com> <CAHej_8=6huc-N4ymDTOWZXHGjQQ-3RFDdomRzmGp4kOseHckMQ@mail.gmail.com> <7863d250-f56a-1fe1-44ee-fbc7486d48b4@mtcc.com> <CAJ4XoYdMdaE92UOrXvcAqm2iou+PCGg_uzHUsmBsYRe1PivBJw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ac7b7b32-c544-60f2-1a6a-a5a210ac72ed@mtcc.com>
Date: Wed, 30 Dec 2020 08:38:52 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAJ4XoYdMdaE92UOrXvcAqm2iou+PCGg_uzHUsmBsYRe1PivBJw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------84F4B323B8D1E2E08EBA74BB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8cEkEJ-Tc0tZaU2hFK6GSFXOav8>
Subject: Re: [dmarc-ietf] auth-res vs. dmarc
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: Wed, 30 Dec 2020 16:39:03 -0000

On 12/30/20 8:22 AM, Dotzero wrote:
>
> You just stated the case as to why this discussion should be ruled out 
> of scope.  " DMARC != Auth-res." and " DMARC in auth-res seems to be 
> an orphan"
>
> This is the IETF DMARC working group, not the AUTH-RES working group. 
> You gave the example of someone writing a crappy Thunderbird extension 
> as a reason for the working group to change its focus. Perhaps getting 
> the extension author to fix their extension might be a more fruitful 
> effort.
>

Let me put this another way:

"The verifying DMARC SHOULD encode its results into an 
Authentication-Results header [RFC 8601] for downstream MTA's, MDA's, 
and MUA in the same administrative domain, and those downstream entities 
SHOULD use the Authentication-Results so as to not put undue burden on 
the DNS infrastructure".

Anything that would cause them to have to violate that SHOULD is a 
problem that needs to be resolved.

Mike, getting tired of the circularity going on here