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

Michael Thomas <mike@mtcc.com> Mon, 28 December 2020 18:17 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 CAE343A0CDC for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:17:38 -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 fqqFLg2HsNJu for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:17:37 -0800 (PST)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 334C83A0CDB for <dmarc@ietf.org>; Mon, 28 Dec 2020 10:17:36 -0800 (PST)
Received: by mail-pj1-x102d.google.com with SMTP id lj6so67466pjb.0 for <dmarc@ietf.org>; Mon, 28 Dec 2020 10:17:36 -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=K0txgQpvhy62lE5kccCA6bDldCK5LYB45jaSnuZYvBg=; b=Xesu1xMj5NiVxEgPyV9ihoCOullGxpsCratS5/MQueyaSZ0WmHdjtmBz6alnZj5kBa tL4CVUQ3S0EkPwi60ZLbl5nYrpKrYZyA3D31KBozhJ8FezywAteCpJmsYDlPE9NxidX1 xDQklIUBKSzSoOuKyyje7pqW7jdMPskoZZU9YTbbfF/XlqAhT/4EHDGAt1pdt9NSnUwM F1jHSPhqCCFWW6zuaaIi0Uq+hZu2B1Acq6eDMMM7PB2gvaK6omwWi1EF9k66MbKsQNwP pL8j/aK8J3R05sapCDh9aiZ7sIBdLNLQ+Isg3iRg1vljNsW3Ci32LAmo63YGLW+CG5Vu U/ow==
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=K0txgQpvhy62lE5kccCA6bDldCK5LYB45jaSnuZYvBg=; b=g2OgJkc3uliCJf5xq53pxsApN3rVaCfCtHt7b7KiJ39e9wC9D6kOveW8ZNhyaIkVzT DQBLQOEGYIOsZ7MS1C5GVvTRh1KzJ5YHHbXwASaK0aZw1FHvglFcAGkEdcO4gcWw7ltS DFBJHiqC62mw9Lm269eqW/WSaku6W2kT4ibjXHlZqKyBEFw1MJQq485sHHE7f+NohRuL GxHM1XRhRu17JHWnWSSgswF5fF4TjgKT2T5Lv4HbgNvkIfmp72EhkQvmuYfV8WRs404i 57cdujhpWtXpoV2yrLH6A1kCsvxWVqdQylFB90li5uEGoEuOLxodDQpsJX1u6K3pwWQT I+rw==
X-Gm-Message-State: AOAM532JCS4slgWVxfpj6ixjkzPntmV8BHv+XouBxVHu4Z0ukjouOoUz Kn6aGw7gT+dds+e6ZGjNGdV91uH4zHgi1Q==
X-Google-Smtp-Source: ABdhPJy4cMYqI3nIf7CEkCVSdwc993KXxg6fLVu5hkBSVQt0b3+KliqPwrucl5y6CAXMgMb9a+3EQQ==
X-Received: by 2002:a17:90a:6a48:: with SMTP id d8mr135830pjm.130.1609179456201; Mon, 28 Dec 2020 10:17:36 -0800 (PST)
Received: from mike-mac.lan ([107.182.37.0]) by smtp.gmail.com with ESMTPSA id na6sm75436pjb.12.2020.12.28.10.17.35 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Dec 2020 10:17:35 -0800 (PST)
To: dmarc@ietf.org
References: <20201218023900.E73B82ACBB2B@ary.qy> <74a5c37-19a6-6f6f-a51d-6e5cca5b29e8@taugh.com> <CAJ4XoYdXWTgADpdL1eJuYGnpSY038vj-FW_x1f2rEp1JL0r2oA@mail.gmail.com> <01RTICXKLL3E0085YQ@mauve.mrochek.com> <c5f7413e-52c1-6710-16e5-63f59d2c24b9@taugh.com> <CAL0qLwYDeV9CmFg9qCCGPse00JV30WRiSC4orC-EitK=hiahgA@mail.gmail.com> <a79dd75-4d73-d1dc-d6b1-272de866b950@taugh.com> <CAL0qLwZXu3FxH7QGBS7PGbeDwfDTGmC=rbPEQidVV4eDJNHLUA@mail.gmail.com> <CAJ4XoYeK2cJb+easc=mqCi4ap1932LmbDdfxM1dFZKrdo2a2mw@mail.gmail.com> <acfe3d9e-97eb-50ee-26a2-568fdd8359dd@taugh.com> <CADyWQ+GJ62jt=dL9Gzuw_O7USNbS=86BqAzu8Rdv9sCb5OpCdw@mail.gmail.com> <d4a00be5-bd61-0c05-3431-8d56b39a3550@tana.it> <8813331f-f5e4-faa5-c6d-11212fc25797@taugh.com> <5d150251-427c-5c44-a0c3-ad2e7f24b692@tana.it> <01RTP8I70EYI004QVR@mauve.mrochek.com> <6a4a11ea-fae2-81f5-ce5f-fbd4bc1d41e2@taugh.com> <CADyWQ+GrxxVBBGSViap-Hmjty+jq69ak51hY2fUOn1jryUHCHw@mail.gmail.com> <CAOZAAfOuYft5f7JjXi57chBzJwPu1nWb_XUP5iPJPxu5gu2Zgg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <22d97bde-22c3-ef30-c93a-ec89951ab5be@mtcc.com>
Date: Mon, 28 Dec 2020 10:17: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: <CAOZAAfOuYft5f7JjXi57chBzJwPu1nWb_XUP5iPJPxu5gu2Zgg@mail.gmail.com>
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/jq6gFmyLTMnHaVEbCLOATmhbFA8>
Subject: Re: [dmarc-ietf] reporting documents, 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: Mon, 28 Dec 2020 18:17:39 -0000

On 12/28/20 10:05 AM, Seth Blank wrote:
> We agreed to split aggregate and failure reporting into different 
> documents, and this split was discussed on the list several times, as 
> well as at IETF 108.
>
> The intention was to split apart the key components that realistically 
> get updated in different manners / at different cadences.
>
> Aggregate reports and failure reports get used in wholly different 
> manners, have fundamentally different use cases, are implemented in 
> wildly different ways, and have completely different privacy and 
> security considerations. Hence, we agreed they should be split into 
> separate documents, so each can be concise, to the point, and 
> independently updated.
>

Does that mean all of the reporting? So that DMARC is really ADSP-bis? 
The reporting is clearly a completely separate protocol from the policy 
mechanism, and is far more likely to mutate than the base policy 
mechanism which has changed very little from ADSP. I mean, as far as I 
can tell the main change from ADSP is to include spf too.

Mike