In <[email protected]>, on
02/02/2012
at 12:35 PM, Steve Atkins <[email protected]> said:
>I'm not against using ARF for unsolicited reports, I'm against
>sending unsolicited reports that aren't actionable by the recipient.
I'd suggest changing MAY to SHOULD in item 11 of 8. Generating and
Handling Unsolicited Reports.
11. This is, however, not universally true. Anyone sending
unsolicited reports in ARF format can legitimately presume
that some recipients will not be able to see the ARF
metadata (e.g., those elements present in the second part of
the report), and instead SHOULD include all information
needed in the human readable (first, text/plain) section of
the report. Further, they MAY ensure that the report is
readable when viewed as plain text, to give low-end
ticketing systems as much assistance as possible. Finally,
they need to be aware that the report could be discarded or
ignored due to failure to take these steps in the
most extreme cases.
I fixed a couple of nits in the above; adding "some" and changing an
inappropriate "i.e." to "e.g.". I'm not sure whether the second MAY
should also be SHOULD.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2 <http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf
