[acm-tf] Poster on theory of abuse contact management, was Date and time next ACM-TF meeting

On 12/Apr/11 10:55, Tobias Knecht wrote:
>> I candidate myself for producing SVG drafts to be discussed here, and
>> printing the final poster(s).
> 
> 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).

Let me attach a draft example.  Does anyone have difficulties with it?
 As an alternative, I could park PNGs somewhere on the web...

> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: acm-tf.svg
Type: image/svg+xml
Size: 141444 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/acm-tf/attachments/20110412/7c968fea/attachment.svg>