Could I suggest the following: - Keep the first sentence unchanged.
- Then: SPF implementations on IPv6 servers need to handle both "AAAA" and "A" records. This is because clients on IPv4 mapped IPv6 addresses [RFC4291] will appear to the SPF implementation as IPv4 clients. Complementarily to this, SPF records for such clients must contain only IPv4 <ip> addresses. On 24/04/2013 12:22 PM, Scott Kitterman wrote:
On Wednesday, April 24, 2013 06:09:54 PM Philipp Kern wrote:
...
As above that does not help. If your SPF process is operating in the setup above, IPv4-mapped IPv6 space needs to be treated with the IPv4 ruleset.That sounds right. Apparently I fail at describing it though. Going back to the current text in the document: Section 5 of draft-ietf-spfbis-4408bis-14: 'When any mechanism fetches host addresses to compare with <ip>, when <ip> is an IPv4, "A" records are fetched; when <ip> is an IPv6 address, "AAAA" records are fetched. SPF implementations on IPv6 servers need to handle both "AAAA" and "A" secords, for clients on IPv4 mapped IPv6 addresses [RFC4291]. IPv4 <ip> addresses are only listed in an SPF record using the "ip4" mechanism.' I'd appreciate suggestions on making it clearer. Thanks, Scott K -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
