Re: [dmarc-ietf] is DMARC informational?

Michael Thomas <mike@mtcc.com> Sun, 06 December 2020 17:20 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 79E0B3A046D for <dmarc@ietfa.amsl.com>; Sun, 6 Dec 2020 09:20: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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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.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 VWVI70Hdbnxn for <dmarc@ietfa.amsl.com>; Sun, 6 Dec 2020 09:20:37 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 E75203A046A for <dmarc@ietf.org>; Sun, 6 Dec 2020 09:20:36 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id 11so1201107pfu.4 for <dmarc@ietf.org>; Sun, 06 Dec 2020 09:20:36 -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-language; bh=PZkcE/n0f6zr2tKKrYzHCbga1EzQy168ij+ZYcuysCo=; b=hAjRPpbJJFzf6e1ksyDGHITd1IbQhixRyByRw5hXSDVx8Ap7QZa8DIaHMjkxYM2m0n FR5d3lh6do/CCZw0wBbe8gCq/CDTz2pkIhQNZBtuWJXyGQyRMW2Voj0Sx6Dw9NmGqPe+ bV8Ok3DFBdalCTaCGKBdDtyrNufF58axwQUFyHb/99yELzccx/KVSxG/c1+WI32geiny EprQqIqq7krieNGuAm7NhJAiUSZ0rQLTHDS7Q5h+uN4uvHLIIUXhiERcnmRGWvCQ8tzf dRBwQjJmayBkT2iGi09JPXM3V9bocWhb/dmZhD/LlNPL78U0RhtFc0i2+Xl9BQdq0fZz bR1A==
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=PZkcE/n0f6zr2tKKrYzHCbga1EzQy168ij+ZYcuysCo=; b=RkINMFerl1eqGgn12pnafK0aVNmcEKXISyL5HVExdje/E9Yg5P2r4h8s2Usm+NF1uK 0rhYuzBEMImgLJ8izcAAPnjWou42+9uR1Vk1anUED7+0qm7UE37B0qkdfuNU4sRxau23 tONVvoPbF9++vhWRt6meeU9u8rDfznqXxW0gdxrje2aXZ3xs8GcvCp14UXsLKr7L4r4J zatThirruKuhXXsCfcDt7IeEV4WEKtmBJyOCrqJSGGT8Pmdu6u+DrX2v7EgWtXFUJVhq 9DquUpErAa6eUO9U2RccnB7sHYgYibSy2lUQZ14C5PTXrqgTpwitctlZuuJn/ZL/ThWf JhhQ==
X-Gm-Message-State: AOAM531GJTno8+rybpzx+3Vbawl97FhY3Cuk3Eezz/tyOPMUkiMs+I7m XHCFPZfIrEUp3inSEwiXS5KBjy7kAltnUw==
X-Google-Smtp-Source: ABdhPJyV3+uLMfWtJCmEGToZ03FAAf6GbOB/ms0TcGmqBaObXnm2UnMHpMFIxwwgqpRUY6LJaIBTdA==
X-Received: by 2002:a65:6a4e:: with SMTP id o14mr15371109pgu.65.1607275236006; Sun, 06 Dec 2020 09:20:36 -0800 (PST)
Received: from mike-mac.lan (107-182-42-33.volcanocom.com. [107.182.42.33]) by smtp.gmail.com with ESMTPSA id m17sm1636241pgi.11.2020.12.06.09.20.34 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 06 Dec 2020 09:20:35 -0800 (PST)
To: dmarc@ietf.org
References: <134860ee-5fbf-2fb3-a5b3-4be68806ab22@mtcc.com> <CABa8R6veBqY1fUuoy3Qm=vfrV51_5YyoS0P4SLSbKJP_Qrcn-A@mail.gmail.com> <7224575d-685f-5020-073e-c1880acecc88@mtcc.com> <7e459496-61f8-ddcd-713c-3b6be448090c@gmail.com> <2cecceac-1add-44ec-6e16-e157fee293fe@mtcc.com> <5a577765-4a0d-e1bf-5321-dfeff19d107e@gmail.com> <40d7e78e-7026-c65c-383c-df4e3c537de3@mtcc.com> <CABuGu1qpn16+=6CUqpXbAiFrLV87s9Lx4+fqCzNtkD83HVPzEQ@mail.gmail.com> <C456270E-89A3-48BD-B123-1D789682AEBE@bluepopcorn.net> <18e93db9-bde7-bf49-670c-1e680f2ce3a6@tana.it> <65bbc2a6-701a-1729-7892-ef68c1b6b237@mtcc.com> <5bce5710-6553-36ee-c46e-cbde702141e5@tana.it> <CAL0qLwZZ31bYwPphHEDsfeLCRPEZmp7jOZOR5RVof3J5LHxe6w@mail.gmail.com> <CAJ4XoYc890qRpWq4gz6HTxGO0Uu515SLFkMf3D6vKJry8puVRw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <1daf772a-e9d0-904c-cbb9-6730d70e4424@mtcc.com>
Date: Sun, 6 Dec 2020 09:20:33 -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: <CAJ4XoYc890qRpWq4gz6HTxGO0Uu515SLFkMf3D6vKJry8puVRw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------50A047D3BE537E5D76B6F817"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Go-NTuobgXqJzm7KsLwLKpKTvDs>
Subject: Re: [dmarc-ietf] is DMARC informational?
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 17:20:39 -0000

On 12/6/20 7:13 AM, Dotzero wrote:
>
>
> On Sun, Dec 6, 2020 at 8:58 AM Murray S. Kucherawy 
> <superuser@gmail.com <mailto:superuser@gmail.com>> wrote:
>
>     On Sun, Dec 6, 2020 at 5:09 AM Alessandro Vesely <vesely@tana.it
>     <mailto:vesely@tana.it>> wrote:
>
>         On chartering the WG in 2013, the decision was made to publish
>         DMARC as
>         independent submission, even though it was going to be
>         discussed and reach
>         consensus of a IETF WG.  AIUI, that was the original question
>         of this thread.
>
>
>     This isn't correct.  DMARC was not published as a product of this
>     working group.  It was published through the Independent
>     Submission stream, which can only produce Informational
>     documents.  At the time, this was because the group advancing
>     DMARC wanted to preserve the installed base and not cede change
>     control to the IETF, so a working group was not an option.
>
>
> Murray, your recollection isn't quite accurate. The group advancing 
> DMARC was looking to preserve the installed base for a defined period 
> of time due to a) almost all the implementations were custom code and 
> b) there was a desire to see more experience in the wild as almost all 
> of the deployments were by members of the group advancing DMARC. There 
> was also a political element in that there were folks within IETF that 
> felt the DMARC folks were only looking for a rubber stamp, nothing 
> more. This resulted in part of the pushback.
>

What I still don't understand is what drove the decision to deviate from 
ADSP. From reading through DMARC, it's basically ADSP nee SSP with 
provisions for SPF and the new reporting feature. SPF had its own policy 
at the time, but adding it and the reporting could have been done in the 
context of an ADSP-bis. Had I been paying attention, I certainly would 
have supported adding both of those features because they clearly make 
getting to the end goal better.

Mike