Re: [dmarc-ietf] Ticket #61 - Define and add a simplified (redacted) failure report

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 10 December 2020 04:18 UTC

Return-Path: <superuser@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 8A3C63A09F9 for <dmarc@ietfa.amsl.com>; Wed, 9 Dec 2020 20:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 62dxohAodgxU for <dmarc@ietfa.amsl.com>; Wed, 9 Dec 2020 20:18:52 -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 3FD1B3A09F6 for <dmarc@ietf.org>; Wed, 9 Dec 2020 20:18:52 -0800 (PST)
Received: by mail-vk1-xa31.google.com with SMTP id a4so908053vko.11 for <dmarc@ietf.org>; Wed, 09 Dec 2020 20:18:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=wZUot1u6s2RCeHqmet1KMMemfBrMFiXUQ04/fiuFOes=; b=ZBri38EVTmqLJBM+N4iMtFlclSzL9rtoZQXkd0Q1xvQkz18ltunLPqP0fWKVxy0deP 4sma0G27BdzepEGQKEEcn6txWW1IA3TSzEftNBpu0XxVoHrDPRtqeZjA8LCSOVNjEueZ At6kXQ1bjY8ZHVyeji7y8Saf8XBOHM+2YyBWxGmKqtOHHReZMH53AnZ4WuqHh78IE4dS 6bzMhvmnHLBMvAc0hp4eoqjud4CfPUu7YA3fvR5+/D8JdWV3N2T/J2iFcLhlyJGg0M7V x9tU7ImTCkV9jBo/PU1TtW/6xpxaLIigJe7HWa83FSDEi0PFXg+2Hei1rs2nOEYbYsfG iTiQ==
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; bh=wZUot1u6s2RCeHqmet1KMMemfBrMFiXUQ04/fiuFOes=; b=dTTaDYWyEIOjxHzr164gJButQ8DKyhCaaWkFUPrLrcju/qCc+eKXcXT7B0EGh2AzQB P6OJRRNDtSHlpuDdygPODbtOuHH1jTZLmMlSdaD7ZUa8FLrDqEbPgj6i7r81kISOD9Wt AN71zzGgd3WHZCA0jErH6/R4D0eizMt3aUzfNAFpsbWztZipYkRjS/Yeqgtlm1vj2ayO 2y2jgdHQb3y5ZPRhXcil7mEmt0eaL+k0Z45T4jBdSxs8JFCCvfRHKEOfD/huXFvjCJ0s iHyyoSdlWO1LWW49w+2/71M3aqrzeHDEXhTLtLdnosoVLtJzFZxtLgz3yL4edG7tDkQb z39w==
X-Gm-Message-State: AOAM530wH0S+jT1+Xn5BmEVBcgtvSo/nLXO8JcOnOFFLlVogB+N0MEHh KSzow7cvchsA0pR8bjeyoVCLMxgMp8m6w+u/wcwYZjHp
X-Google-Smtp-Source: ABdhPJwDA5lKQnnD4SJaS5ir2AaZV0MXUNbGaCbNhapBPxFxIxrO9D5RhPlRpr1UrBIqwz2l90kZoBxSwXrYuN0LsyM=
X-Received: by 2002:a1f:1b82:: with SMTP id b124mr6316104vkb.5.1607573930694; Wed, 09 Dec 2020 20:18:50 -0800 (PST)
MIME-Version: 1.0
References: <609e1c9b-cc4d-d7d1-0fa8-79f515c1eee4@tana.it> <20201209185246.1D40C29474C4@ary.qy> <CABa8R6sU0RQLSBA2LRk4mnkpzWVP5qBMbbHeTaw6VdgG02preQ@mail.gmail.com>
In-Reply-To: <CABa8R6sU0RQLSBA2LRk4mnkpzWVP5qBMbbHeTaw6VdgG02preQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 09 Dec 2020 20:18:37 -0800
Message-ID: <CAL0qLwa04NVQyP+=4o905ZF-e+NxmHhQqXZ5sGbdU9x8T3jSjg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000016df9c05b6147999"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/X7shrtwll1fLBdfoHKJ-sLRYnAQ>
Subject: Re: [dmarc-ietf] Ticket #61 - Define and add a simplified (redacted) failure report
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: Thu, 10 Dec 2020 04:18:58 -0000

On Wed, Dec 9, 2020 at 1:29 PM Brandon Long <blong=
40google.com@dmarc.ietf.org> wrote:

> In today's much more privacy conscious world, should we have RUF reports
> in DMARC
> at all?
>

Forensic reports in DMARC are akin to the DKIM failure reporting we added
to ARF back in the MARF working group.  In fact if you go back and read
those RFCs, an ancestor to the "pct=" tag is there. (RFC 6591 and RFC 6651
in particular are what I'm looking at.)

Back in the original DKIM era I always found this kind of reporting to be
really valuable especially since DKIM can fail for a variety of reasons
that are far less obvious than SPF.  Being able to get the verifier to tell
me exactly what it saw and compare it to what I think I sent was key to
getting the implementation right especially in curious corner cases (any of
you that remember the DKIM interop event would know what I mean).

Seems to me that's still a useful thing to have, at least sometimes.  We
might say something like: Include support for this, but don't have it on by
default.  Or even if it's an extension to DMARC and not part of the base
protocol, it might be really helpful in some situations.

-MSK