Re: Live-DNS testing infrastructure

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
> Julian Mehnle wrote:
> > Stefano Bagnara wrote:
> > > Wouldn't it worth to publish command line conventions and spfd
> > > "protocols" in the OpenSPF website so that implementations can
> > > easily see what are the "suggested" interfaces?
> >
> > Yes.  It's just an issue of finding the time to do it.  I'll try to do
> > it since I am the one who is most familiar with the original
> > spfd/spfquery interfaces (other than Meng, who is busy with other
> > stuff nowadays) as well as the thought-through-anew ones in
> > Mail::SPF's versions of the tools.
>
> Currently I think pyspf is supporting libspf2, Mail::SPF::Query, and
> Mail::SPF style spfquery.  Please let's not add more.

Not add more, but agree on a standard and then document it.

As far as spfd's interface is concerned, which is probably the best 
solution for an implementation-independent test harness interface, 
there's really only that of the original spfd that was shipped with 
Mail::SPF::Query and libspf2 (I think they behave identically), and the 
one shipped with Mail::SPF.  The only difference between the former and 
the latter is the naming of the request/response fields as well as the 
naming of the result codes ("unknown" vs. "permerror", "error" vs.
"temperror"):

  http://search.cpan.org/dist/Mail-SPF/sbin/spfd#COMPATIBILITY

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkisJusACgkQwL7PKlBZWjtbZACfaL3iXMTm06U6lS2xscMFbdIL
8yYAoL1K61v7x5cAGq7JWSSSFVep2GLT
=yGiT
-----END PGP SIGNATURE-----