[dmarc-ietf] Static allowlisting

Alessandro Vesely <vesely@tana.it> Mon, 24 August 2026 16:48 UTC

Return-Path: <vesely@tana.it>
X-Original-To: dmarc@mail2.ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0DDB312E7EC13 for <dmarc@mail2.ietf.org>; Mon, 24 Aug 2026 09:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787590138; bh=rTB2soxTXxv5t0tar3Fj6F4G4aW0PZGOp29dheBqIAQ=; h=Date:From:To:Subject; b=CzO68L4mD9ZWGk3dhWmTigAkY/eIaowL11IsDeoi4msygcqOGkB93CcKwpQAsd6fY 6LYAfu3TOra/uZ8D+gxzZowrLSGnzQ4a0YkVI01IjqU5jYZcTdtgIiL2S3wCjyfWzO fFXdU6CQR3oNSphTC43aB+LBwzSzxoY9K3U2k+Lg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52qYa7_2BOPn for <dmarc@mail2.ietf.org>; Mon, 24 Aug 2026 09:48:56 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 43A0E12E7EC0E for <dmarc@ietf.org>; Mon, 24 Aug 2026 09:48:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1787590127; bh=r8E90c3n3WYZIjgi04Ix7gO+Y9Ujy9rnpPhiGnCP10c=; h=Date:From:To:Subject; b=CNF9u466nKQtO4i1RyqjjPfIdzf/17Zx1lsjyhlYrjSziyNw3KgqtbmYHZIgVD6+E miySfB7a5g5X3ykTleECi9U/HC529VyuI7BII644b2dOquJKg6Ael6Fn3afuX9dSAo JafFsww9Gv1QQ3YZot9s1YNOcLZzUPzPISQOtnNZPizJ+NA1XEo/SaV5+4fb2
Original-Subject: Static allowlisting
Author: Alessandro Vesely <vesely@tana.it>
Received: from [192.168.1.176] (host-82-90-216-49.business.telecomitalia.it [::ffff:82.90.216.49]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3,128bits,ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0EB.000000006A8C75EF.00005FA1; Mon, 24 Aug 2026 18:48:47 +0200
Message-ID: <d55ab849-aa3f-4111-ac05-3fbaf533bf42@tana.it>
Date: Mon, 24 Aug 2026 18:48:46 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US, it
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: RQIBMPDZVHWLR3XZ6DFZSVJDXIM2FRP7
X-Message-ID-Hash: RQIBMPDZVHWLR3XZ6DFZSVJDXIM2FRP7
X-MailFrom: vesely@tana.it
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Static allowlisting
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PFqY6Ub2yS00O2Xcgi9XE4hRYkA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>

For the third bullet in Section 3.1, we have:

    *  Limited reputation deployment:Even early deployers that validated
       ARC chains did not deploy robust, dynamic reputation.  Instead,
       they implemented “allow lists” of intermediaries whose ARC
       assertions were always (or mostly) accepted.  This provided
       utility in specific bilateral or consortium relationships but did
       not scale to the open Internet.

Again, this does not specify that the allowlisted domain has to remain 
at or above the oldest-pass value.  Trusting assertions that precede 
modifications by third parties can be dangerous —an obvious but often 
overlooked point.

This use case is presented negatively, although it sounds like a 
legitimate and useful allowlisting method.  If static allowlisting is to 
be criticized, the criteria for dynamic allowlisting should be made 
explicit.


Best
Ale
--