The MARF Working Group met at IETF 77 in Anaheim, California. Approximately 25 people attended in person. JD Falk presented the history of the ARF effort, which started at the Messaging Anti-Abuse Working Group (MAAWG) several years ago. The focus was data sharing among ISPs, and the current format developed after some collaboration among the membership there. This produced draft-shafranovich-feedback-report, which is now draft-ietf-marf-base. Working Group Last Call for the base draft will begin April 2nd after Barry Leiba goes over it once to ensure the proposed payload is in a format easily adapted to other transport mechanisms. WGLC will run for two weeks, and then the base draft will be passed to the IESG. There was some discussion about the MAAWG Feedback Loop BCP document, which might be used as a basis for the working group’s informational documents, per our charter. There will be more liaison about that effort between now and Maastricht; Barry is the IETF’s liaison to MAAWG. There was some discussion about the value of doing an IETF BCP if MAAWG does a BCP; JD points out that BCPs from the IETF undergo more technical rigor, and Barry mentioned that this would increase the general exposure of the material. Murray Kucherawy presented about parallel activities in the mobile space, namely efforts by both the GSM Association (GSMA) and the Open Mobile Alliance (OMA), as we are chartered to track those. The “short code” abuse reporting experiment conducted in France was summarized, as well as a brief overview of the OMA’s current “SpamRep” project. The IETF already has an OMA liaison position, so this will be useful to the working group going forward. There was some discussion about things like where to send reports, which currently neither SpamRep nor ARF specify (though that’s a charter item for us); might be something we could work on with the OMA since they need it as well. Murray also introduced the DKIM Reporting draft (draft-kucherawy-dkim-reporting), which is among our chartered items. There was a brief discussion about ARF extensions. The group was reminded that we are not currently chartered to discuss extensions, but rechartering can easily be done once we’re finished with our current work.