Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality

[Alessandro Vesely <[e-mail]>]

On Wed 30/Dec/2020 22:23:20 +0100 John R Levine wrote:
> There was some discussion about the detail that if there are multiple addresses 
> in the rua= tag you send the report to all of them.  People were quite clear 
> that is a feature.  I proposed as a hack a ruap= tag for rua preferred, if the 
> reporting system can send reports to all of the URIs in the ruap tag it does 
> so, otherwise it uses rua as it does now.  That lets you put the https URIs in 
> the ruap tag which existing code will ignore.
> 
> Didn't get a lot of comments pro or con on that one.


I still like better sticking to a unique tag (rua=) and applying OR-slashes.  With a comma, it is backward compatible:

v=DMARC1; p=none; rua=mailto:[e-mail], mailto:[e-mail], /https://service.example/report/;

(The first scheme without a leading slash introduces a new series of alternatives.)

The main reason to stick to the same tag is to allow overriding.  For example, if the above record were:

$ORIGIN=_dmarc.example.com
IN TXT "v=DMARC1; p=none; rua=mailto:[e-mail], mailto:[e-mail]"

Then service.example can override rua=:

$ORIGIN=example.com._report._dmarc.service.example
IN TXT "v=DMARC1; rua=mailto:[e-mail], /https://service.example/report/;


Best
Ale
--