spf-discuss
[Top] [All Lists]

Re: [spf-discuss] Last changes to draft-schlitt-spf-classic

2006-01-11 16:29:05
In <200601112311(_dot_)10745(_dot_)julian(_at_)mehnle(_dot_)net> Julian Mehnle 
<julian(_at_)mehnle(_dot_)net> writes:

Frank Ellermann wrote:
Wayne Schlitt wrote:
It is quite possible that we could have had an RFC by now.

[...]
You also planned several ABNF updates confirmed by the Community.  Last
state I know was "not yet ready", that was some months ago.

...and I think these last changes /must/ go in, if at all possible.

Also, the council website URL in section 12.2, "The Received-SPF mail 
header", needs to be changed from "http://spf.mehnle.net/"; to "http://www. 
openspf.org/Council" (with a capital "C").  (See the attached patch.)

Yes, this is on my TODO list, along with the reference to
spf.pobox.com


I also wonder if the following change, which I hadn't proposed[1] in time 
for draft-schlitt-spf-classic-02, could make it into the last edition?  
(Patch attached, too.)

--- draft-schlitt-spf-classic-02.xml
+++ draft-schlitt-spf-classic-02+ipv6-handling.xml
@@ -997,9 +997,13 @@
         When any mechanism fetches host addresses to compare with
         &lt;ip&gt;, when &lt;ip&gt; is an IPv4 address, A records are
         fetched, when &lt;ip&gt; is an IPv6 address, AAAA records are
-        fetched.  Even if the SMTP connection is via IPv6, an
-        IPv4-mapped IPv6 IP address (see <xref target="RFC3513"/>
-        section 2.5.5) MUST still be considered an IPv4 address.
+        fetched.  For SPF clients supporting IPv6, it is recommended that
+        it internally operates on IPv6 addresses only, and that it
+        converts any IPv4 addresses to IPv4-mapped IPv6 addresses
+        (::ffff:n.n.n.n, see <xref target="RFC3513"/> section 2.5.5)
+        internally. However, the client MUST still match any such
+        ::ffff:n.n.n.n addresses against n.n.n.n addresses in SPF records
+        and format them as n.n.n.n addresses when generating output text.

I don't see any reason to tell implementations how to do their job.
This may be a good way of doing things, but I see no reason that
should be in the draft.  It is already too long.


-wayne

-------
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