[acm-tf] Poster on theory of abuse contact management, was Date and time next ACM-TF meeting
Alessandro Vesely vesely at tana.it
Tue Apr 12 18:01:53 CEST 2011
On 12/Apr/11 10:55, Tobias Knecht wrote: > In my opinion there are just 3 pieces. > > The sender (in this case the complainant). > The abuse contact addressbook (in this case the whois database). > The receiver (in this case the abuse contact). I sketched a draft example http://www.tana.it/file/acm-tf.svg I cannot attach it to a list post, because there's a limit of 40 KB. Does anyone have difficulties with SVGs? Most browsers can display them. If needed, I'll put also PNGs. The example doesn't show connections among Sender, Receiver, and db yet. There's more on the threats. > This TF should in my opinion just look at two things. > > How can the Sender find the appropriate contact information in an easy > way and without any restrictions? > > How can the Receiver publish his information in an appropriate and > generic way? A third thing is to maintain this information. In order for a Sender to confidently send a report to a Receiver, someone has to collect assessments about their trustworthiness, so that they can reliably understand each other. > One thing about the wiki page. We need to be careful to not mix up user > generated feedbackloops about spam and real thread reports about > everything + spam. Yes, but being careful implies considering them. > Feedbackloops are a completely different ecosystem. They are usually on > subscription only and it's only about spam. Currently it is like so. However, I counted less than a dozen of those FBLs, all of which are located in North America. > Real thread reports cover much more than spam and are usually not > subscription based. Some kind of FBL may also be not subscription based. > Subscribing to a service will usually give me the opportunity to define > the email address I would like to receive the information. The problem > starts when somebody is not offering a subscription and does not know > where to look for the appropriate contact information. > > That's where we should start.
[ Acm-tf Archives ]