>Complex mess?!? It can be done by a 40-line C function that I attach >untested. The benefit is the simplicity of being stateless while >still not requiring to report each and every failure. > >The alternative needs a semaphore to synchronize access to global >store. Then, what kind of global store? Plain files like >/tmp/reports-example.com? MySQL? ...
Assuming you remember what reports you've sent, which I can assure you is a good idea, rate limiting requires one line of SQL. >Yes, such limit makes much sense, either as a global maximum or as a >per-domain one. Shouldn't it be set by the reporter, though? Well, I rate limit my reports, but I thought the topic under discussion was a way for report recipients to say how many reports they want. R's, John _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
