Re: [dmarc-ietf] is DMARC informational?

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 07 December 2020 04:48 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 C37223A00D3 for <dmarc@ietfa.amsl.com>; Sun, 6 Dec 2020 20:48:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_PASS=-0.001, 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 bdE8bnaK2oU2 for <dmarc@ietfa.amsl.com>; Sun, 6 Dec 2020 20:48:57 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 53BA63A0FDA for <dmarc@ietf.org>; Sun, 6 Dec 2020 20:48:57 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id b23so6851203vsp.9 for <dmarc@ietf.org>; Sun, 06 Dec 2020 20:48:57 -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 :cc; bh=Mfn+qLf4DSMaX1J+m26gbU8ReAu98qGCJbck+DAm7gw=; b=scxAWf6qcRxvdhtN+Jktg1BtOIvLPuw4lGvx3zQkVcmA+xpQZu02jk2pNIQabtHCAy xOjq4DQhzcnvEDC6pkn/WEtpvyrQML8YGEf7PgEz73C8C9WEumfe7aWDZY8IHKYiNV3b VwczZg0/MpzF2NkzY2z3OF6KQXHCi3Pmon9NAX4p9NNJMuaRwIiBnTC/uC7zRAku+57P zIg7q3VCLG+GRhw/8LYdzX1R/bOD+25YvoIdzq/VOAVg0g+6UvhENNLnYK1O36SbqCcz Bmno6bN3CyX459Ghk84TjtjozW75rdopUQ2AmvOUDWBhG3KovdEMq+sup7Ape3536Iev 24KA==
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=Mfn+qLf4DSMaX1J+m26gbU8ReAu98qGCJbck+DAm7gw=; b=DS88niuLS7qQRwocixBfdvYmiCtMIYtCpyYJl5WlTCQzrN1Vkg39JxdIiBxc2/lZ/y xAem0Nmep3T/tKZRsd5QEmQBFN7i9FV+CaxsWTFgdumdq9BfFHOr+vrFQ3sTkSTMr5FQ nQF7WRHYNNyoWVeEU0HtuPzUgpKOODzsRzwphyK1t70zCAZOw9N3FJFc2aURGAbL1G/I DxSBv/iIWGy/S/y3VVJf13newGhSi4zWLM1iLKBSYysFinA44q2AQP1uujFn4ep4TKEc yy9jDCwPnSLXsAxmpwubguEHpp4qYL/IRKjzNNaKpwgWGEl7ne+ZgRyTdOOYqlmdw/aU mqEw==
X-Gm-Message-State: AOAM532uPKH/dX/ETf3tLqoxk0EhO581BaH8t4Pahwn6dVGv5ajcX9Q4 +hdVGdB0Y6Uas3TMkAnufp0J6n6PR9R4xa8K6B247Cyw
X-Google-Smtp-Source: ABdhPJy/Ce35YQSSh1eZd/+cgsxeFRMxssJD+BuH/nB/6iWA7bsTMFYonLJ5V8LDBC8nuIjnNUeA/LH62v9nmS30g8E=
X-Received: by 2002:a67:1d07:: with SMTP id d7mr11006930vsd.33.1607316536211; Sun, 06 Dec 2020 20:48:56 -0800 (PST)
MIME-Version: 1.0
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> <1daf772a-e9d0-904c-cbb9-6730d70e4424@mtcc.com>
In-Reply-To: <1daf772a-e9d0-904c-cbb9-6730d70e4424@mtcc.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 6 Dec 2020 20:48:43 -0800
Message-ID: <CAL0qLwb3pLVFkOiuKeY38Kk9wEiesbyZCiBy72Ls5yRwN6EpdQ@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002ebea005b5d88b32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/79DXYiVMhCQwMFl3YKijdnkAj8M>
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: Mon, 07 Dec 2020 04:48:59 -0000

On Sun, Dec 6, 2020 at 9:20 AM Michael Thomas <mike@mtcc.com> wrote:

> 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.
>

As I recall, people took a run at trying ADSP and it was largely
unsuccessful.  I recall at least Yahoo, PayPal, and Google trying it but
finding that it interfered with their employees' participation in lists, so
they each invented new domains for their employees to use as separate from
their operational public services.  This basically led to its demise.

This might also be because there weren't significant actors pushing for it,
or because it was basically an all-or-nothing prospect, or because its
scope in terms of domain name coverage was too limited.  DMARC was in some
ways a second attempt at ADSP that tried to address those apparent defects.

In addition to reporting, the Organizational Domain, "pct", and "sp" were
considered major features at the time.

-MSK