[dmarc-ietf] DMARCbis WGLC Issue 132 - 5.5.1 and 5.5.2 SHOULD vs MUST (was Another point for SPF advice)

Todd Herr <todd.herr@valimail.com> Thu, 14 March 2024 14:09 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 823E1C14CE31 for <dmarc@ietfa.amsl.com>; Thu, 14 Mar 2024 07:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 ObzmZE34EklG for <dmarc@ietfa.amsl.com>; Thu, 14 Mar 2024 07:09:54 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 D909DC14F5E4 for <dmarc@ietf.org>; Thu, 14 Mar 2024 07:09:54 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id 3f1490d57ef6-dcc80d6006aso890677276.0 for <dmarc@ietf.org>; Thu, 14 Mar 2024 07:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; t=1710425393; x=1711030193; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=s72aV27nYAbAU9AS7YqJbb8cbgjF5YAQw5W8ufYRFj4=; b=JkPelUTXmEaC1ypWQMrBB7qcRI4yqmF7mwCCCkvyQnnbGVEFqzogAYOAwr08BRts4b WicWlz5E8ZSG5xzTL1wvF5zLndSFzS2uGsqENRcOamGOk19w0COAu+z+8abr62YnE+rx X1QYy2WHbgwwb1SbUIMuD33W4fCC/J2BqDBpOt41DnMWHazmx2av39T2niT6tJLDK8cs Kw12kR9eLsn3c4Vr7RJxX8Arw47exe/YS+whEzxi3sCZDDgnur/JpTwskSw2X1pf14Md kjO7na8uSW29VQWu+br0FWsmgBP+8PL+5+itCIHKcqRHBq98ncKUXvGrid1O7DYqWJxW KJZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710425393; x=1711030193; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=s72aV27nYAbAU9AS7YqJbb8cbgjF5YAQw5W8ufYRFj4=; b=Zp7+XPMZkl4tagLvnznwlz3hgmbAicHh+IjYvO5BYqEh34S4UaJC4P/yZaCJvAKOvw v+OVfx6OVR4G1XQxU3BjMmIM0fUuKzLoL4K2/KGVlJJ0raf0PjyReknGFKfQXPPfFxwN qTq8shGkkB00M7cnRKmEHMWgj0wC83l0lRnVSxu8Dbppf4+R4Gcst/65knA1gyQABlDn KpGgucVvCAPuCqNmOKb2iurYBYsb+lU7RjbUwrVoFJTUy2phkj1UTSfBJjU38zEgRXNo ofgsyPKRepNHWV33SlgGLBkTvp9qqKkb2ebW7LIG/ftGPqLLPLASuKE/WVKGaDA7Ltcv C8dw==
X-Gm-Message-State: AOJu0YxK9fR9gNCLAVxmW9jFkBnxojtXFhNslMHf53tISr6HRjRbeYiW a82uOc1yksfEbAlaeILiROC+K4lI7Ni4U41hYHN3K7w+4rFNh6N1zyQz2plPEJ7Iqk/db22rc3U CW4oiqupmLulIBqogBq6U3pY4cqa4/C/hLbyVL1d1ZVRhEPZWkcw=
X-Google-Smtp-Source: AGHT+IEK+7/KPPAvHGmsvm8uC67Q22qAsUstHCiMaAPKT0S+LkbAefAqRowzKBVkFHKdAr9lnI+CjQULbF0ETsZ2cXE=
X-Received: by 2002:a25:b21d:0:b0:dcf:c086:dd43 with SMTP id i29-20020a25b21d000000b00dcfc086dd43mr1881592ybj.14.1710425393077; Thu, 14 Mar 2024 07:09:53 -0700 (PDT)
MIME-Version: 1.0
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 14 Mar 2024 10:09:37 -0400
Message-ID: <CAHej_8k=GC11rNesi6dRnMv+Bdrtq-GRfFPuGAJxfWa9ydpcPw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8480f06139f7180"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/S6C28B5JWORxHIUZNy58XeArSe0>
Subject: [dmarc-ietf] DMARCbis WGLC Issue 132 - 5.5.1 and 5.5.2 SHOULD vs MUST (was Another point for SPF advice)
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: Thu, 14 Mar 2024 14:09:58 -0000

Colleagues,

After reviewing the "Another point SPF advice" thread and Murray's separate
post re: SHOULD vs. MUST, I have opened issue 132 on the topic:

The current text of section 5.5.1, Publish and SPF Policy for an Aligned
Domain, reads:

==================================================
Because DMARC relies on SPF [[RFC7208]] and DKIM [[RFC6376]], in order to
take full advantage of DMARC, a Domain Owner SHOULD first ensure that SPF
and DKIM authentication are properly configured. As a first step, the
Domain Owner SHOULD choose a domain to use as the RFC5321.MailFrom domain
(i.e., the Return-Path domain) for its mail, one that aligns with the
Author Domain, and then publish an SPF policy in DNS for that domain. The
SPF record SHOULD be constructed at a minimum to ensure an SPF pass verdict
for all known sources of mail for the RFC5321.MailFrom domain`
==================================================

In the ticket, I propose the following replacement text:

==================================================
Because DMARC relies on SPF [[RFC7208]] and DKIM [[RFC6376], in order to
take full advantage of DMARC, a Domain Owner MUST first ensure that either
SPF or DKIM authentication are properly configured, and SHOULD ensure that
both are.

To configure SPF for DMARC, the Domain Owner MUST choose a domain to use as
the RFC5321.MailFrom domain (i.e., the Return-Path domain) for its mail
that aligns with the Author Domain, and then publish an SPF policy in DNS
for that domain. The SPF record MUST be constructed at a minimum to ensure
an SPF pass verdict for all known sources of mail for the RFC5321.MailFrom
domain.
==================================================

In addition, the last paragraph in section 5.5.2, Configure Sending System
for DKIM Signing Using an Aligned Domain, reads:

==================================================
The Domain Owner SHOULD choose a DKIM-Signing domain (i.e., the d= domain
in the DKIM-Signature header) that aligns with the Author Domain.
==================================================

In the ticket, I propose the following new text:

==================================================
To configure DKIM for DMARC, the Domain Owner MUST choose a DKIM-Signing
domain (i.e., the d= domain in the DKIM-Signature header) that aligns with
the Author Domain.
==================================================

Further notes on the threads that gave rise to this ticket:

   - I do not believe that recommending the use of the ? modifier in an SPF
   record configured for DMARC is appropriate, since as I understand the ?
   modifier, the result produced is not "pass", but rather "neutral", which is
   the same as "none". Therefore, an SPF record using ? would not produce an
   aligned pass to be used with DMARC. I am willing to be convinced that I'm
   wrong here.
   - That said, I think there is room for discussion of too-permissive SPF
   records and the  cross-user forgery discussed in RFC 7208 Section 11.4, and
   I will open a separate issue for that to expand on section 8.1


-- 

Todd Herr | Technical Director, Standards & Ecosystem
Email: todd.herr@valimail.com
Phone: 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.