Closed ietf-svn-bot closed 2 years ago
@tim@eudaemon.net commented
List traffic mentions newish working http POST scheme for TLSRPT.
@johnl@taugh.com commented
Specifying a POST or PUT of an XML blob is easy, question is whether there is enough interest to be worth doing so. Semantically PUT is correct, if you PUT the same file twice it's idempotent, but POST is more familiar.
@freddie@freddieleeman.nl commented
I do not think an MTA should do HTTP traffic, most of them might not even be allowed to due to firewall rules. If this is something that remains in the DMARC spec it should be a POST, not a PUT. But my vote will be against this form of report delivery.
Also rua=mailto:
(path-empty) is considered to be valid according to the [URI] ABNF. But since this is NOT a valid DMARC report endpoint I think we need to adjust the [DMARC] ABNF accordingly.
@todd.herr@valimail.com changed component from dmarc-future-notes
to dmarc-bis
@todd.herr@valimail.com commented
As reported in ticket ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis#86:
Long thread on mailing list is here - https://mailarchive.ietf.org/arch/msg/dmarc/DvMTzIy_u6HeK2ptGX9x1oy74kQ/
Thread seemed to fizzle out with takeaways being:
@todd.herr@valimail.com changed status from new
to assigned
@todd.herr@valimail.com set owner to todd.herr@valimail.com
No real interest in URIs other than mailto, so closing ticket.
owner:todd.herr@valimail.com
type_task
| by tim@eudaemon.netSection 6.3 says that ruf and rua tags can take any URI, but only define the meaning of a mailto: URI. Either it should define some other URI schemes or it should say that only mailto: URIs are valid.
Back in the olden days there was an http or https scheme that we took out because it was ill specified, and nobody but me had tried to implement it. If people are interested in an https PUT scheme it would be easy enough to define one, but only if someone says they want to use it. For large reports it could be somewhat faster than mailto both because the report body isn't base64 encoded and the report goes straight to the https server and doesn't get relayed as mail does.
Issue migrated from trac:29 at 2022-01-24 16:15:20 +0000