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

Michael Thomas <mike@mtcc.com> Sun, 24 January 2021 18:49 UTC

Return-Path: <mike@fresheez.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 B90833A0F46 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level:
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 5t6fjMZKYUI7 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480513A0F35 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id n7so7442816pgg.2 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=KLNBN0VOaRSegwn9LZf56RfUd3xqLOg5k5eajIH8NsQ=; b=kbtO9dN1imR2ArqaUc2eLHnMX10lbBDX4472aDUeVWOZIVjpLsueqL0YxyVWUPUCFv sC4gw4eXbDvkkdmVOV3gEPMUivazrfo19MpP2TjAwBYFzOC23/yLKlKH1C++WGENraWh Jnlft+zVibZC3XrQV82wFfGon1dW1+OXJtB7zPGZNZW+aLy7M/EEMDQ5WvVllVA4jVsm ZVqYTtJqp4lB1S+IQO0WjrMLezIFrF1xZuot33pzfFFqPH3nQ0ruWvy3o0w1yLXwtjYZ z6MGnyW5fHr6PmxexPHtj1vBBM6xZuw/hivxAtBvt4TXA9kaLjp5dnK2XDOlVbh7BuZI KeNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=KLNBN0VOaRSegwn9LZf56RfUd3xqLOg5k5eajIH8NsQ=; b=LNYBNCORQ6vX8QgBXKxtW0XwOUAD7MdX1riBk6tciLVwvpvWeDNSM77+4Y1NR/x0oT xgU/1CAVftblgrYLT8pEU7b0NMKKXDcPn88h0tsFbHzrGcvKqaJMOXmnBFuE7/zA4hBq /FPG5Kf9GRvQUJ36n5LMvdVMmATbgaaLHuzHY+L7FBQ1BpV0gSGAM8/C6vnfxIvNLhnM xR0Mt1ocwzBm8hj3cFupjgiA1cuYrEP2sHhKIThsJuOB6B5cWkZ+95dtCvrxjxUpoPle LlV+35jrQX8TTVZShA19uyHUq05nRi8L1VkarboZn4psO1OBD2ifaYq60Azoaw6Ob68x 7spA==
X-Gm-Message-State: AOAM530cs3Nm/2BuAGHikbC91umLJv9RxiQIMs9bJbofHXW+FHcfgSpt bFIkno8vQc54kHb2hnr2JMe3oHvDL17IlQ==
X-Google-Smtp-Source: ABdhPJzogoCCIgqvUA4chLBN4uLcGPhp5IIzcxBiPAIgsYcXrQbr1QRW+SWqFlggh5sBPS4wM25uqg==
X-Received: by 2002:a63:4517:: with SMTP id s23mr1470346pga.267.1611514176330; Sun, 24 Jan 2021 10:49:36 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 6sm16713820pjm.31.2021.01.24.10.49.35 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 10:49:35 -0800 (PST)
To: dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com>
Date: Sun, 24 Jan 2021 10:49:34 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124184659.12DF46C068F5@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wWiUnSweo5RXd8TMfr3cgvvTYAY>
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 18:49:39 -0000

issue #99 needs to be addressed.

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