On Tue, 19 Oct 2004, Koen Martens wrote:
I agree completely.
I think PRA in SPFv1 puts an obstacle in a fast moving lane.
Right, and what can the members of this list do about it?? Nothing. If
microsoft decides to use v=spf1 they will just do that. Irrelevant is
what you and others think. This list is largely irrelevant for microsoft.
And we need to change that. I was hoping that PRA can be defeated on
technical grounds (its bad design, really!) and that we'll be able to
convince Meng to stop working with Microsoft based on that and to show
that his continued participation and support of SenderID it doing harm to
SPF community and splitting it up, but now it seems clear that Meng is
also acting not based on technical reasons or for benefit of SPF community
but for his own political reasons... Very unfortunate situation....
So I see no choice but to start reacting to this on the political grounds.
And as far as that, some of you maybe aware that democracy is not only the
elected representatives system, but its ability for citizens to self-organize
and make their opinion known and protest bad decisions made by those elective
representatives. The standard citizen groups political tools are:
1. Letter-writing compaign to your local elected representative (consider
that we've just tried it on this list and failed),
2. Similar is group petitions to government bodies and elected
representatives signed by as many people as possible
3. Political rallies and demonstrations
4. Pickets of events participated by elected representatives and those
who are trying to convince them to do something that people "on the
ground" dont want to do with making sure reporters know about it.
5. Public outcry and use of media to spread the message
(which should go along with 2-4).
As I mentioned #1 we're doing right now on this list with no success, next
step is #2 and it would involve having to write an semi-official letter
from spf community (not too long - about one or two pages, no more) which
should be a group effort if possible (wiki but somebody would have to
volunteer to make first draft and somebody would have to be final editor
as well). The letter or (rather more then one) needs to be addressed to:
1. FTC
2. IETF
3. Meng
4. Microsoft
The letters would have to detail why spf community and those who support
us believes use of v=spf1 records for Sender ID is bad and possibly why
SenderID is itself not a good solution for email authentication. Once
letter(s) are ready we'd have to put it online and spread the word to have
as many people as possible sign it (signing in this case means they
click on the form and provide their name and email and then email
confirmation is sent that they had to respond).
Separate (or similar) letter would also have to be prepared for distribution
on public events. In that case its good idea to distribute it to all
participants of SenderID workshops (somebody who is also on same
conference stands near the door and gives it to all those that come in -
don't worry most will read it if its written well enough).
Media would have to be contacted (after letters to FTC and IETF and
delivered) and be made aware of the situation.
If everything is done, its going to put a lot of pressure on and
make people reconsider supporting SenderID and if its made clear
that most people that support the petitions are main SPF community
participants (all but Meng ...) than its going to make it that
much harder for Meng to make it appear that SPF is behind what is
going on and at least put doubts for everybody.
Now its up to you folks to think if you have enough political energy
to do all this and somebody would need to volunteer to write the letters,
host it, etc (I can volunteer to host it if others can organize everything
else). And note that time is very short to have all this done by IETF and
by Atlanta events (and if at all possibly by ISPCON event). We have no
more then week really to get the letter finished and start telling public
about where it is (i.e. to get people sign it).
--
William Leibzon
Elan Networks
william(_at_)elan(_dot_)net