On Wed, Sep 29, 2004 at 03:35:03PM -0700,
Mark Lentczner <markl(_at_)glyphic(_dot_)com> wrote
a message of 58 lines which said:
The only thing I see is the SPF Classic ("v=spf1") that is deployed
in thousands of domains and implemented. Do we have enough
agreement to promote that?
Several good people already said it but, since you asked to see is
there is enough support, I strongly add my vote to an independant
effort to publish a RFC (non Standards TRack, of course) about SPF
classic:
* it would help implementers and deployers to understand what they do,
* it would be an useful basis for future work like "SPF unified".
Some people may seem there is little reason to work on a "SPF
classic", which will be "soon" outdated, when future and more
beautiful "SPF something" are waiting. I disagree. Future systems are
far from being ready and may not be before long. In the mean time, we
need a serious specification of the thing we maintain and deploy.
I suggest to set up a separate effort, on a separate mailing list
(spf-discuss being for discussions of "SPF future"), with a chart
like:
SPF classic specification group
*******************************
The aim of the group is to publish a RFC describing the current SPF
(SPFv1 or "SPF classic") protocol.
The RFC will document the existing protocol, as implemented by
software like libspf or Mail::SPF::Query or libspf2. Every attempt to
"improve" or "fix" the protocol is out of scope.
The RFC will start from the last individual Internet Drafts about SPF,
using the fixes that went into MARID's -protocol Internet Draft.