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

Michael Thomas <mike@mtcc.com> Wed, 06 January 2021 15:26 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 633A03A0EA4 for <dmarc@ietfa.amsl.com>; Wed, 6 Jan 2021 07:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
X-Spam-Status: No, score=-2.012 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, HTML_MESSAGE=0.001, 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 dZuDTWpo9jn9 for <dmarc@ietfa.amsl.com>; Wed, 6 Jan 2021 07:26:27 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 2FB7F3A0E9E for <dmarc@ietf.org>; Wed, 6 Jan 2021 07:26:27 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id b5so1764267pjl.0 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:26:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=DOP/8ksz7W4Xp80xeyfrwFuEr442wcAj71lyXzQqUWE=; b=abcm7cLT59M///UOM4MW3K2WWKsKSl1jVBvTaTk88OLt6M9S95dJLJsZf879L3sJNs 6oVjBV6xwn7uyeURz4eQZ/pxWkYD/q2WYJmysZ/uPOvb4cJyDS8h8WxzGKtV+Gfmwg+A Pe2lUb3lx2xb3MUbMjuN7mbEUfFb7/6mwthWTDrnsgEB3oKBduOv9dOWff4NpJTKl7H/ 7DHM2gyjd78bRdgrdyIPRmGNQQIFP1A2ek08PNZic/Y4pGUYCgSzP1C4J4W9jciT9R1g 2GP5hj7Np2L3h0EgbVggDbdti3WvPYpN7nf1TJneqcj+TJ4NO1RzoVE3rIqMJfOPgoMD X+MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=DOP/8ksz7W4Xp80xeyfrwFuEr442wcAj71lyXzQqUWE=; b=QlaXPDA4/dPU3Gkkrn9fJaHSiMGOS+L7pmDTsYvzsY3yLxH9atrv27gSOPQXEla9m9 B1pz+wrcS+5h/Xmb+T7Xd5XgRFcxmNYGDk9N2FlWvrNznrDGY0TQfvSBaX7xmdQbUR1x TYo/IetCgJbY8NrV3bgBBCmJTozXWo7q2DIm0Pn3ynzHJf/S/NQFRlPfPbECLZPsWyd5 5AWo+KQ6mTq36JEXtoOYN7hN/QFYSyaOfCl+mTIrBMsYiFD1xHCjUa+SccWYtg9YosYI my7JWRjfKxB93qSICnaSiZiFbac0xb3rGmkXNyMQXBDNa2XNfhXJdZ+YNj+S3bNt8NcJ 4FgA==
X-Gm-Message-State: AOAM531vVmukOEBcZiTAGjlZ1KcY25aGAVjEiDs/bM+qkA2jWWbmpq7B wQTSM77UVMcRC/qf0ovGZFzVsSb4mn0NLg54
X-Google-Smtp-Source: ABdhPJxW7MW63ozfdsZEiIdu07ETO2TnOmR57xhDjuvjfMmmBvnJUyYtAYgpzYrmgIdiJDTBdR05sQ==
X-Received: by 2002:a17:902:7793:b029:da:d44d:1968 with SMTP id o19-20020a1709027793b02900dad44d1968mr4905179pll.47.1609946786043; Wed, 06 Jan 2021 07:26:26 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id ev23sm2636156pjb.24.2021.01.06.07.26.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:26:25 -0800 (PST)
To: Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com> <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <da2077f6-8a97-2ea8-bb2f-2a10cb8582e9@mtcc.com>
Date: Wed, 06 Jan 2021 07:26:23 -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: <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A30A3CBDDF55138EFE3C4B45"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4GJLIUkD_0BnloRRzM6z-Zp7boo>
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: Wed, 06 Jan 2021 15:26:28 -0000

On 1/6/21 7:17 AM, Dotzero wrote:You are literally telling me what I 
knew at the time. It was a lot of the reason that we got push back to 
form the DKIM working group. It wasn't until I read that paper that I 
got some concrete feel for how it affected things, and that was 16 years 
later. The biggest change for the better was senders closing open 
relays. It's still not clear that DKIM had any affect on that.
>
>     Mike
>
>
> No, you are literally telling everyone else how things were. In fact, 
> there was a lot of data. You are the one who claimed that everything 
> was in your head and the rest of us have no clue. - "DKIM itself was a 
> leap of faith" and that we were doing things based on opinion and 
> conjecture. It did not take 16 years for there to be data. There was 
> data before DK and IIM were merged to form DKIM.
>
What data? Data that showed what? That's completely news to me. You 
weren't even part of the informal group who caused DKIM to be created, iirc.

Mike