Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports

Michael Thomas <mike@mtcc.com> Tue, 22 December 2020 19:41 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 EA4673A1250 for <dmarc@ietfa.amsl.com>; Tue, 22 Dec 2020 11:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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.25, 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 klLKZDrSUJse for <dmarc@ietfa.amsl.com>; Tue, 22 Dec 2020 11:41:10 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 1577C3A124E for <dmarc@ietf.org>; Tue, 22 Dec 2020 11:41:09 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id b8so7959513plx.0 for <dmarc@ietf.org>; Tue, 22 Dec 2020 11:41:09 -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=zUOeAH47I0sGbAbnKr45P7upKUaY23WZNy1jXAnLFcQ=; b=QL1Z/+Eq9FuSXm8NoXSrS5Y9CkB44BzZobQtoqVo/RZ1/mUABV4+A89tT6KNk1NWuq qruVmk21P0J6kayxO5DwFI2t7daAh48Eh6W/snRsiNvLA8yhNq0rgBn4azArtsPMGk3a BV9S0Ll3H1UcR8jEpaFVzZCZZDCASKw3P9buo6d4vser0CaB/a+RaIH2fMM+4q5EUVnn CKPS0zfUhzREjjsY7dZkQW6lXrgK397ebrhuQdDKzNSI1opyQYU4tuxO22nV1FjQEcDA W75O60wyTyK5bVzqIYxd1l/qwu5dOs9VTvcrx0t8rOnmbkStYgphXfyBNMOosnWY2OAQ sXLQ==
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=zUOeAH47I0sGbAbnKr45P7upKUaY23WZNy1jXAnLFcQ=; b=nP0GzEV0Jx1cn4DbZ4WYc/1LU6kdMsCuDBoWpdhJUCK30YWryrLZbnT31bTLRWxT5/ aP5JcFUsld+bELopOg/xMQqxu0lGip311L1dtqFofAocLe5duIz5m0C3n6+6LLyDqpbK IVqBXoXUfJBpMl3fZmmGWELXOWjpPJ/tKSLfD7ObQl+5jl8TkNjT9bk3YuwwF5u8zKTZ lO/KrYpD8/MQrM+NKaO3EPgZZwWCqp4eELxqeq2w3O18303hn7PjowApyLBJviS55azJ Dph+U16Pz3fS/eqQGTb+u3heaCFMuvWWPSaRoLQCibwn0g8oohkqkd48H2rB5WROWMO4 cwPw==
X-Gm-Message-State: AOAM533G2Dt8nve8sU5MqomciJW0SGI8uy87B8TUR8RjnNRnpnLaty9m ub/I/aqF8z+t3kQZHdp5Oh24+TRcZckknQ==
X-Google-Smtp-Source: ABdhPJx/AaIIQMo/HoyS4q1nBKL6ROV8tcPfgFWbKfmwAiqBORWuyrUV5MMJRSUrnQfBkwLjCaCbyw==
X-Received: by 2002:a17:90a:e28a:: with SMTP id d10mr22782902pjz.77.1608666068551; Tue, 22 Dec 2020 11:41:08 -0800 (PST)
Received: from mike-mac.lan ([107.182.37.0]) by smtp.gmail.com with ESMTPSA id k64sm21840437pfd.75.2020.12.22.11.41.07 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Dec 2020 11:41:07 -0800 (PST)
To: dmarc@ietf.org
References: <20201218023900.E73B82ACBB2B@ary.qy> <4a43ffaa-3987-c892-cce7-56f18888cdf5@tana.it> <39125012-e356-d62d-36fd-a7ff25a9f59f@taugh.com> <e6880ba9-f5f3-1050-25c0-658551187512@tana.it> <6bba023-d3d9-63a5-8441-11dac9a05e28@taugh.com> <74051a64-871a-db72-b5d9-1be374e23015@tana.it> <a323077-9b64-555b-3561-62cdc93819fd@taugh.com> <a8281e16-9417-5189-df73-79ea0a865fbd@tana.it> <c713b9ae-a364-1ae0-e79-55f61624aa3d@taugh.com> <3034face-b6fc-0ce2-fa1b-f59210bd6f5b@tana.it> <46339b38-3b24-bcb7-5e73-8a97038ed69@taugh.com> <3997c81d-3b30-0823-a752-fb1d60a44593@tana.it> <448eeae1-2d82-91d3-4adf-cb547acd427a@mtcc.com> <c929bfa4-9b32-5099-01fa-078c56191571@tana.it> <0bf9fb2e-9974-4db3-3165-78508de3547c@mtcc.com> <44d92626-a13c-64e7-b1de-07cd50b1fd20@tana.it>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <fff265af-16c0-9d75-c92f-ee438ae088b5@mtcc.com>
Date: Tue, 22 Dec 2020 11:41:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <44d92626-a13c-64e7-b1de-07cd50b1fd20@tana.it>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YvfhD10pW3Z9B-P3QlQqYM1qyi0>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 22 Dec 2020 19:41:12 -0000

On 12/22/20 10:59 AM, Alessandro Vesely wrote:
>
>> Sorry, having to ask for permission because of laws does not 
>> constitute a "severe privacy concern".
>
>
> Except in the sense that they're called privacy laws.  Do you have a 
> better wording?


I don't know what was wrong with the initial text. But it most certainly 
is not a "severe privacy concern", especially if it is the originating 
domain getting the report. It already saw the original message in the 
first place assuming it wasn't spoofed, and if it was spoofed they are 
entitled to see it for forensics if the receiving domain is willing to 
send it to them.


>> That is completely outside of the scope of IETF and we should be 
>> pandering
>> to it.
>
> Making specifications that cannot be legally abided by is in IETF scope?
>
If the laws are unreasonable? Sure. We're not putting backdoors in for 
encryption either. It's their laws, let them figure it out.

But you said that providers can get people to opt in, so that seem moot.

Mike