Re: [dmarc-ietf] https reports, or nits in draft-ietf-dmarc-aggregate-reporting-02

(With Chair hat off and Valimail hat on)

Email works fine for reports, even huge ones at scale. HTTPS adds nothing
for us and adds complexity to report processing (multiple paths to
ingestion) that we’d rather avoid.

Of course, were HTTPS added to the spec, we’d implement it.

Seth

On Sat, May 8, 2021 at 11:14 Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, May 7, 2021 at 12:22 PM John R Levine <johnl@taugh.com> wrote:
>
>> On Fri, 7 May 2021, Murray S. Kucherawy wrote:
>> > [ mail and web departments don't talk to each other ]
>> > If that logic also holds for mail people and web people,
>> > I imagine the lack of interest here has a similar basis; we're talking
>> > about standing up a whole service or endpoint here, not just adding
>> records
>> > to a zone file.
>>
>> That's true but there's also the fact that a handful of analysis services
>> like dmarcian and valimail collect a large fraction of DMARC reports.  If
>> a few of them were interested in https reports, it'd be worth adding.
>>
>
> Ah, that's a good point.
>
> I think both of them are represented here, and maybe some other report
> processors.  Any feedback on this from them?
>
> -MSK
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>
-- 

*Seth Blank* | VP, Product
*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.