Hi,
If I am correct, the proposal is on the improvement on finding the correct and valid contacts for abuse handling. Unfortunately, the proposal does only mention a possible techical solution on how this data can be stored. It leaves speculation on how the goal (such as valid contact data) can be achieved, which is (for my opinion) the most crucial part. (I am not talking about stuff that is beyond not cooperating members, etc.)
Yes this proposal is only mentioning how the data should look like and how it is stored. Because the Task Force was not intended to do more so far. We all have talked about the problems and how we could solve them, but this was not the intention. Community wanted us to solve the problem on how abuse contact information will show up in the RIPE Database, because the first proposal was too technical and went into a wrong direction. If Community wants the Task Force to go on and take care of the data accuracy. That is fine and I know that the Task Force will be happy to do so. But this proposal is a first step into this direction. Maybe it will get clearer as soon as RIPE NCC has published their implementation thoughts. Since I can not talk for RIPE NCC in behalf of implementation and operational issues I have to stop this discussion here and take care that RIPE NCC is joining this discussion. Never the less thanks for your thoughts and thanks for the suggestions.
+1, why not review and add how to accomodate the accuracy of data.
Because we can not boil the ocean at once. ;-) The implementation of this proposal will take steps to make things easier while looking at data accuracy. We have an accuracy problem in the whole database and not only with the abuse-c. So let's differentiate and mix not up things. Thanks, Tobias -- abusix
Regards,
Aftab A. Siddiqui.