> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Scott > Kitterman > Sent: Monday, February 06, 2012 10:14 AM > To: [email protected] > Subject: Re: [marf] I-D Action: draft-ietf-marf-dkim-reporting-09.txt > > I've read the AS draft again and other than the text you just moved > into it, I don't find it particularly useful for implementers of auth > failure FBRs. I think the minimal efficiency for document producers > provided by having one draft to update is more than offset by increased > complexity for implementers having to sorth through a lot of irrelevant > advice.
What I'm trying to avoid is having the same text in two documents (the two reporting drafts) without having to spin up yet another document to contain the common factoring. As Barry pointed out, the AS is essentially our answer to the "How do you use ARF?" question in general, so it seems like a reasonable path to me. That said, this has to have consensus, so I'm open to other opinions. > > The SPF-specific text (i.e., the last paragraph of the AS Section 9.2) > > could be moved back to the SPF document, with more generic text left > > behind in the AS so that it addresses the problem without naming SPF > specifically. > > Except that as written, 9.2 isn't giving advice for just SPF auth > failure results. It's now giving advice for all ARFs (as I understand > it), so I don't think it can be pushed off into a document on how to > due auth failure ARFs for SPF. Right, and my suggestion is to fix that by removing the SPF-specific stuff back to your document, as you suggested, and leaving something more generally applicable in its place. It would not, for example, reappear in the DKIM reporting draft. Section 9 overall is about automatic report generation such as is defined in the two reporting documents we have now, and how doing so differs from the rest of the document. I thought the text in Section 9 itself says that, but I can make it more explicit if needed. -MSK _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
