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

Michael Thomas <mike@mtcc.com> Thu, 21 January 2021 00:05 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 387593A1610 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level:
X-Spam-Status: No, score=-2.013 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.248, NICE_REPLY_A=-0.262, 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 (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 QnGZPp1wKLqG for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:05:56 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 9CA9A3A144E for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:05:56 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id x20so246864pjh.3 for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:05:56 -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=Heh5qAx4olpX85rrWcalcCS4QhBvqmSK2g7JP7FNFRU=; b=mBK+kjRnz3i5MGE8xYZ0XMjb4D1xFINk0kp0OwdpbIm0NDfgf2iVR/Q6sfnHoz8wLI aKfgP0utZrZJi0UJbXZuH7OZtJ2CDOQtBQwEbpFnz7+5dOWtGSG+0O9cXZhcHY+L7WlR CCCFRL0/HkKfrciRlPO/EavPPDNX5wIvxeNpPxgCthpWW+E2ozq/9vGAYH36p3npOfuo v6Big9/51WeP2dzIMlMou3FtnhkuHcEWKxP753RqPBbNjPSknFpNxIU/Zd1wX3Rwu3uU hRTiFQDUn0JwqKu8+8QGp5Kvfr7FrCnivN9zF7njnxfejjIR3IbuA6/flggGeG6q04kl x1Mw==
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=Heh5qAx4olpX85rrWcalcCS4QhBvqmSK2g7JP7FNFRU=; b=f0dkW1MqON0l62nAOz6bT5o1xieTkekOwjquPYo+D35YFcZRlsHERif/JK+4OlGukq sESY1G0sQQAZy+G0qeLLg1igJ12D5YtkbEXWqQSv8/SwyFvGtxxWHlRr7xDk0womiyXc m18IooNhqnVcwqjLEi6HLgDTeY9jk4er38pTQbxG4Rzwcmtw9espkIbD++RJori7tFAw lsBg48zSsG1b0SAemT5kp21iRmFztv1AWhbeg3Y3923ULOLvco1VyW1IXFOlCrmUeiYU jO9x9KkXEghnUGlNzLAvoqQpP9Z5+Ujnfqo0Lr97jMQ1i3lW+ICoP12aZOFoD8LGCiqO 7C+w==
X-Gm-Message-State: AOAM531sbl7NQs9Dg4NPUtL4GZ3I9IYHDQLsGuOEeoF8sxYBbjcpftVw n2Ad+oHygbcXmJKQYfVnsMSzsKB86hNlnQ==
X-Google-Smtp-Source: ABdhPJz+a+s4dEqx5F6gzohaF2pMdtx2KHj64EQTPqApnIoKxi+1QE40QLAsLxruypejlXFjZB6Wog==
X-Received: by 2002:a17:90a:517:: with SMTP id h23mr8482948pjh.108.1611187555632; Wed, 20 Jan 2021 16:05:55 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id a31sm3368043pgb.93.2021.01.20.16.05.54 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 16:05:55 -0800 (PST)
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com> <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <eb2c5c9e-48a1-76a7-aba7-0bb73eebc765@mtcc.com>
Date: Wed, 20 Jan 2021 16:05:53 -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: <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
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/RH0rU9rDBbQxUTwQwMbeARL9EGY>
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, 21 Jan 2021 00:05:58 -0000

On 1/20/21 3:10 PM, Steven M Jones wrote:
>
> I think we should specify HTTPS URIs, and following 7489 section 12.6
> "Secure Protocols" and current practices, HTTP should not be
> specified/permitted.
>
> However I don't yet see a compelling case for the OR- syntax or a
> separate "ruap" tag. Duplicate reports to the same destination are not
> the base case, and the bandwidth for unintended duplicates will likely
> be much smaller than, say, per-message DNS tree walks being discussed
> elsewhere. Report processors annoyed by receiving duplicates can work
> with the domain owners in question, and if that doesn't work they can
> withdraw their report authorization record.

See this before spending too much time. It's probably better to just 
junk this enhancement.

https://trac.ietf.org/trac/dmarc/ticket/99

Mike