55
edits
ISATS: Leveraging Identity Based Sender Authentication and Trust for Spam Mitigation: Difference between revisions
ISATS: Leveraging Identity Based Sender Authentication and Trust for Spam Mitigation (view source)
Revision as of 06:23, 23 May 2011
, 23 May 2011no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
The spam protection systems used today only filter spam from the user’s inbox (i.e. recipient’s edge), but the spam already travels the network, and provokes non-negligible cost to network operators in terms of bandwidth and infrastructure. On the other hand, content-based filtering, one of the most widely adopted defense mechanism, has turned spam problem into false positive and negative one. In consequence, this makes email delivery unreliable. | The spam protection systems used today only filter spam from the user’s inbox (i.e. recipient’s edge), but the spam already travels the network, and provokes non-negligible cost to network operators in terms of bandwidth and infrastructure. On the other hand, content-based filtering, one of the most widely adopted defense mechanism, has turned spam problem into false positive and negative one. In consequence, this makes email delivery unreliable. | ||
In iSATS we will leverage the Identity of the email sender to authenticate the source. Further we will maintain a Trust Infrastructure to verify the legitimacy of email along with the sender. Following are the design requirements of iSATS | In '''iSATS''' we will leverage the Identity of the email sender to authenticate the source. Further we will maintain a Trust Infrastructure to verify the legitimacy of email along with the sender. Following are the design requirements of iSATS | ||
* Bind sender‘s identity to the domains, making the misbehaving sender visible | * Bind sender‘s identity to the domains, making the misbehaving sender visible | ||