<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi Hans Petter!</div><div dir="ltr"><br><blockquote type="cite">I would encourage you to have a look at the article outlining some of the alternatives:</blockquote></div><blockquote type="cite"><div dir="ltr"><div><a href="https://labs.ripe.net/author/athina/protecting-resource-holders-in-distressed-areas/" class="">https://labs.ripe.net/author/athina/protecting-resource-holders-in-distressed-areas/</a> </div></div></blockquote><div><br></div><div>Yeah, I did read that. I just don’t agree with the arguments. </div><div><br></div><blockquote type="cite"><div dir="ltr"><div>While this might seem like an easy solution on the surface, we cannot help but anticipate situations where this could be abused. For example, we can imagine cases where malicious employees want to prevent an upcoming transfer. Such a solution would also have some administrative challenges, because who is authorised to activate this freeze would need to be specified. </div></div></blockquote><div><br></div><div>Make it the same person who is authorised to open/close an LIR. The NCC already has those contracts. To prevent abuse make it a paper form with signatures over registered mail, or whatever the NCC has in place already. I’d put the authorisation level at the same one as closing the LIR. </div><br><blockquote type="cite"><div dir="ltr"><div>Also, we wouldn't be able to adhere to such a requested freeze when companies are bankrupt, liquidated or in case of a legitimate merger and acquisition.<br class=""></div></div></blockquote><div><br></div><div>Yeah, I agree there is little you can do about those in any circumstance. </div><br><blockquote type="cite"><div dir="ltr"><div>In any case, if the period of time for the lock is longer than a couple of days, we would again be very reluctant in implementing this solution without a policy proposal.</div></div></blockquote><div><br></div><div>Why? An LIR explicitly and voluntarily giving up some rights they have under the service agreement is surely a matter between the member and the NCC? The policy stays exactly the same. </div><br><blockquote type="cite"><div dir="ltr"><div>I can assure you that we have taken the measures we believe we can within the existing policy.</div></div></blockquote><div><br></div><div>I think adding a disclaimer that allows for making transfers null and void retroactively is a much bigger risk to all involved than a transfer lock would have been. I don’t see how on one hand the NCC can’t verify whether a transfer lock is valid, but can verify with absolute certainty that existing paperwork is null and void.</div><div><br></div><div>To me it feels more like a “let someone else figure this out in court” attitude than an actively helpful one.</div><br><blockquote type="cite"><div dir="ltr"><div>Looking forward to hearing what the community thinks here at the list or the meeting next week.</div></div></blockquote><br><div>Me too! I’m only a single voice here, and this is a community!</div><div><br></div><div>Cheers,</div><div>Sander</div><div><br></div></body></html>