well, I'm not crazy to develop a new ultimate spam killer from scratch :)
but those groups don't seem to propose something new either.
I'm just telling that SMTP is not the right protocol for email delivery:
-- why do client-to-server and server-to-server have to be the same protocol on the same TCP port? These are completely different tasks with different domains of control, so they have to be two different protocols.
-- there's no obligatory identity check. Well, most ISPs have SMTP authentication for users, but on server2server path, there's none.
-- With wide spread of patent-free cryptography algorithms, why aren't the digital certificates obligatory?
... and so on.
I just say that now it's the only chance to deploy something new, as IPv6 deployment is already something new. There won't be another chance for ditching some old rusty legacy stuff :)
----- Original Message ----
From: Jeroen Massar jeroen@unfix.org
----- Original Message ----
From: Rainer Duffner
How does that work on IPV6 anyway? I read that RBLs will be dead in IPV6-land, due to the fact that the address-space can't be packed in a database anymore.. Currently, RBLs are an important part of our spam-defence.
I mean, drop the current mail transfer protocol completely and design
something new.
With obligatory certificates or some fancy DNS entries, or whatever. I don't
know
what it is, but it's the right time to introduce it :)
I guess you have never ever read: http://www.rhyolite.com/anti-spam/you-might-be.html
Developing the details of the solution is a bit different type of work than
we're
doing here in this list. But it's the perfect place for brainstorming and
throwing
crazy ideas :)
SwiNOG is not that place IMNSHO.
If you want to do protocol work, I guess you read up first, then figure out what this thing called the IETF is and possibly the IRTF, then gain some operational experience, figure out what the MAAWG is, and then proceed from there....