Re: [dmarc-ietf] A-R results for DMARC

Brandon Long <blong@google.com> Wed, 09 December 2020 00:52 UTC

Return-Path: <blong@google.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 4D29C3A07C8 for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 16:52:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level:
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 TMXz2gEv_dkP for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 16:52:10 -0800 (PST)
Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (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 9E1CA3A0779 for <dmarc@ietf.org>; Tue, 8 Dec 2020 16:52:10 -0800 (PST)
Received: by mail-vk1-xa31.google.com with SMTP id d68so153995vka.2 for <dmarc@ietf.org>; Tue, 08 Dec 2020 16:52:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+sDA2breHzjsCFfrBBi32osFsCYZlvYOCXjT0Jeii3g=; b=QsMz7qJd2AUeqf5bmJedB8K6Kr+0m0nsZrg5KgpelPhW+WTpvyarzp5SGBRJZ8OwwZ avT8dTUljpaPJ0aGLLlbAkW2IUcHNuoVwGxUi8mnYRsOZgRJg1RF/fdjRKRr9PUjbzdg zo445FnYr6hemfhErqwCcJlN2+08b6KoD+u9J/9897uwu9kqb+D7jNe+xFkkoy7j1bln ettlmRy0ibCLTmBn5zUQ0oC2vW1nkU33oh2ipBeOqSOvR1A2JFAi7fQPXuhnEUz+p/Yu 2mLKnkcFCeB47kjPpYHfgNpBQfVwZw1dw2ICoYAq1oGq1c81L7BMcNAR4TfBJ3A98ax5 VnXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+sDA2breHzjsCFfrBBi32osFsCYZlvYOCXjT0Jeii3g=; b=T3CDxjpgxIaG22VAqICk8XoTa9c5/E3rd4sBbtIPRotJNVlcowzNeL9qVq1N3vDH+A 532Jwx0Y26E9DNsxgMsOdatTxBLjZTmRtGR2Wp+zKy0liqCi/lewQtQkCUYSXIixfoJo ih/osAlPWdt6JaGge7XhfCKTN/H4VNDN4kcTQGRHZPEsulXtyppPp7Mc4+ruHbQu7XBu gHPXRZEkj/c/GbF+2C7OnnwZCrwEmuzbOy1+uNJ8Pt7pmczZrCWBTh7eMny0VwKdrsoL 5bC+XfuTlZPd0/80MkZO3znQR2AOKO/w3n6r14Ss3iNaHm/h35II6j7GeI4VdnEA0/To osYg==
X-Gm-Message-State: AOAM5329MqxsdugwVBoesL/UjIek+jd1dOf2kPDdukBsDowO1hFusSMv FrraZQLmdfMWJfSXR33F4jIMbg5DKsdopWSHX31o
X-Google-Smtp-Source: ABdhPJy01FP7plC4CB54K8fy7JjuPI1RpYN7oT8+xKqJRx/WcNtsVfbI+RGQ/WYeUot4TobFXY2mqIAupY3jGnfi3sM=
X-Received: by 2002:a1f:288a:: with SMTP id o132mr19183vko.2.1607475129474; Tue, 08 Dec 2020 16:52:09 -0800 (PST)
MIME-Version: 1.0
References: <20201208031609.C8CC52926414@ary.qy> <CAL0qLwYmweiS_bX85L4=ipXXR+AnJo9EX4NnXMAzi6HmfMir5A@mail.gmail.com> <b8d63e53-d7fe-73f1-859e-88136ebe8564@taugh.com>
In-Reply-To: <b8d63e53-d7fe-73f1-859e-88136ebe8564@taugh.com>
From: Brandon Long <blong@google.com>
Date: Tue, 08 Dec 2020 16:51:57 -0800
Message-ID: <CABa8R6uKcEkh7id-TM-DwfGT6iBA5sdCEDzudhjDLKA1BSSCbw@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001461d105b5fd78f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4wvTrZylJj9lMUTgPBlCtMYav7U>
Subject: Re: [dmarc-ietf] A-R results for 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, 09 Dec 2020 00:52:12 -0000

On Mon, Dec 7, 2020 at 8:31 PM John R Levine <johnl@taugh.com> wrote:

> On Mon, 7 Dec 2020, Murray S. Kucherawy wrote:
> > The original intent back in RFC 5451 was to relay only those details that
> > an MUA might care about, such as the DKIM result (so you can display
> > something representing a "pass" or "fail" on a message) and maybe the
> > domain name found in a passing signature (an early shot at caring about
> > alignment when rendering a message). ...
>
> I suppose but 5451 also says it might be useful to message filters.
>

Right, there are clearly MUAs that do some amount of spam filtering, so
disposition
of p=quarantine would seem to be useful for that.


> > So that ship has sailed, meaning yes, we could register these too if
> > they're going to be useful to downstream agents.  Though for that matter,
> > you could just start using them even without registering them to see if
> it
> > would be helpful, because 8601 allows for local conventions (the
> > tried-and-true "ignore what you don't know" thing that DKIM introduced).
>
> Sure, I can write the code to stick them in but it would be nice to have
> some expectation that I'm not going to collide with something else, or
> other people use different tags for the same thine.
>

Right, we clearly send that information around our system as separate
metadata
about the message... for us it would be more useful as an agreed upon place
where MUAs can consume it.

And it seems like in some places, disparate tools are chained together, and
headers
are where that metadata lives as the message flows between systems.  I'm
sure those places will come up with their own or add to some large
X-My-System blob,
but a standard place does allow different tools from different folks to be
used together.

Brandon