David Brodbeck [Friday, July 30, 2004 8:37 PM]
On Fri, 30 Jul 2004 13:27:50 -0400, John Keown wrote
The example I should have used was the one posted by an actual spf record.
Mail-OUT.Odessa.Net.
195.66.204.51
where his spf record is Mail-OUT.Odessa.Net/24
That's perfectly sensible -- it means anything from 195.66.204.0 to
195.66.204.255 is allowed. It's not ambiguous. There's no other way to
interpret it.
Sure. As for somebody to wonder why I've used /24 not /16 or /26 or /8 here is
an answer:
http://www.ripe.net/perl/whois?form_type=simple&full_query_string=&searchtext=195.66.204.51
route: 195.66.204.0/24
descr: TM-NET
origin: AS8192
source: RIPE
As result I would like to replace my current record:
24.odessa.ua. IN TXT "v=spf1 a mx a:home.24.odessa.ua ip4:195.66.204.0/24
ip4:207.246.149.176 ~all"
by new IP-less one:
24.odessa.ua. IN TXT "v=spf1 a mx a:home.24.odessa.ua
ip4:Mail-OUT.Odessa.Net/24 ip4:207.246.149.176 ~all"
Or even better !! I would like SPF allow to specify autonomous system number or
ISPs-owners of netblocks from RIPE/ARIN/etc...
24.odessa.ua. IN TXT "v=spf1 a mx a:home.24.odessa.ua as:AS8192
ip4:207.246.149.176 ~all"
This way I will not requere any additional information about my ISP. Actual
information will be always obtained from whois
database or any other service (like BGP).
P.S> Take a read my suggestion about shortcuts for /24 /16 /8 netblocks.
http://archives.listbox.com/spf-discuss(_at_)v2(_dot_)listbox(_dot_)com/200407/0172.html
ip4:10.1.2.3/32 = ip4:10.1.2.3 (already done)
ip4:10.1.2.0/24 = ip4:10.1.2
ip4:10.1.0.0/16 = ip4:10.1
This usage will clear confusion by removing all useless (that somebody think
must be zeroed-out) data.
--
Andriy G. Tereshchenko
Odessa, Ukraine