[anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)

Leo,

> You previously wrote, that "If there is no cooperation, this can go
> down until the deregistration." I don't see how a threat of
> deregistration fits alongside a statement that dealing with bogus
> data is outside the scope of your proposal.

Because you asked what will happen if there is no cooperation and I said
that the new abuse-c will be handled in this case as every other object
in the RIPE Database. The "what could happen" is described in this
document (https://www.ripe.net/ripe/docs/ripe-517#b1). And this document
is existing and already in use, so there is no need to describe the same
things in our proposal again.

And from that point of view dealing with bogus data is outside the scope
of this proposal.


>> RIPE NCC has processes in place that cover these issues and as far
>> as I know, is steadily working on improving these to increase data
>> quality. If there is a need for changes in these processes, this
>> should be covered by another proposal.
> 
> I searched the RIPE NCC's web site and could not find any description
> of systemic processes for evaluating and improving the quality of
> registration data. Right now, I don't know whether your threat of
> deregistration is credible. However, I would suggest that if you want
> a data maintenance process to apply to the abuse-c object, then you
> should describe it. As you seem to want the RIPE NCC to remove the
> registration of address space if abuse-c's are not maintained
> appropriately, the standards required should be explicit and either
> included in the policy text or referenced by it.

If RIPE NCC is getting notified about bogus data in any of the objects,
they first of all contact the responsible member and try to solve the
issue that way. If this is not working and the member is not cooperative
RIPE NCC can deregistrate.
Nobody wants that to happen, but at the end it is the decision of RIPE
NCC and I'm absolutely sure, that they take these things very serious.

I do not know why this process is not described somewhere on the website
or why you haven't been able to find it, if it is there. But I guess it
is quite clear that RIPE NCC does not deregistrate members immediately
without trying to get in contact first.

If you think there is a need to have this process described in a paper
we should ask RIPE NCC if they would mind to do it. Maybe they are
already working on something, since the data accuracy issue is a big one
and needs attention.

Tobias

-- 
abusix





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 307 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/anti-abuse-wg/attachments/20111129/cf2351d1/attachment.sig>