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

Seth Blank <seth@valimail.com> Mon, 28 December 2020 18:06 UTC

Return-Path: <seth@valimail.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 E301B3A0CD6 for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=valimail.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 BMm_nNPNXPo5 for <dmarc@ietfa.amsl.com>; Mon, 28 Dec 2020 10:06:10 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (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 E65743A0CD5 for <dmarc@ietf.org>; Mon, 28 Dec 2020 10:06:09 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id k9so2468730vke.4 for <dmarc@ietf.org>; Mon, 28 Dec 2020 10:06:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UdRH7LIy0iqwJ01K93GUZa9PdJlGRmP8rIUaxoeT8NI=; b=X2OuPn9A/+XdDEsK+6iA9LdyK+2rM31lUqzaRAeoV6h/vt61WYqlktfp38H7xA6iz+ gJG5xFAui+4tGjlfOT2ziz6jQaU+jhCFrgcFndAsASUHswh/EVP4odhR/91rCgHPIOso F8WU7XREKiB5JkeC0QPBPxq9so5zbKsQTKOPcpEcwziMHvlpPk1B4DaEvJkiP+3qnHMj QhFM7QEDo4gucpzvwzj3zYGDr37gtp1G6SNZVViBwK/tCx8tX5wrS4GJbOghfyXE4GLm Nz8tI4RoTzRaL80CODJYrt1MQd2Uj6b5vYG8ca/QOBnero5M2NnzXVIKeTdLwfNLlxOZ pLcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=UdRH7LIy0iqwJ01K93GUZa9PdJlGRmP8rIUaxoeT8NI=; b=KdQAARubhGAb3ohwo/6ESR6swnKIgm1pJm5lapgcb7sMgSsOGfLL39hzEP6cMp5zKe nHEEG8o1uhsIhH9NC34jF8z7FfvbWrXuOzBpSoRJOOKNew4zEPLGEkWYwRdJgjUf7P9b U6fWUbhD3ROLJkB4hOCa5aYgIK5+AP0dUrfv0SkqX2RDjJeRPQNFx6F6iP34oZMzaBCM tNHkzsuNnaH7BHJYHGgTTqE7EFgfgaIjvrGq+uWdFC5rutqqMybaLKfOnBwpnl3JddPY TQmcSPQyXjnGNkfk0D+9hN1TTQZHfK4HbNNWpzmYsET8O8XHZpxWZ3jTECnQM90b8PKD gpyQ==
X-Gm-Message-State: AOAM532cytcjRJFXbKZ7oYA6Z/b1zA3ffvp4mydy6sUbcmOrHTBA6Kv9 s7Q+KI/XA7WfPNVovT+7HqxIfSLuvqqyTTnDe5fze2zS1SA=
X-Google-Smtp-Source: ABdhPJzpvHrFg/+B3Nnaq9jGtfm9OI3s98B7JRPBklCjOXkX1o5y8LQFhpiR8QCB+S13kNny5bwVmNHwA6mS4TXZUSY=
X-Received: by 2002:a1f:182:: with SMTP id 124mr29582497vkb.4.1609178768348; Mon, 28 Dec 2020 10:06:08 -0800 (PST)
MIME-Version: 1.0
References: <20201218023900.E73B82ACBB2B@ary.qy> <3034face-b6fc-0ce2-fa1b-f59210bd6f5b@tana.it> <46339b38-3b24-bcb7-5e73-8a97038ed69@taugh.com> <3997c81d-3b30-0823-a752-fb1d60a44593@tana.it> <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>
In-Reply-To: <CADyWQ+GrxxVBBGSViap-Hmjty+jq69ak51hY2fUOn1jryUHCHw@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 28 Dec 2020 10:05:57 -0800
Message-ID: <CAOZAAfOuYft5f7JjXi57chBzJwPu1nWb_XUP5iPJPxu5gu2Zgg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de332305b78a2068"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gUn32Y5xXuXpwWQ0lpmP1x4LHC4>
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:06:12 -0000

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.

Seth, as Chair

On Mon, Dec 28, 2020 at 10:00 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:

>
> I will admit my memory can get pretty hazy, but I agree with Mr Levine - I
> remember splitting out reporting,
> but only as one document.
>
> The Working Group can always make a compelling case to change this
>
> tim
>
>
> On Mon, Dec 28, 2020 at 12:06 PM John R Levine <johnl@taugh.com> wrote:
>
>> On Mon, 28 Dec 2020, Ned Freed wrote:
>> > I'm not ethusiastic about the split, but if that's what people want
>> then so be
>> > it. I will say that my experience has been that doing so is usually
>> more work
>> > and provides less benefit than you'd expect.
>>
>> I recall agreeing to split out all of the reporting into a separate
>> draft,
>> which makes some sense so the two parts can proceed separately, but not
>> further splitting aggregate and failure reports.
>>
>> Regards,
>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>> Please consider the environment before reading this e-mail. https://jl.ly
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.