Date: Tue, 11 Feb 2003 12:37:46 +0100 From: Brad Knowles <brad.knowles@skynet.be> To: Rahul Siddharthan <rsidd@online.fr> Cc: Brad Knowles <brad.knowles@skynet.be>, freebsd-chat@freebsd.org Subject: Re: Email push and pull (was Re: matthew dillon) Message-ID: <a05200f2bba6e8fc03a0f@[10.0.1.2]> In-Reply-To: <20030211032932.GA1253@papagena.rockefeller.edu> References: <20030211032932.GA1253@papagena.rockefeller.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:29 PM -0500 2003/02/10, Rahul Siddharthan wrote: > http://cr.yp.to/im2000.html > OK, it's now 2003. Still, nice idea. If spam continues to grow at > present rates, some such scheme may become necessary by 2010 or > even earlier... Okay, so you're going to replace the e-mail system for the entire Internet. You're going to go to local storage on the sender's system, but then you still have to generate messages to be sent to the recipients to tell them to come pick up their mail -- how do you do that? In and of itself, notices like this could be a DOS or DDOS, because you have the same criteria for "Hey, you've got e-mail over here that you need to come pick up" as you do for regular e-mail today. Granted, the messages would be smaller, but their sheer number could still be a DOS or DDOS. There are lots and lots of really big questions that haven't been answered about this kind of solution. This list (from the bottom of this page) is just beginning to think about scratching the surface: How should receivers be identified? How will the sender's ISP find the receiver's ISP? Recipients will want to move transparently from one host to another. How should senders be identified? How will the receiver find the sender's ISP? Recipients will want to provide better handling to known senders; in the long run, recipients will want to debit unknown senders. How should messages be identified? How should messages be downloaded? Messages could be retrieved through HTTP, but an NFS/FSP-style UDP-based protocol would be much more resistant to denial of service. How should notifications, messages, and confirmations be protected against espionage and sabotage? DH authenticators seem more appropriate than public-key signatures for private email; they're also much faster and just as convenient. How should the sender create a message? How should the receiver download a list of notifications? What format should messages have? Indeed, I'd be interested to know if there is a single analog anywhere in the world for this kind of system. -- Brad Knowles, <brad.knowles@skynet.be> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a05200f2bba6e8fc03a0f>