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

2021-05-08 Thread John Levine
It appears that Seth Blank said: >-=-=-=-=-=- > >(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. Just out of nosinesss, ho

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

2021-05-08 Thread Seth Blank
(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

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

2021-05-08 Thread Murray S. Kucherawy
On Fri, May 7, 2021 at 12:22 PM John R Levine 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 >

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

2021-05-07 Thread John R Levine
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