Re: [dmarc-ietf] DMARCbis issue: Reporting URIs
"John Levine" <johnl@taugh.com> Tue, 28 May 2019 02:50 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 6723F120116 for <dmarc@ietfa.amsl.com>; Mon, 27 May 2019 19:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=HfdB5OE4; dkim=pass (1536-bit key) header.d=taugh.com header.b=hq5TGfze
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 X4FBSWdG2WvW for <dmarc@ietfa.amsl.com>; Mon, 27 May 2019 19:50:41 -0700 (PDT)
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 6CD84120147 for <dmarc@ietf.org>; Mon, 27 May 2019 19:50:41 -0700 (PDT)
Received: (qmail 63702 invoked from network); 28 May 2019 02:50:39 -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; s=f8d4.5ceca1ff.k1905; i=johnl-iecc.com@submit.iecc.com; bh=NDAxK1n0iOSZBrX8XwMtqzXrpNjnKYwo7vVYoLjaxLk=; b=HfdB5OE4t/xH5HoCkgzzeerqU0IhHBMpFu6gmc8GaC7rPTr9amcUEk2zyk0fFXgb0V7D+ugRo0RSgwmbDmTT9K8X2C4UiyFi/QqVsNJr84a8eK1GzE9VdDf2UbymNJT3PY1ZBh0oL+iPmeB5/GE1B+0vjbGuDTMrZoY2w/XocGA238wwSAEgzu4QRS2Qwc+a/GbOuroWmPN3YFnbmfrS0Cz7e8J0pzf+kTU9rR2QZaijsC1+lVSFu2p2gMQ1KBea
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; s=f8d4.5ceca1ff.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=NDAxK1n0iOSZBrX8XwMtqzXrpNjnKYwo7vVYoLjaxLk=; b=hq5TGfzeJeb0UASUz9dXv8Q5dC13UYyDlHvw/pgABD1M2QIT4napcbr4kZfE6TZ41miN8xgmLNDgcCjaUSotBaDikv95kVDTfBlgjoeyxdLw5e2+KqL4rY63bInBQ+uSk5881jMudvyseP6l/U6X1kIyPeHEB6tf5tcABkTnMxAGV7LjiW21YKkpvc9uR3+h+roHmm2z9DibLsjD9syIYuts7Ps0tZh1i+ugbST/S3rgViRvV7+yC0Eui0lxkEES
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 28 May 2019 02:50:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 0D5272014B0A62; Mon, 27 May 2019 22:50:38 -0400 (EDT)
Date: Mon, 27 May 2019 22:50:38 -0400
Message-Id: <20190528025039.0D5272014B0A62@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: cloos@jhcloos.com
In-Reply-To: <m3y32r5vpd.fsf@carbon.jhcloos.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3HaVm_fJFNqT_nr6wzF5H44UkDA>
Subject: Re: [dmarc-ietf] DMARCbis issue: Reporting URIs
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: Tue, 28 May 2019 02:50:53 -0000
In article <m3y32r5vpd.fsf@carbon.jhcloos.org> you write: >>>>>> "JL" == John Levine <johnl@taugh.com> writes: > >JL> implement it. If people are interested in an https PUT scheme it >JL> would be easy enough to define one, > >I find that the http POST scheme for TLSRPT works very well. It looks straightforward enough. Do people actually use it?
- [dmarc-ietf] DMARCbis issue: Reporting URIs John Levine
- Re: [dmarc-ietf] DMARCbis issue: Reporting URIs James Cloos
- Re: [dmarc-ietf] DMARCbis issue: Reporting URIs John Levine
- Re: [dmarc-ietf] DMARCbis issue: Reporting URIs James Cloos
- Re: [dmarc-ietf] DMARCbis issue: Reporting URIs Tim Draegen
- Re: [dmarc-ietf] DMARCbis issue: Reporting URIs Tomki