[dmarc-ietf] DMARCbis and M3AAWG Email Auth BCP (was re: Proposed text for p=reject and indirect mail flows)

Todd Herr <todd.herr@valimail.com> Tue, 28 March 2023 13:57 UTC

Return-Path: <todd.herr@valimail.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 28341C14CF15 for <dmarc@ietfa.amsl.com>; Tue, 28 Mar 2023 06:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjazbMX2fwHj for <dmarc@ietfa.amsl.com>; Tue, 28 Mar 2023 06:57:26 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187CCC14CF12 for <dmarc@ietf.org>; Tue, 28 Mar 2023 06:57:26 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id d22so7251132pgw.2 for <dmarc@ietf.org>; Tue, 28 Mar 2023 06:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; t=1680011845; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=1I2vSJXtkfv04skYVVGaoTtRk0J3fT/XnuEKDy6oMxU=; b=UgCkhxHWJ5J5sREwM+ojmJD3zGx2GT00zjcdXD6+HohsaEZeTUwAa63rkjWVHvt95L H9Po7Os/yvZiUCAGtw44Mo5uitjvv+S+MEG+J3vHLkCvZaQB97v+r4AFaPsr5BfZUujD KWRdFxjyf5iq0RqPkF7mxbOd71xJEH0YSl/4uVSmigSahqz51FP8dhUa8c+y8yg8Yd31 atFZZT1z5GxZ5YQKWWK+4SH9n+sJr3rRKT0Rd9PK3lTSwoY+ly8JwYXwWzHwxZdLvt8r vtbyCN2oDF35OYh+6IFXLTXcsKGo6pu6P4nHp/A+7T2KznyzCRzznIom94SGY6lLj5Js fgvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680011845; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1I2vSJXtkfv04skYVVGaoTtRk0J3fT/XnuEKDy6oMxU=; b=dhRXxAgoaV/u4VS+urUTgSF7AsuFs3uV/R9RRHH/iDF51+ubOu/r5iyHHxKVuW+lIc 2ceeuTfewssyzYJSCofKwOt+feQmunaxbDQfpJlWz+MP5YTZdPwyTbO2CKUCGAtVwB6i G2RxzVy77U2AXRiqyAMnVr+fgtM+bcir7DdTHoknXAmG+99atztB3dk7T/KP6xcVzz+B 5irjKAf8Jq5w8qHntBvG93xKFMCWDrVsNRdkK7lmw72ddE+OOvB8c0K/q9MKugcQK8NS fwbfeFdg4T7rRtxi2piozdqkuH+W7MdY2+A5lieSjIcTgcz6mBsjq1KZz+7y4G5CiYDP gD1w==
X-Gm-Message-State: AAQBX9fy2On8d230pMemEIHMMiQ8BKWAbsynfNRUuXthMoNi8yPMPO9Z zBPCKwIOjnWS3KawKf46znn/QafNxJEVSJgfP59mVMgNFMhUtIkG
X-Google-Smtp-Source: AKy350anSjVltBzmld5H8fXgUhLavXsN/+epB+WCgQMUCXGJ446THDb5ZA2UesXQ+2XffIWjjvvndGbDpXQuUoX5BMY=
X-Received: by 2002:a05:6a00:8c7:b0:625:cda5:c28c with SMTP id s7-20020a056a0008c700b00625cda5c28cmr7651378pfu.6.1680011845217; Tue, 28 Mar 2023 06:57:25 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+NBg9vzqa0_t-sBf7EKXQ3A=DTyy-Vc7M-ZK9-vfJxmw@mail.gmail.com> <3A0C013F-55E6-46FE-92DD-EF31BC58A55D@bluepopcorn.net> <CAHej_8m7m29EiKUzarR1wBVyxfORfdcX_kgUz0-3uDiqoZ+i2A@mail.gmail.com> <b2f4cee2-49e7-2fa1-db77-7b628ab01f08@tekmarc.com>
In-Reply-To: <b2f4cee2-49e7-2fa1-db77-7b628ab01f08@tekmarc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 28 Mar 2023 09:57:09 -0400
Message-ID: <CAHej_8kLrqOcuPXoef1DiP-MDPBphMKk1Mumtw1id--9u--r4g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040ca2b05f7f63d36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/pd4c9BnVh6No5tu2CGEeLa_TIgI>
Subject: [dmarc-ietf] DMARCbis and M3AAWG Email Auth BCP (was re: Proposed text for p=reject and indirect mail flows)
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 28 Mar 2023 13:57:30 -0000

On Tue, Mar 28, 2023 at 9:51 AM Mark Alley <mark.alley=
40tekmarc.com@dmarc.ietf.org> wrote:

> I know that M3 is totally separate from this group, but this is more-so a
> question for Todd H- does this mean that the M3AAWG authentication best
> practices recommendation will also change based on this if this is the
> intended usage going forwards with DMARCbis?
>
> Quote from the existing document
> <https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf>
> -
>
>    - "DMARC Policy statements should be “p=reject” where possible,
>
>
>    - “p=quarantine” otherwise.
>    -  “p=none”, “sp=none”, and pct<100 should only be viewed as
>       transitional states, with the goal of removing them as quickly as possible.
>       "
>
> Maybe. There's wiggle room there with the "should be ... where possible",
but you're right that this question is probably off-topic for this working
group.

-- 

*Todd Herr * | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 703.220.4153

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.