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

Hi,

> No, it doesn't really answer my question. I am no longer familiar
> with the way the RIPE NCC handles bogus data published in the
> database but as you are proposing that failure to comply with the
> policy should lead to deregistration, it seems only reasonable that
> the proposers should explicitly state what they intend to happen in
> various circumstances.
> 
> I want to know whether this is proposal is going to result in large
> amounts of unmaintained data of questionable quality being
> registered, or whether some kind of maintenance process is envisaged
> and if so what that should be.

I'm and the Task Force are not proposing anything about bogus data. The
proposal is proposing to introduce an abuse-c with some special
features. What happens with bogus data is not and can not be part of
this proposal. I fully understand that this is an issue that has to be
covered, but not within 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.

In my personal opinion the proposal has a chance to increase data
quality. Since there is not a new object and the existing objects can be
used but have to be "upgraded" with the abuse-mailbox attribute. There
is a need for maintainers to go over at least the objects they want to
use for abuse-c and review the data given. But that is a personal opinion.

Thanks,

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/20111128/24d2ed40/attachment.sig>