The MARF charter [1] does not contain any mention of "SPF Authentication
Failure Reporting using the Abuse Report Format" as a deliverable. There is
no mention of SPF in the charter.
Keep in mind that the charter has these two items:
2) The group will produce an informational document detailing
guidelines for deploying and using ARF, including descriptions
of current practices and their rationales.
3) The group will specify the integration of ARF into DKIM-aware
environments, with draft-kucherawy-dkim-reporting-06 as its input.
It contains extensions to DKIM that are related to ARF as a means
of reporting DKIM-related failures which include phishing
("fraud") and as such are relevant to the ARF effort. The group
will produce Proposed Standard track specification for these
ARF and DKIM extensions.
Then note this:
1. The reporting document originally included the SPF information,
since there's a lot of common aspects, and it makes sense to talk
about both. The WG decided to split the document into four pieces,
for organizational purposes, with authfailure-report, redaction, dkim,
and spf as separate pieces.
2. SPF is widely deployed in the real world. Information about
deploying and using ARF (item 2 in the charter) in such an environment
is absolutely part of the charter.
It's important to get this information out there in parallel with the
DKIM information. If the output of the spfbis working group results
in a need for a revision to this document, such revision can be taken
up then.
Barry
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf