Re: [dmarc-ietf] Revisiting the Race Condition in draft-crocker-dmarc-sender-01

Dotzero <dotzero@gmail.com> Wed, 19 August 2020 17:07 UTC

Return-Path: <dotzero@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 2D6793A0D3F for <dmarc@ietfa.amsl.com>; Wed, 19 Aug 2020 10:07:31 -0700 (PDT)
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 RYOGaUIiFAam for <dmarc@ietfa.amsl.com>; Wed, 19 Aug 2020 10:07:29 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 833873A0972 for <dmarc@ietf.org>; Wed, 19 Aug 2020 10:07:29 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id x69so22272205qkb.1 for <dmarc@ietf.org>; Wed, 19 Aug 2020 10:07:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ftgotU/o5nDvp1Xft99YyNctxDC2cRDTXIJz5HzU/t8=; b=usQH4fBq77Vs76fSjkqiH21WCTODLkilB7dvVTU3ZgXZUTm5j1PfeLG18FqQq1JHnb INsDp29PWFIn8hdzAW4MfZRliKmYBC9EIRdxWBQzK6COAyxB1wgMp0P4x/a8OGpDVXsq EqWoIq9PF2FTSbSCErv8Of4+HN2SvxlAPioLlmcU+5fqpgV4NSqqlkxT5HO+Hk2Cw8Im hQGF8AKih64dM8LbmnkgDTRaQRl+8Td4zyAVCH7g+BUgKd+Ukwid2Xjcbp6E2o9xKZXH 3swbj98yDtthyFz31xYm4jk9u4Q4h+WBI8Xf2oNVPcyI5SDWrcipVCFkuS58dca0zSb+ wWGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ftgotU/o5nDvp1Xft99YyNctxDC2cRDTXIJz5HzU/t8=; b=C+gpBHVrxhFg/tSWB5rnwz7uuGg7PXFAfaYxvSNyhFoiKLrFLnh/zzUIWe6AGVzLYf NOAXFBf/q64pfPkQK1bdOvr3hGbjofIzjm6fYe9wqeGE2g8tad9od8QPJkErDD94f5Fu uiUIH/aDTgnUAmmJcI14ImNybbvGLC67AEdm15UrF9yg1QDjFS8cLugp+23kfvCOT51g vEfJbO9oXMfHbmyzCdende7b9T2tnlyF6NWyhvjWFSSNeMZzdxjrhetvYLLR+X3w+745 qPe30O+vT22DfXO1B5tFzRpGuriVKFnFf7F2WNcC7zO+DcL5oJXKDNNDp2oPqSZiv0eu ryVw==
X-Gm-Message-State: AOAM5301hqYesLpE10BTjkevWTPSpdXYmKGzVdrKAU/hX0U8Wxbu6xTy w4U66XAzYiPHWE2sxQ468Ngd3UV7uadjuI/bXIV7xjn8ZpY=
X-Google-Smtp-Source: ABdhPJzDCOTdyp/vvYmqA+rn3DjWMhf6QVk63yLxzwoSFuUnUjTwInEnuxbHWPQ4Q/OdAvBSqGTSitzSBZ5uaxEzF2s=
X-Received: by 2002:a05:620a:545:: with SMTP id o5mr21601796qko.187.1597856848496; Wed, 19 Aug 2020 10:07:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a0c:fcd0:0:0:0:0:0 with HTTP; Wed, 19 Aug 2020 10:07:27 -0700 (PDT)
In-Reply-To: <73cb2f8c-5f9-8fa2-6b13-3ec9318f2c5@taugh.com>
References: <CAJ4XoYcue16VU6otKOzQBFy_59nD8DGcDQb8H=Z0MsX-XLah8w@mail.gmail.com> <20200819004724.16EE11EED520@ary.local> <CAJ4XoYfFKe1yKK5OBx91qJOxZNHSNptu7kHS_bKnyGo_wGLB_w@mail.gmail.com> <8e939d83-3cc8-3989-4e48-7e79e7e86973@taugh.com> <CAJ4XoYfFWbGky+A7GXZeTAth_5JQz1y8QQXsGW-bQ=86CUTt5A@mail.gmail.com> <73cb2f8c-5f9-8fa2-6b13-3ec9318f2c5@taugh.com>
From: Dotzero <dotzero@gmail.com>
Date: Wed, 19 Aug 2020 13:07:27 -0400
Message-ID: <CAJ4XoYd71Ybn=15=y7Ydg3cSMzpkaAr45ynUshTqGEFzq3KLaQ@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000db4d4605ad3e09fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/2-L0D50svFzE9R8UKJIDFdE1j3A>
Subject: Re: [dmarc-ietf] Revisiting the Race Condition in draft-crocker-dmarc-sender-01
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, 19 Aug 2020 17:07:31 -0000

On Wednesday, August 19, 2020, John R Levine <johnl@taugh.com> wrote:

> On Wed, 19 Aug 2020, Dotzero wrote:
>
>> Then Ericcson as an organization has made a decision regardless of the
>> objections of those employees. The correct thing for Ericcson as an
>> organization to do is to publish an internal policy that employees should
>> not use company mail for participating in mailing lists. An alternative to
>> that would be for them to hire someone to help them come up with a
>> workable
>> approach. We both know plenty of people who could help them.
>>
>
> No doubt, but they're not going to do that.  They want their employees to
> work on the IETF, the publish p=reject and they apparenty believe the
> contradiction is not their problem.  So we're stuck with it.


For some definition of stuck. I happen to believe that validators/receivers
SHOULD generally respect policy assertions. Mail list operators should as
well. Absent a functional and meaningful mechanism for authorization of
specific intermediaries by domains, that is the way to go. If things break
and users complain then those users should be told to contact their mail
administrator. Just saying.

>
> Of course you personally know what DMARC policies mean and what they
>>> imply.  But every time a list has to rewrite a From line, we have
>>> evidence
>>> that someone else doesn't or at best doesn't care.*
>>>
>>
>> I'm going to guess that more often than not it is the latter. *I heard the
>> same. Too big to care?
>>
>
> Yup.  They want phishes, or in Yahoo's case expensive user complaints, to
> go away, they don't care about discussion lists one way or the other
>

Perhaps they would care if users/customers complained and or walked. Again,
just saying.

Michael Hammer