It appears that Brotman, Alex said:
>"The Report-ID MUST be a unique identifier for the report generation system
>and the domain (domain-name from 7.2.1.1) to which the
>report applies. The string should be created using some number of ASCII
>characters. Otherwise, no format guidance is
It appears that Barry Leiba said:
>I think it should be handled as HFDU, and John should open an issue
>for it on the bis doc. The working group needs to decide what the
>right ABNF should be.
I added an issue with suggested BNF.
Looking at a sample of reports, I see that almost nobody
Folks,
Ticket was opened to address "Report-ID" in aggregate reporting. Today,
RFC7489 (Section 7.2.1.1) refers to a "msg-id" that it uses from RFC5322 as the
format that is required. The document then goes on to say that the true
purpose of the field is to ensure that the receiver can
I think it should be handled as HFDU, and John should open an issue
for it on the bis doc. The working group needs to decide what the
right ABNF should be.
Barry
On Fri, Sep 30, 2022 at 8:51 AM Independent Submissions Editor (Eliot
Lear) wrote:
>
> Hi,
>
> Can I get a bit more clarity on what
Hi,
Can I get a bit more clarity on what should happen with this one.
Eliot
On 21.08.22 17:06, John Levine wrote:
I happen to have a folder with 300,000 reports and took a look. Reporters can
be pretty
random about what they do.
Comcast and Yahoo put angle brackets around the report ID but
