[dmarc-ietf] Recipient domain in aggregate reports (#23)

[Matthäus Wander <[e-mail]>]

Hello everyone,

I'm new to the party. I'd like to bring in some practical experience of
working with DMARC rua reports.

#23 introduces "receiving_domains" in the report metadata, justified by
large infrastructures that host a large number of domains (e.g. Google).

I think, this information would be more useful per-record rather than in
the global metadata. As large infrastructures tend to include many
different records in the report, the analyst needs a correlation between
record and recipient domain.

The <identifiers> section has an optional "envelope_to" already:
>        <!-- The envelope recipient domain. -->
>        <xs:element name="envelope_to" type="xs:string"
>                    minOccurs="0"/>

Is there a benefit in the global "receiving_domains" over the per-record
"envelope_to"?

Most reporters don't include "envelope_to" (e.g. Google). This field
could be made more prominent in the draft. The main body mentions
"header_from" only, but neither "envelope_to" nor "envelope_from".

Regards,
Matt