<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="">Dear Sasha, Thank you for your question. Please find our response below. On 12/12/2018 16:04, Sascha Luck [ml] wrote: <blockquote type="cite" class="">I'd like to see input from the NCC here as to what *precisely* constitutes acceptable documentation of a merger or acquisition. Is the assertion that "a full agreement from lawyers" is required true? I believe the NCC owes its members, at the very least,a clear set-out of "the rules" so members will at least be aware of how the NCC allows them to conduct their business. </blockquote> We list the documentation that is required here: <a href="https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/required-documents-for-registry-updates" class="">https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/required-documents-for-registry-updates</a> When we mention documentation from a national authority, this refers to an entry in a trade registry, or another document issued by a chamber of commerce - anything from a national authority which can certify that changes to an organisation or its business structure have taken place. An agreement from lawyers would not meet this requirement because they are not a national authority. While we aim to provide our members with certainty wherever possible, we are unable to supply an exact definition of what is acceptable. This is because the exact legal frameworks around company registration and changes to the legal structure of companies can vary. It is also not practical to supply an exhaustive list of all national authorities in all countries that we serve. In cases where a member has questions, they can always contact us with questions about the supporting documentation. While our due diligence processes might seem cumbersome at times, given the stakes involved for some organisations, it's important that we get this right. Kind regards, Henriette van Ingen Customer Services Manager RIPE NCC <div> <blockquote type="cite" class=""><div class="">On 12 Dec 2018, at 16:04, Sascha Luck [ml] <<a href="mailto:ripe-md@c4inet.net" class="">ripe-md@c4inet.net</a>> wrote:</div> <div class=""><div class="">On Wed, Dec 12, 2018 at 12:50:05PM +0000, Erik Bais wrote: <blockquote type="cite" class="">The RIPE NCC will ask proof of an actual M&A documented by a legal party as a notary in case an actual M&A has occurred. The RIPE policy can’t over-rule actual business decisions like an M&A and with any normal business M&A this is properly documented between parties, typically with a full agreement from lawyers. And that kind of documentation is required. </blockquote> I'd like to see input from the NCC here as to what *precisely* constitutes acceptable documentation of a merger or acquisition. Is the assertion that "a full agreement from lawyers" is required true? I believe the NCC owes its members, at the very least,a clear set-out of "the rules" so members will at least be aware of how the NCC allows them to conduct their business. <blockquote type="cite" class="">If the documentation can’t be produced, because the party is just trying to trick the system (to sell their just received IP resources), the restriction apply. </blockquote> Please provide evidence for your assertion that inability to provide this documentation constitutes "trying to trick the system". In the absence of said evidence, Hitchens's Razor applies. <blockquote type="cite" class="">This was decided by the community (not ‘just’ decided by the RIPE NCC or the Exec Board) when the Transfer policy was presented and discussed. </blockquote> The community (or even the membership) did not decide what 'documentation' is allowable to make a M&A 'legit'. Regards, Sascha Luck <blockquote type="cite" class=""> From: members-discuss <<a href="mailto:members-discuss-bounces@ripe.net" class="">members-discuss-bounces@ripe.net</a>> on behalf of Фри Дата <<a href="mailto:freedatas@yandex.ru" class="">freedatas@yandex.ru</a>> Date: Wednesday 12 December 2018 at 13:37 To: "<a href="mailto:members-discuss@ripe.net" class="">members-discuss@ripe.net</a>" <<a href="mailto:members-discuss@ripe.net" class="">members-discuss@ripe.net</a>> Subject: Re: [members-discuss] Change of conditions Hi. I agree with Alexey. Also I want to pay attention on <a href="https://www.ripe.net/publications/docs/ripe-709#transfer35" class="">https://www.ripe.net/publications/docs/ripe-709#transfer35</a>. This document refers to <a href="https://www.ripe.net/publications/docs/ripe-682#2-2-transfer-restrictions" class="">https://www.ripe.net/publications/docs/ripe-682#2-2-transfer-restrictions</a> where you can read next: This restriction does not prevent the resources from being transferred due to further mergers or acquisitions within the 24-month period. But dear RIPE tells that they cannot transfer the resources in case of change the business structure because of 24 month restriction. How can we understand it? 12.12.2018, 13:03, "Aleksey Bulgakov" <<a href="mailto:aleksbulgakov@gmail.com" class="">aleksbulgakov@gmail.com</a>>: Dear all. I would like to ask you one question. If one company open account in June 2018, but respected executive board decides to implement restrictions in September - should the company to apply this restrictions? I mean the document <a href="https://www.ripe.net/publications/docs/ripe-709#transfer35" class="">https://www.ripe.net/publications/docs/ripe-709#transfer35</a> -- ---------- Best regards, Alexey Bulgakov _______________________________________________ members-discuss mailing list <a href="mailto:members-discuss@ripe.net" class="">members-discuss@ripe.net</a><<a href="mailto:members-discuss@ripe.net" class="">mailto:members-discuss@ripe.net</a>> <a href="https://mailman.ripe.net/" class="">https://mailman.ripe.net/</a> Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/freedatas%40yandex.ru </blockquote> <blockquote type="cite" class="">_______________________________________________ members-discuss mailing list <a href="mailto:members-discuss@ripe.net" class="">members-discuss@ripe.net</a> https://mailman.ripe.net/ Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/ripe-md%40c4inet.net </blockquote> _______________________________________________ members-discuss mailing list <a href="mailto:members-discuss@ripe.net" class="">members-discuss@ripe.net</a> https://mailman.ripe.net/ Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/cs-staff%40ripe.net </div></div></blockquote></div> </body></html>