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

> Will there be room to hang a poster illustrating how abuse contacts
> are expected to work and play a role in the current scenario?

Don't get me wrong ;-) but does it really matter on how abuse contacts
are expected to work? and play a role in the current scenario?

Does it really matter on how tech-c or admin-c or IRT contacts are
expected to work? and play a role in the current scenario?

I would not go to far with this TF at the moment. We should talk about a
way on how abuse contact information can be inserted into the whois
database in an easy way. And how we can ensure that querying these
information is as easy as publishing them.

> If yes, I think we can quickly agree on some relevant points and
> arrange them nicely in a drawing.  The drawing may illustrate a flow
> scheme, e.g. like http://wiki.asrg.sp.am/wiki/Abuse_Reporting
> (the picture on that page can actually be used as a starting point.)
> 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).

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?



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.

Feedbackloops are a completely different ecosystem. They are usually on
subscription only and it's only about spam.

Real thread reports cover much more than spam and are usually 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.

Thanks,

Tobias

-- 
abusix.org










-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
URL: <https://www.ripe.net/ripe/mail/archives/acm-tf/attachments/20110412/e464d072/attachment.sig>