On Fri, May 15, 2020 at 7:20 PM John Levine <jo...@taugh.com> wrote: > In article < > cal0qlwaskzdyeqnjs-bj4ttfdgevfc8gaukmvnost0wj3ge...@mail.gmail.com> you > write: > >+1, unless there are known cases where the XML payload size is a problem > >that switching to JSON would solve. > > It's gzipped, do I doubt it would make much difference. Gzip is really > good at compressing the boilerplate strings that make XML bigger than > JSON. > > Also, FWIW, in seven years the largest report message I ever got was > under 300K, and if people really are concerned about big reports, I > would much rather revive https reporting which avoids base64 encoding > and doesn't have to buffer copies of the report for relay. >
Hatless, as a data point: at Valimail we see reports that are hundreds of megabytes in size, and sometimes push close to a gigabyte. These reports continue to increase in size month over month as sending volume, geographic footprint, deployed third party services, and fraudulent mail attempting to impersonate the domain continually increase Seth -- *Seth Blank* | VP, Standards and New Technologies *e:* s...@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.
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
