2. The second task, which is more fun, but not needed for some time is to
draw up the successor (v3). Of course, the successor will be tagged. One
tricky issue for the v3 RFC to specify is what to do when v1 and v3 are both
specified and give different results. (I would say that v3 should always
override v1 when present.) When a somewhat stable v3 takes shape, it can be
deployed by enthusiasts without an RFC (but with a draft rfc on openspf.org).
After it is really stable (years), a new RFC can be submitted.
Do we really want to alter the specs to the point that v1 and v3 yield
different results? I hope we don't. SPF is quite stable and functional _now_.
I'd expect the time required for stability to be proportional to the number
and depth of changes. Hence, in general, the fewer changes the better.
well I for one would like to see v3 being finer grained
and absorb superceed sender-id functions {so folks like me who don't love
sender-id could publish}
v=spf3/helo a -spf
v=spf3/mfrom -spf
v=spf3/pra -spf
for helo id's
and
v=spf3/helo -all
v-spf3/mfrom redirect=%{l}._spf3.%{o}
v-spf3/pra ?all
for the domain itself
so it is never valid for helo
sender-id pra is never failed and the per-user mfrom spf is checked as usual
for {enveloped sender}
obviously believers in pra checks could define a separate pra policy to mfrom
policy {as even most older SRS-compliant forwarders currently fail pra checks
afterward}
as currently its achievable but kludgy and the average spf user dosn't bother
with the helo portion at all {and relies on the default pass for no spf}
{i would still love to see a syntax addition that equates too invalid from any
source ip ever,
and results in an extra fail-code,
and results in a syntax error if proceeded by any ip returning syntax {mx a
ptr ip4 etc},
or a rewrite to the parser that if it finds -all not proceeded by {mx a ptr
ip4 etc} it returns the same extra fail-code}
the client re-write might be easier all told
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com