<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I think it would be good to look for contact details in the authoritative whois for the resources involved. E.g. RDAP provides a generic way to do this. In particular maliciously created objects may have contact details in them for the wrong people if only the RIPE (non-authoritative) object is looked at, and these contacts may have a vested interest in keeping their object.</div><div class=""><br class=""></div><div class="">I understand that this could complicate processing of potential concerns in cases where disagreements may come up, but to me it seems more important that the real current holders of the resources should have the bigger say in this.</div><div class=""><br class=""></div><div class="">Tim<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 4 Jun 2019, at 15:21, Alexander Azimov <<a href="mailto:a.e.azimov@gmail.com" class="">a.e.azimov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">I was opposing the first version of this proposal, where conflicting objects were silently and instantly removed.</div><div class="">The new version seems to resolve these concerns - and 7-day notification should be fine.</div><div class=""><br class=""></div>But I'm not sure if all objects have optional 'notify' field (and a brief check showed that there are some without this field, I don't have exact numbers at the moment). If there is the technical opportunity I would suggest to also use notify field (and may be other contacts)
from the related maintainer object.<br class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 31 мая 2019 г. в 14:11, Tore Anderson <<a href="mailto:tore@fud.no" class="">tore@fud.no</a>>:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* Marco Schmidt<br class="">
<br class="">
> A new version of RIPE Policy proposal, 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now available for discussion.<br class="">
> <br class="">
> The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA.<br class="">
<br class="">
Eminently sensible. Supported.<br class="">
<br class="">
Tore<br class="">
<br class="">
</blockquote></div><br clear="all" class=""><br class="">-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class="">Best regards,<div class="">Alexander Azimov</div></div></div>
</div></blockquote></div><br class=""></div></div></body></html>