Re: [dmarc-ietf] DMARCbis WGLC - Issue 141 DMARC and What To Say About SPF -all

Neil Anuskiewicz <neil@marmot-tech.com> Sun, 07 April 2024 14:00 UTC

Return-Path: <neil@marmot-tech.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 AEB30C14F610 for <dmarc@ietfa.amsl.com>; Sun, 7 Apr 2024 07:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=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=marmot-tech.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 TgT8BIop8EMr for <dmarc@ietfa.amsl.com>; Sun, 7 Apr 2024 07:00:39 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 7F441C14F60E for <dmarc@ietf.org>; Sun, 7 Apr 2024 07:00:39 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-1e24c889618so29265065ad.2 for <dmarc@ietf.org>; Sun, 07 Apr 2024 07:00:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marmot-tech.com; s=google1; t=1712498438; x=1713103238; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=TNPNxzvy/ujpg0nCDC5h1zKsW2CfqM1IlMXwKNI9Fb4=; b=HY48qVI28Jw4rB2VosW6mkkGnWLqi5h83xL77YiLTSN4d7/facX+GmqkCm1Aqx/Bv+ jJzTHXFSly3zdjae+kk5f3JZe8GW3zvAnrvOfvlFlgzskwWfAT/axleA+pYfS5VqjPGt dhjAWETdglS445ZbpyNlF08dxlvgXCEVyx01QUcLT7Vbn3bHbBhiElKfnqFhad8wAvCI Z9SKIbHz1is0WfnGuRXLgJqnx6rbfzgegmzq2kFEODdL0uC0oH8gu9ZoHhgavHgIVEBq /01STz2e1THC8Bg7w2jMz1ynSkCSQd8cOCrR3392k6zFKMngYiUHA3qVx8j029KySGLI z23Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712498438; x=1713103238; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=TNPNxzvy/ujpg0nCDC5h1zKsW2CfqM1IlMXwKNI9Fb4=; b=aJ6gmoxgTA2k0yuvdDgCo13MMlaksGJy1ZbMkz+F7o5kCH3Ni6BwLVkRa2BxiHpn/+ w6IM4WUby6gWpMU6M/6zIbot2Ym3C/HaN6QAiWjxXNBw0F+Geldwe59370LgZ2jsNalw OzSx0alpHbLvqrIu46snStbMjynILl27BixWT67R7YVWdBM8u3Kea+LYGULaUGIfNLbn CWsDAgDdBD6eLWr2P4uxeVAbHI2lutpGp594pchFTcU3XC1nnniLnMnOjsj0QJr7IWxn CDJjwZWShrWq2sqQMZ9VALAuRUwPob/o6+0CxNSP37hxW8dSb3lpp0fDx9gjpBLZZyQA eL1A==
X-Forwarded-Encrypted: i=1; AJvYcCUMfgAhBCPgE7BzvZxmEmUCKtu9uGRXGTD8tuQkUYDgdcq7JjCtRcBaIpak/coyLcVZEbwdzMxcDapWg1nV1Q==
X-Gm-Message-State: AOJu0YzufcNhvcPKQzrQcvLKj5SJhhHCnRADedI+X5aK/MReghwqSs2H KC1b6cEUInWUdHFjNaSehIsOBYcRt8IVK7XYv481/OoycEP2GVocoEnLXJVnUgPI+Kne1L2I/XK /
X-Google-Smtp-Source: AGHT+IEedfQfyw2Zk5DJH0KLklTF/LxYV6zwC2DDbQrJDMTMwAtpV3Yqz4+ARHfnRxeJi9pn2TJIgw==
X-Received: by 2002:a17:903:190:b0:1e3:f27c:457a with SMTP id z16-20020a170903019000b001e3f27c457amr1832042plg.45.1712498438103; Sun, 07 Apr 2024 07:00:38 -0700 (PDT)
Received: from smtpclient.apple (c-73-96-89-175.hsd1.or.comcast.net. [73.96.89.175]) by smtp.gmail.com with ESMTPSA id j7-20020a170902da8700b001e2a7e90321sm4937735plx.224.2024.04.07.07.00.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Apr 2024 07:00:37 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Neil Anuskiewicz <neil@marmot-tech.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 07 Apr 2024 07:00:26 -0700
Message-Id: <57C20A88-5461-4BA4-9597-1D138B71EF24@marmot-tech.com>
References: <26130.42353.390864.725688@fireball.acr.fi>
Cc: Scott Kitterman <sklist@kitterman.com>, dmarc@ietf.org
In-Reply-To: <26130.42353.390864.725688@fireball.acr.fi>
To: Tero Kivinen <kivinen@iki.fi>
X-Mailer: iPad Mail (21E236)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wkVfyJrVUIfdrOWcTAigPOVix48>
Subject: Re: [dmarc-ietf] DMARCbis WGLC - Issue 141 DMARC and What To Say About SPF -all
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: Sun, 07 Apr 2024 14:00:44 -0000


> On Apr 7, 2024, at 6:54 AM, Tero Kivinen <kivinen@iki.fi> wrote:
> 
> Scott Kitterman writes:
>> I hear you. Your operational issue is my system working as designed.
>> DMARC works on top of SPF, it doesn't change it.
> 
> Yes, DMARC works on top of SPF, and DKIM and provides policy layer. We
> are trying to change the fact that people rely purely on SPF, and try
> to get them moved to use DMARC istead, and we are trying to explain
> that if you do SPF inside the DMARC context, you get exactly same
> policy results you get as when you do SPF before, except you get it
> better, as you have more data available. Using -all would be
> completely ok if everybody would be doing DMARC, but as there are some
> systems which do SPF outside DMARC, and there having -all might
> shortcircuit DMARC out from the equation, we should provide guidance
> to those people how they can get best results in current environment.
> Thus the best current practice should be use to use ~all instead of
> -all if you are trying to use DMARC, and want other systems to
> actually act based on your DMARC policy.
> 
>> Anything like this belongs in an operational guidance document, not in the
>> protocol description.  I have no problem describing the trade offs in an
>> appropriate document, but I don't think this is it.
>> 
> 
I think you’re right the core document should be kept sacred but a DMARCbis pointing to an operational document that discusses the trade offs and perhaps goes so far as to recommend best practices if that seems appropriate.