RFC 4291

Frank Ellermann <[email protected]>
Newsgroups gmane.mail.spam.spf.discuss
Message-ID <CAHhFybre0QqPbeOM_zzRZa+ziZ0+a57D=8PwfFwdYt8Cuir8fw@mail.gmail.com>
Hi, somehow RFC 4408 managed to have a normative reference
to RFC 3513 when that was already obsoleted by RFC 4291.

The latter was updated by RFCs 5952 and 6052.  RFC 5952
is relevant for SPF, because it fixes some details for the
textual representation of IPv6 addresses.  Section 3.3.3
is also interesting for ARF.

For RFC 6052 I'm not sure if it is relevant for SPF, what
do the IPv6 experts here think?  We knew ::FFFF:0:0/96 for
IPv4-mapped IPv6 addresses.  IIRC it is used in the test
suite and/or in the reference implementation.

Unsurprisingly we did not know RFC 6052 64:ff9b::/96 for
"IPv4-embedded IPv6 addresses with the well-known prefix"
(that long name is used in RFC 6052).  I think that this
is irrelevant for SPF implementations, but I'm very far
from sure.

-Frank
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.