On Thursday 10 August 2006 17:30, Stuart D. Gathman wrote:
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.
The more I think about it, the more I like that idea. So shoot holes in
it quick before I start promoting it.
We don't need a new standard for this. If you want to compile the records to
IP addresses, just do it. If you want to improve the syntax, do the
following:
1. Ditch PTR. It's virtually never necessary, way overused, and inherently
problematic.
2. Combine a, ip4, and ip6 into one new mechanism. There's no need for them
to be separate and it's a source of common mistakes. An implementation can
distinguish based on the content after the ":".
Given the sizes of the records we are talking about, I don't see where http
helps us much.
Scott K
-------
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