IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Mon, 25 January 2021 21:22 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 3CB463A18FB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:22: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=KDdvcX0V; dkim=pass (2048-bit key) header.d=taugh.com header.b=l1aV/qC1
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 LjWys-Q0myBX for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:22:27 -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 A36063A18F8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:22:27 -0800 (PST)
Received: (qmail 18734 invoked from network); 25 Jan 2021 21:22:26 -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=492c.600f3692.k2101; bh=1ALZ0kQko0GKe9/6MHU+zqVxyi8tMFj7U4cfo1WTUZs=; b=KDdvcX0VPSGSV7t9NLFi5b9XlSR7WVudPTYD3fRQbCJkpIpQYDoYyGpGQAxLqOf8ioBaANzyi8r7xX9yih0IwDaE3y4HzK8U7VFBhhrNkkdl42uzUypyVA+6ruarZaEmWYdFTFSOsRqDohcborane5yAvDfJ+X+XT5+rl1AIAzVj7F0EZe6R3vv/CEIQejgmhekCFm2Rkejcb3wzNbCLIJx/hIJAq+iVNknCrfO2F4z3fCw3eoifamJrKKRFGFUnbeU1MLn9Z9Wu/8jsNjOUgiobo7e1Sb6OnX5rp7VxAGh7Xg6fpxK2Jtj1+/nRL66RQ3fPkRGJQnNWSXnKiNGhYQ==
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=492c.600f3692.k2101; bh=1ALZ0kQko0GKe9/6MHU+zqVxyi8tMFj7U4cfo1WTUZs=; b=l1aV/qC1b+a//3Hj7D7VqiYAshqNPqD4OSLqvopEBQqojtVwXaA3eWusVMsYSpp5+iCnD+bg0h5K03ZvWI3699yhbOzbvvYCte8Wjgq6PqE1gqW6b12J0DYyen8/uYmNReu0XMxK+2RRExNollqY4lGRO2TFGRgwUvLDaxDEjPCCmvehs+1nle9mUXXwnmJXW7/3uc6yqwhxyAeY1eB1KJFb3ykDiPHHeXwrNYvjwCs7Ars/JTBpLC7UY06xFVJ67sVeTsm8inO1gsIY761RJ3AZDNcS6FGWPOlhEpdzjkhlkC2X4Ntd7jnI6lsJVVJRu63itC4kpTv7kumomG/XGQ==
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 21:22:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 9045B6C14E41; Mon, 25 Jan 2021 16:22:25 -0500 (EST)
Date: Mon, 25 Jan 2021 16:22:25 -0500
Message-Id: <20210125212225.9045B6C14E41@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@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/keug59CMIiQzQQPCEjtvYxmjW0o>
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 21:22:29 -0000

In article <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@tana.it> you write:
>On Mon 25/Jan/2021 21:07:01 +0100 Michael Thomas wrote:
>> 
>> On 1/25/21 11:53 AM, Alessandro Vesely wrote:
>>> 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?
>>>
>> I don't know. That would need to be specified. To me it sounds like a good 
>> reason to not try to specify http especially if there doesn't seem to be any 
>> clear desire for it.
>
>Yes, it needs a spec.  It doesn't seem to be overly difficult.

Sheesh.  That isn't mission creep, it's mission gallop.

If you want a domain identity (even though in this case it provides
nothing useful), what's wrong with a client cert? They exist, they
work, they have software support everywhere.

v2.23.0 | Report a Bug | By Email