[acm-tf] Minutes of the first ACM Task Force teleconference

Dear mailing listees,

Herewith I send you the draft minutes of the first ACM Task Force meeting held on the 10th of March 2011 14:00 UTC.

Regards,

Paul

*Participants*

Brian Nisbet (Chair)
Wilfried Woeber
Peter Koch
Tobias Knecht
Suresh Ramasubramanian
Alessandro Vesely
Jochem Ruig
Paul Palse

*Administrative Matters*

- Welcome
- Select scribe (Paul, Jochem)
- Finalise agenda: Agenda accepted.

*Introduction of the task force members*

There was a round of introductions. Everyone gavprovidede some information about their professional background and their motivation to join the ACM Task Force.

*Background of the task force*

Brian explained how the task force came about.

During RIPE 61 in Rome three proposals were discussed, 2010-08, 2010-09 and 2010-10. It was felt that some of these proposals contained either too much implementation details, were too general or missed a clear problem statement.

The most appropriate way forward was to set up a task force as a vehicle to define the problem statements outlined in the proposals and to formalise them into a coherent policy proposal or policy proposals to address them.

*Task force name*

The name: "Abuse Contact Management Task Force (ACM-TF)" was found to be appropriate.

*The charter*

The first round about the charter focussed primarily on “Documenting abuse POC in the RIPE Database” and proposal 2010-08 in particular. In general the following points were brought forward:

- Should be a single logical path to document abuse POC
- The current abuse POC data in the RIPE Database should be deprecated and/or migrated.
- The target audience needs to be defined
- Should it be mandatory?
- Should include a best-practises document
- Should there be a consequence attached for non-compliance?
- It should be done in a way that it doesn’t fall under the “Personal Data” restrictions

Regarding “Data quality in the RIPE Database” the following points were brought forward:

- RIPE NCC mentioned that they found it was hard to find the right approach to find useful “Abuse Contact” details, when they implemented the “Abuse Finder” tool.
- APNIC implemented the IRT object in the way as specified in proposal 2010-08, but also have a procedure to make sure that all other references to abuse related data in the form of abuse mailbox attributes on various other objects etc are cleaned up…

*The charter for the task force*

1. Come up with a policy to describe how to document abuse related POC information in the RIPE Database that is both easy to maintain by resource holders, and easy to retrieve by different target audiences.
2. Put in place procedures and technology to ensure that anti abuse related data is and remains accurate.

The RIPE NCC will work on the draft Charter and will send an updated version in April.

*Other topics/remarks*

 - Task force membership is public by default. The RIPE Website will have a page dedicated to the taskforce and its participants including a short profile. If anyone feels uncomfortable with that please let the RIPE NCC know.

- Tobias indicated his preference to address the “Documenting abuse POC in the RIPE Database” issues first and then continue with the other aspects. This way we can see results much sooner.

- Suresh raised the question if we need more involvement from other groups from the Internet security and anti abuse fields by inviting more participants to the Taskforce. In general it was felt that there is a fair representation of the different groups in the existing task force membership, also to contain the task force group the aim is to limit additional members. We can always invite others for specific topic if we feel we need input for missing expertise ( for instance a Legal Counsel )

*Next meeting*

Set during RIPE 62, Krasnapolsky Hotel, Amsterdam. Monday 2nd May 10:30

Exact room details will be circulated to the participants as soon as they have been fixed. Remote participation will be facilitated.

-- 
Paul Palse
Database Group Manager at RIPE NCC
http://www.ripe.net/info/ncc/contact.html