On Tuesday, February 14, 2012 10:26:16 AM RFC Errata System wrote: > The following errata report has been submitted for RFC5965, > "An Extensible Format for Email Feedback Reports". ... > Reports can be created from info collected in SMTP transactions that don't > accept a message, a scenario we didn't consider when we wrote this section. ...
Based on the discussions on the list, I looked at including the 'fix' for this in the SPF draft and having it update 5965. When I get into the text though, I don't think this works. The current draft (correctly) says: This document extends [SPF] to add an optional reporting address and other parameters. Extension of [ARF] to add features required for the reporting of these incidents is covered in [I-D.IETF-MARF-AUTHFAILURE-REPORT] and [I-D.IETF-MARF-AS]. So it seems more than a little awkward to shove an ARF fix in here. Ideally, if we were going to fix it in one of the current drafts it should be I-D.IETF- MARF-AUTHFAILURE-REPORT, but I guess it's too late for that. I'm going to proceed on the assumption that the errata will eventually be confirmed and that's sufficient or some was will be found to stuff it into I- D.IETF-MARF-AUTHFAILURE-REPORT/AS and that I don't need to directly address it in the SPF draft. I don't see an non-contrived way to do it. Scott K _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
