Hi,
On 8/20/24 10:08 PM, Carlos Friaças via db-wg wrote:
In the case where the inetnum holder can't be contacted (or is
unresponsive?) maybe deletion by the RIPE NCC could be a sensible
approach (then there will be a ticket trail).
This can be extended even to personal contact reference in DB. It's
similar issue. Now there is practically no protection against unwanted
reference.
It may also be just non-updated (historic) records, but if the LIR
holding the object does not respond / doesn't care about record
accuracy, there are not many ways to defend yourself from
personal-object-holder perspective - there is no way to get rid of those
references.
And during ARC, you don't have to deal with such micro-details.
A ticket from the other side is probably a reasonable choice here.
And once I tried in the direction of NCC, but without success. Probably
the lack of a policy is the reason for this.
- Daniel
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
