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

John Levine <johnl@taugh.com> Sun, 24 January 2021 19:08 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 A9A283A0FF0 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:08: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=X63fzQdr; dkim=pass (2048-bit key) header.d=taugh.com header.b=P8nggnld
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 9hTBt-Io5CNc for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:08:28 -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 EAEB93A0FEF for <dmarc@ietf.org>; Sun, 24 Jan 2021 11:08:27 -0800 (PST)
Received: (qmail 51106 invoked from network); 24 Jan 2021 19:08:27 -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=c79d.600dc5ab.k2101; bh=F2jJ3GjX4O7a4Ms7aFZfMjjWs527i0Gas8F3jbycjSk=; b=X63fzQdr4kNgmOxJ45yrK5pkbeIRCRJ74LVNW2OJtl7bf1ZNWCaf1HXa3ON4fxlp8mSCHOnTQy74TDYeT/mHrRE9DNJAjvQUnvpjLCI2B0rCn2BCQpkouDCqwZpcrqSGr1TU4k1PhQ4zPze7zbLycl9G0dA7JssP0i9diRkjk46rHJcnEgi7Ni1R+bZPmXy21m58VTRePs4l6DN4zpVSUSBVIgqlV7zhId9gzXpqoCgXc53cdp+/f9Ib5Xfhnwbj9UYdlFU3UoipO9WKzpbOioySwVOVt6hYqyUmk9eTcPc44guCEY7O8w/vbkp59GZMlllTzQqbbQNeTV+b/CGuVg==
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=c79d.600dc5ab.k2101; bh=F2jJ3GjX4O7a4Ms7aFZfMjjWs527i0Gas8F3jbycjSk=; b=P8nggnldmbZ2khCX2wnTtrP/exxiQwksjUT3WJ0E9rIvFtQVT4OzfifSO/sxXPsN5ZUEfN87TZEZkBDIVcUO2fEEi6peUX6AbP1ZF9R3ijyjyRHLrcqY//Ns1sVHcFKsydscoaZVYMnfK6A4eggqEymUEG2t+1Q0ZeRiQW4RjdMMlX3/847sw6ISXFO+4N9dJx3wEy/gXgJUAMyLh0zvn5mTzzjU8yuE+zAyGyLtTsfXu+4zsjNEzjMH4VUlx5SS0OYbOfXBxwyJYYoxPHiuyBBdicrjRAjJY0zbB2Flc8pf+SKMYASOG/goPI9Rf0R5nQeLgtGoPOdc4sjNRnMQdQ==
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; 24 Jan 2021 19:08:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 380E26C07CF4; Sun, 24 Jan 2021 14:08:25 -0500 (EST)
Date: 24 Jan 2021 14:08:25 -0500
Message-Id: <20210124190826.380E26C07CF4@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com>
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/DPniKp2QBtTKmDnzEpamiWT7Srg>
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: Sun, 24 Jan 2021 19:08:30 -0000

In article <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com> you write:
>issue #99 needs to be addressed.

I don't see any connection between issue 99 and this proposal.  This is not about failure reports.

R's,
John

>On 1/24/21 10:46 AM, John Levine wrote:
>> Here's a concrete proposal for https reporting:
>>
>> In draft-ietf-dmarc-aggregate-reporting, in the transport section,
>> between Email and Other Methods add:
>>
>> Https POST
>>
>> The message is an XML file with GZIP compression, sent with an https POST message
>> to the given URI as media type application/gzip.
>> The data SHOULD contain the filename described in Email transport
>> above as the filename in the gzip header. The filename helps recipient
>> hosts recognize duplicate reports.
>>
>> In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:
>>
>> If there is more than one URI in the value, the URIs are conceptually evaluated from
>> left to right and each report is delivered to each URI in turn.
>> If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
>> This allows a report recipient to prefer https reports while falling back to mailto reports.
>>
>> R's,
>> John
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>