Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality

John Levine <johnl@taugh.com> Mon, 25 January 2021 20:44 UTC

Return-Path: <johnl@iecc.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 1BF953A18A7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level:
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=QXXC9E6B; dkim=pass (2048-bit key) header.d=taugh.com header.b=xoPWaudG
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 OmCAI2tc-Sy6 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:44:26 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7524A3A189B for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:44:26 -0800 (PST)
Received: (qmail 8322 invoked from network); 25 Jan 2021 20:44:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2080.600f2da8.k2101; bh=Os+vkJmFwu5Eg7q0XPHOdEw46LLgBKWpQafjv7/pbVo=; b=QXXC9E6BngK2fwU0QPvt1ydLRQlUTxN8y7hEQ48CjkAG0mdBpXONWRYF+ww4wP5SitczXQRgJ3XRHK4jnXb/k6aKdllX2ggSWxoXoPvabcqs10cnCp/0vtxiB/bjnuDb8LjaMNI05Z9z2dvByS12b85I9wWLKb4xfT3wa2VkVuMC4rqd9umytUK98ScdZy6TyhtJgipfwBsXMfcpPIoWSCGsdEamtO9mVshW13aOMZUpPrazpfpOCdKdgwcpCeGDzZtuKwWBiakXbjAlkxPTTWhmu5EjPSKCYwwlzO19UIRjkmbHgimL+cw5kaaKruwbej7ACw+VQT4xPkeygj4Aww==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2080.600f2da8.k2101; bh=Os+vkJmFwu5Eg7q0XPHOdEw46LLgBKWpQafjv7/pbVo=; b=xoPWaudGU7OpA2UUkcZ0TWDlq8jgzTarF46+RE/5AHyTVJ+tAUr4J145sepnynmlnfmKrygu/jGTzl2YwtCyto/BNyXg5oJywsNNLbUCfHtQZn8GV1nYqnewxGmpiVEEtWrjRi064NrHbPEhoueSSqUCwQ9cMY2wMFA807gyW7RBc5E+An6iN6eO+YrFLlGXFssr3sMevxJbwNcgMaTfals3CpTtJ/7ZkblffdMe1aFXM/ND56J+J1ivjZqyrWMifYw0L/aIFC79w9s0AHy5rLL+vITqEv816pUQ2/NJPQoBT7eGO71F37sCpoWD72VSc2UQHr2q0NMUGvU8TTjU8Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 20:44:24 -0000
Received: by ary.qy (Postfix, from userid 501) id 9FE546C14371; Mon, 25 Jan 2021 15:44:22 -0500 (EST)
Date: 25 Jan 2021 15:44:22 -0500
Message-Id: <20210125204423.9FE546C14371@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/U1OjMDB5fB24OO7k65MzQoJIO2o>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 20:44:29 -0000

In article <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it> you write:
>On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>> issue #99 needs to be addressed.
>
>Won't we put a DKIM-Signature: in the http: header?

No, there's no spec for signing an http transaction.

If you want a client domain identity, It's easy enough to permit a
client SSL certificate, but as I have pointed out a few times, since
there are no recipient domains in an aggregate report, they don't
provide anything useful to link to.

R's,
John