You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Michael Monnerie <mi...@it-management.at> on 2006/05/15 09:52:51 UTC
SPF is now a standard: RFC4408
http://new.openspf.org/News/SPFv1_is_RFC_4408
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660/4156531 .network.your.ideas.
// PGP Key: "lynx -source http://zmi.at/zmi3.asc | gpg --import"
// Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE
// Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
Re: SPF is now a standard: RFC4408
Posted by Tony Finch <do...@dotat.at>.
On Mon, 15 May 2006, John Rudd wrote:
> Technically, that doesn't make it a standard. That means it's on the track to
> becoming a standard.
It doesn't even mean that. There are many RFCs which are not standards-
track, including this one which is "experimental". Note that all the MARID
RFCs haave an extremely scathing IESG note which basically says you should
expect interoperability problems if you use any MARID technique, including
SPF.
> It's not a standard until it's STD-4408, IIRC.
STD numbers are not allocated like that.
Tony.
--
f.a.n.finch <do...@dotat.at> http://dotat.at/
VIKING NORTH UTSIRE SOUTH UTSIRE: SOUTH 7 OR GALE 8, OCCASIONALLY SEVERE GALE
9 IN VIKING AND NORTH UTSIRE, DECREASING 5 OR 6, THEN VEERING SOUTHWEST 6 OR 7
IN VIKING. RAIN AT TIMES. MODERATE OR GOOD.
Re: SPF is now a standard: RFC4408
Posted by John Rudd <jr...@ucsc.edu>.
On May 15, 2006, at 12:52 AM, Michael Monnerie wrote:
> http://new.openspf.org/News/SPFv1_is_RFC_4408
Technically, that doesn't make it a standard. That means it's on the
track to becoming a standard. It's not a standard until it's STD-4408,
IIRC.
Still, nice to see it moving forward. Seeing both SPF and Domain Keys
become widely adopted would be nice.