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

John R Levine <johnl@taugh.com> Thu, 03 December 2020 17:08 UTC

Return-Path: <johnl@taugh.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 E84EC3A0930 for <dmarc@ietfa.amsl.com>; Thu, 3 Dec 2020 09:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=bflQ/To+; dkim=pass (2048-bit key) header.d=taugh.com header.b=KSi+n202
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 T8tiHXaM2_zh for <dmarc@ietfa.amsl.com>; Thu, 3 Dec 2020 09:08:53 -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 DBEEC3A091B for <dmarc@ietf.org>; Thu, 3 Dec 2020 09:08:52 -0800 (PST)
Received: (qmail 32437 invoked from network); 3 Dec 2020 17:08:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=7eb3.5fc91ba3.k2012; i=johnl-iecc.com@submit.iecc.com; bh=7/39eEJHegg2+YG5gXi5ZLaAobSej4fgelAEblJXc1g=; b=bflQ/To+A17D05zU45iq+5V0GGUIyPb8drnp/hBvH0eAcp/WytcE8GiBcx1+IpesNlisWiNVCFHmPazzf0IXM6mcSCOxsgYTJwmYK3wn8DiCLZKwULlVhEZn3zL2OINX20ralswY2yp/LATK0/ZAbB5nkZjDwSnLjM9fS8Kk5fQ1LIbmLcBp/HRCnM5sxPCXT7XVrMkN9I4GqKl0bzmWhsveoKT5tjF1a7E6sLT2wLaUlAmwv+mc0yW0nXinN2nIDkzMoCsM8NY65O+9evFRxRVkwUMm4B8B4M8NVIrHCVV9cWxfP/5xid5XBy2P6+7Z/Lqmpf2mi5BTZ/t0RbRLNA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=7eb3.5fc91ba3.k2012; olt=johnl-iecc.com@submit.iecc.com; bh=7/39eEJHegg2+YG5gXi5ZLaAobSej4fgelAEblJXc1g=; b=KSi+n202Zl4JGj1oabSWfQcB2RQ+e1/EzS2X6QOgEVkZDbp5gizd0g+b/8113ClXpHClqhHBlSFzPMc4P9/vm+5/thn7qIDscc0ocRj35tbCGd85pw0mPIP/2ykg/QCGwYLoq/SQcZRy71GBOO0YXvoU4/FoBbi5MA4xn0mblslwLAaXPpx2tVhI5g4PpzTpOXRhTBPDu9foFh1xO/IFLurbd6T/3mZS7Fp8bShiE6luSVRcLmBLPcvyrL4zXh+H1dhIy5xwpAwe9TAlfr0rQne/SdCyz0YyA3/2ymDluAY7RZm7QRA/Gb3NFuNrceas5PS/IirJlfpSvFs6vyK+Wg==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 03 Dec 2020 17:08:50 -0000
Date: 3 Dec 2020 12:08:50 -0500
Message-ID: <479cfb50-b98e-fbbe-e7ce-375557cd624@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <f719b86d-9a7d-f865-3e16-10eaf35e0de0@tana.it>
References: <20201202233432.D45FB28E1943@ary.qy> <f719b86d-9a7d-f865-3e16-10eaf35e0de0@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/m8laJkWW-s7PEK1c93u_j1UJpBs>
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: Thu, 03 Dec 2020 17:08:55 -0000

>> When this came up before someone said that reports can be extremely
>> large, many megabytes.  An HTTP POST or PUT is a much better way to send 
>> that.
>
> However faster, an https PUT/POST at midnight arrives later than a mailto at 
> midday.

I'm sorry but this makes no sense at all.  Why do you believe that people 
would not send reports by mail and by https at the same time?

> Yes, PUT is better than POST.
>
> How about pgp-signing the file with the dkim key?

Sorry, that doesn't make any sense either.  DKIM keys and PGP keys are 
different.  It is hypothetically possible to sign an http transaction with 
DKIM but that would be a giant distraction from what we're doing here.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly