-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear BIND developers,
I see that BIND supports the SPF RR type (code 99) since version 9.4.0a1,
and that you have included draft-schlitt-spf-classic-02.txt in the source
distribution. I'd like to point out to you that the final SPF
specification has very recently been published by the IETF as RFC 4408[1].
Nothing has changed in RFC 4408 compared to draft-schlitt-spf-classic-02
with regard to the SPF RR type, but you should probably include
rfc4408.txt instead in future releases of BIND.
Regards,
Julian Mehnle.
References:
1. http://www.ietf.org/rfc/rfc4408.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEX8UowL7PKlBZWjsRArapAJ9HM80AXCM8eU7A2zY7/nwT3bHyQACgr6FZ
HrpH5ceu1I+fH7uYu+iJ4QQ=
=jHbR
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Hash: SHA1
Dear BIND developers,
I see that BIND supports the SPF RR type (code 99) since version 9.4.0a1,
and that you have included draft-schlitt-spf-classic-02.txt in the source
distribution. I'd like to point out to you that the final SPF
specification has very recently been published by the IETF as RFC 4408[1].
Nothing has changed in RFC 4408 compared to draft-schlitt-spf-classic-02
with regard to the SPF RR type, but you should probably include
rfc4408.txt instead in future releases of BIND.
Regards,
Julian Mehnle.
References:
1. http://www.ietf.org/rfc/rfc4408.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEX8UowL7PKlBZWjsRArapAJ9HM80AXCM8eU7A2zY7/nwT3bHyQACgr6FZ
HrpH5ceu1I+fH7uYu+iJ4QQ=
=jHbR
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com