Ok, here goes. If I am elected, I seek, amongst others things, to do the
following:
- As one of my first orders of business, I will seek to get SPF "Classic"
formalized as soon as possible. And by SPF "Classic" I mean SPF as it de
facto exists to-date (roughly spoken: that which is currently covered by the
Wayne Schlitt draft).
- I will endeavor to 'serve' the SPF community; trite as that may sound, it
means I stand for a council that goes left when the community wishes to go
left, and right when it wishes to go right. I cannot promise that every
single individual will always be accommodated, all the time; but, on the
whole, I believe the work of the council should reflect the wishes of the
SPF community at large; and I will seek to honor those.
- I will actively, and publicly, dissuade the use of SPFv1 records for PRA.
- I will try and focus a good portion of the council's efforts to the rapid
deployment of SRS/SES, but I will not be a proponent of message-signing
schemes, as part of SPF, which require (expensive) third party certificates.
Or the inclusion of patent encumbered technology, for that matter.
- I will seek to prepare the SPF project for the "next round". That is,
working on a new version of SPF, in which now still controversial issues are
solved. Such as: new RR type, number of total DNS queries, and
message-signing schemes, to name a few.
- I do not subscribe to the "Better to do business with the devil we know,
then to wait for a worse party to take over" policy. Technical merit is
paramount.
- I will seek a quick resolution to apparent schisms now within the SPF
community (such as over drafts, srs/spf libs).
Thank you for your consideration,
- Mark
System Administrator Asarian-host.org
-- "If you were supposed to understand it,
we wouldn't call it code." - FedEx