[dmarc-ietf] Reporting DMARC policy in A-R header fields

Scott Kitterman <sklist@kitterman.com> Mon, 29 July 2019 19:37 UTC

Return-Path: <sklist@kitterman.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 912B812002E for <dmarc@ietfa.amsl.com>; Mon, 29 Jul 2019 12:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=XE5kflf9; dkim=pass (2048-bit key) header.d=kitterman.com header.b=B7+DdLvi
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 8H5Pd_y9esDt for <dmarc@ietfa.amsl.com>; Mon, 29 Jul 2019 12:37:57 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B808120025 for <dmarc@ietf.org>; Mon, 29 Jul 2019 12:37:57 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 2AACFF806F7 for <dmarc@ietf.org>; Mon, 29 Jul 2019 15:37:56 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1564429076; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=kqi2AhMn6F2lQAErhOZ3Jd87XhlE2AKz0HpnqrH8Fx0=; b=XE5kflf91WkJ8Mn8B1tPUQaA/SmZi6VYP8gqL0MZbLabGbaDm5hZlJB6 zmjlo03twFNAkJqkkQeI0b60YZzbDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1564429076; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=kqi2AhMn6F2lQAErhOZ3Jd87XhlE2AKz0HpnqrH8Fx0=; b=B7+DdLviKfBUjKC/2Zm9SMCBslJAUzAQNslyvPzY6DxaMHnbIpBEeL33 KlRJeZ+I8HCwHLwzKyzAnldTzy1qjXDYzNUsaVYGkFGRCLViXEOMCsaAbY 0LZ/0n4A1u9Hy40ScTxI3KUFXh2pFjxjtTEvI9PHbwpTdcUIEG0EDAl+Fb CpgMZUE6G128oLIlNEUKBfN/QfPJIqVncTwiR19O1MT9o2w8D8HUauUnu2 2hKikQ7Z34Lu0jlUrUP/db16VY051DyGv3yIeYn+JtWhmDiTCTxJxsgNgx 5Jikd+o7JO36tXHJy9d5qUY4PWsXzQwqRWrUccOxQ5K4cHB9tTYl5Q==
Received: from l5580.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id F147EF80096 for <dmarc@ietf.org>; Mon, 29 Jul 2019 15:37:55 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Mon, 29 Jul 2019 15:37:55 -0400
Message-ID: <2577720.3ZthdXZjm2@l5580>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TheTKnctHTqMO8xhwH7vyK5ujsU>
Subject: [dmarc-ietf] Reporting DMARC policy in A-R header fields
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: Mon, 29 Jul 2019 19:38:00 -0000

I'd like to add the option to record DMARC results in an A-R header field for 
consumption by a downstream processor.  I think it would be something like 
this:

Authentication-Results: mail-router.example.net; dmarc=pass 
header.from=example.com policy.dmarc=none

That would take adding an entry in the Email Authentication Methods registry 
for:

method: dmarc
ptype: policy
value: dmarc

Does that make sense as a way to do it?  Does anyone have alternative 
suggestions?

Scott K