-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
Here is some brainstorming:
Perhaps SPF2.5 could do away with include, redirect and friends, and
define "source" records separate from "executable" records. The
executable records would have IP addresses only, and a TTL computed
from source documents/records. SPF2.5 checkers would only query
"executable" records. SPF2.5 compilers, on the other hand, would
read the source records - and source records would include text files
fetched via HTTP and v=spf1 records.
As Andy pointed out, there's no need for standardized source records in
your scheme.
Besides you can do that today, using either "ip4:"-only records, or
"exists:" and a dynamic DNS server. I am still working on an experimental
setup of a dynamically programmable "exists:" backend using PowerDNS
(everyone still using BIND should give it a try).
Finally, I think SPFv2.5 would have to be _more_ expressive than v1, not
_less_. That doesn't necessarily mean that it still would have to support
"ptr:", or that the use of "exists:" should not be encouraged more. It
just means it would have to support things like DKIM and PGP policies,
which you can't compile into a list of IP addresses.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFE3gdbwL7PKlBZWjsRAiApAKCwdWEMNtAZNsV4mko1LW/TF9J+vgCaAhrj
nSOtB4On3cXxtf9tpx9M92k=
=OP/o
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com