I have following comments to the new draft:
2.2.1 Subject of SPF testing
...
SMTP+SPF receivers MAY check the HELO argument. In this mode, the
<responsible-sender> comes from the HELO argument IF the HELO
argument is a fully qualified domain name.
12.34.56.78 is also a fully qualified domain name, non-existent though.
So what exactly do you mean by "fully qualified domain name"?
3.1 Matching Version
Please add:
The string "v=spf" is case-sensitive.
4.4 "a"
Please add:
If the domain <target-name> does not exist (NXDOMAIN), the result is
'unknown'.
4.5 "mx"
Please add:
If the domain <target-name> or an MX host name does not exist
(NXDOMAIN), the result 'unknown'.
5.1 redirect: Redirected Query
If all mechanisms fail to match, and a redirect modifier is present,
then processing proceeds as follows.
Better:
If all mechanisms fail to match and no exception is thrown, and a
redirect modifier is present, then processing proceeds as follows.
7.1 Macro definitions
...
The following macro letters are expanded only in "exp" text:
c = SMTP client IP (easily readable format)
There is no need to restrict the 'c' macro to "exp" texts.
i = SMTP client IP (nibble format when an IPv6 address)
Better:
i = SMTP client IP (nibble format for an IPv6 address)
Use of the "t" macro in DNS lookups would greatly reduce the ...
Please add:
The "t" macro expands to the textual decimal notation (without any
leading zero) of the number of seconds elapsed since 00:00:00 GMT,
January 1, 1970 (without counting the leap seconds).
Roger