IETF Logo Mail Archive

Re: [dmarc-ietf] understanding section 7.2

Michael Thomas <mike@mtcc.com> Wed, 27 January 2021 20: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 D8AE93A045E for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 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.249, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 Fh2BOUPmYHbm for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 B8ACE3A0408 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id q2so1718531plk.4 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=9aQk/KXte7TFQS/HYs8eryfTPBe8J6AwEdfFUvcZBXo=; b=PnF/ASNJkyz53A6QqzBSL3oCZdvQbIEOaq4mN32UV67zC3KbjXASHx27+3U6o2nwph s2us29mMzdLEfMuBrTo3f/QY9Vsg7pTSyWHau58rUCaNc2Dj6QF9FSObotEZ9Uf1qJx/ fOj/hD6XDp7FYH/FbJ5OlYBitLkTDLeYr/IHYI6/83WiJZgJUzt9eRBETvJ0jl2VeUbx ed9ZZ9M258PAb7rZ3+rhuxuECXWT4z23k3WjAna+Iy/FgCXKpPvQQ1hmGpo/5vulT1/3 70OdJF83l2mexUe2xSzFavypMuQi4G9YGIEhsEM72xWbvTNSPrEUBdEvnfxnwZy9DVpw 3Byg==
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-language; bh=9aQk/KXte7TFQS/HYs8eryfTPBe8J6AwEdfFUvcZBXo=; b=YpK1fSSiGbVQ+PhejcR9P4QenYNG9FzKHf78EgdX6h1TZPaSqH8EFO0CZovT1o1OZv jlPPUGVxRtPgINC6rPE3a/pJD1bbRbafEPJP24sHw14v0J+jGuaMelZ5SppscpAgJGbS J/HPMC1Ovt1wzVaenhtXjubvfjbOIrEJSMW1gEMhm9imPFtiDley2k5Wxvf5AXgJjEA2 wU/jm9qoCtAKZuNkmrEmZwIMKXq2NfAV5CsZYs5QGs8U7yfk4DnpFD9OjQMcWz+MiRXO 1A+RKsMMFo0NeajWUeZtnw0pctXxDW4IWB5ZF7wH51hslnScZTmndwY4tb79VMpNN/Zw JQWg==
X-Gm-Message-State: AOAM532CfbGhpCneWge5m5K5XVI+qUC37uRzmXWU7hTJfczGXidN9orb mE2xJ5TQEVISoIEQ7jfsM062Fmx1oFGosQ==
X-Google-Smtp-Source: ABdhPJyiiGv6sT5LoTkeOxSI97YzA5vlwpEcK9JXBaSwbwVRI4+DXjFhHLv8fYUGLikIBFKpN2eWJw==
X-Received: by 2002:a17:90a:448f:: with SMTP id t15mr7763428pjg.159.1611780155709; Wed, 27 Jan 2021 12:42:35 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id y26sm3282448pgk.42.2021.01.27.12.42.34 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Jan 2021 12:42:35 -0800 (PST)
To: dmarc@ietf.org
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com> <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com> <MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b446c6da-36f3-6690-99fc-5926634242c2@mtcc.com>
Date: Wed, 27 Jan 2021 12:42:33 -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: <MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------E414AF0B0DA4986F99BA3323"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ehD9fZDOEgEnUMr6AKrygtK_xJM>
Subject: Re: [dmarc-ietf] understanding section 7.2
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, 27 Jan 2021 20:42:39 -0000

On 1/27/21 12:40 PM, Brotman, Alex wrote:
>
> Murray,
>
> That is on my to-do (though not ticketed). I’m not quite sure how 
> elaborate the example should be, but at least enough to demonstrate a 
> basic report.
>
I opened a ticket on this yesterday. I think it's 102.

Mike


> --
>
> Alex Brotman
>
> Sr. Engineer, Anti-Abuse & Messaging Policy
>
> Comcast
>
> *From:* dmarc <dmarc-bounces@ietf.org> *On Behalf Of * Murray S. Kucherawy
> *Sent:* Wednesday, January 27, 2021 3:14 PM
> *To:* Michael Thomas <mike@mtcc.com>
> *Cc:* dmarc@ietf.org
> *Subject:* Re: [dmarc-ietf] understanding section 7.2
>
> The schema's already pretty large, and probably has to be, but maybe a 
> trivial example report would be reasonable to craft and include?
>
> On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     So I'm an outsider who has not tried to digest what's going on in the
>     reports until recently so my eyes are fresh. Basically section 7.2 is
>     extremely hard to understand what is in the reports. I know that
>     the XML
>     is what ought to be normative, but a little bit of ascii art could
>     go a
>     long way to helping people understand what the reports do and don't
>     have. I've been staring at the XML all morning trying to
>     understand it
>     and it is very difficult when all you're trying to do is figure
>     out what
>     the reports supply or not. It would be extremely helpful to layout
>     what
>     is in each record for human consumption to just understand what the
>     reports do and don't contain.
>
>     Mike
>
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

v2.23.0 | Report a Bug | By Email