<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Dear colleagues,<o:p></o:p> <o:p></o:p>The RIPE NCC Procedural document 'Closure of Members, Deregistration of Internet Resources and Legacy Resources' has been reviewed and updated. The following is an overview of the amendments made.<o:p></o:p> <o:p></o:p>Section A.1.2.1 (c) Incorrect registration in the RIPE Database was amended through the deletion of the following wording:<o:p></o:p> “The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC”<o:p></o:p>The reason for this change is that the RIPE NCC no longer approves assignments or netnames in this regard. Deletion of this wording under the abovementioned section therefore aligns current practices with the procedure outlined in ‘Closure of Members, Deregistration of Internet Resources and Legacy Resources’.<o:p></o:p> <o:p></o:p>Section B 1. (c) Deregistration of Internet Number Resources was amended for the same reason, with the same wording being deleted under this section as outlined above.<o:p></o:p> <o:p></o:p>Section B.1. (b) Deregistration of Internet Number Resources was further amended in order to correctly reflect current RIPE policy with regards to the needs-based approach for RIPE NCC-assigned resources. Resources are no longer allocated for a specific need. However, the RIPE NCC may assign resources to members/End Users for a specific need. Slight changes were made to the wording under this section to remove reference to historical RIPE policy provisions and to align it with current RIPE policy.<o:p></o:p> Secondly, the RIPE NCC Transfer Agreement Template has been reviewed and updated. The following articles have been added: “2.1 The terms and conditions of this Transfer Agreement do not violate any existing laws applicable to the Offering Party or to the Receiving Party. <o:p></o:p>2.2 In the event that this Transfer Agreement is nullified or deemed invalid due to violation of laws described in Article 2.1, the transfer of registration of Internet Number Resources shall be reverted and the Internet Number Resources shall be returned to the Offering Party”.<o:p></o:p>In light of a request for transfer of Internet Number Resources, the RIPE NCC was made aware of a law prohibitingcertain transactions between Ukrainian and Russian entities. Considering that different national laws might be applicable to the parties signing a transfer agreement, these articles were added in order for the RIPE NCC to have the parties’ confirmation that the Transfer Agreement does not violate any of the laws applicable to them, and their agreement that, in the event that the Transfer Agreement is nullified or deemed invalid due to violation of such laws, the transfer will be reverted and the Internet Number Resources will be returned to the Offering Party. <o:p></o:p>Members are advised to use the updated Transfer Agreement template (v6.0) from the date of this announcement onwards.<o:p></o:p>You can find the updated documents at:<o:p></o:p><a href="https://www.ripe.net/publications/docs/ripe-798" style="color: rgb(149, 79, 114);">https://www.ripe.net/publications/docs/ripe-798</a><o:p></o:p><a href="https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-of-ip-addresses-and-as-numbers/transfer-agreement-template" style="color: rgb(149, 79, 114);">https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/transfer-of-ip-addresses-and-as-numbers/transfer-agreement-template</a> <o:p></o:p> Kind regards,<o:p></o:p> <o:p></o:p>Kevin Brennan<o:p></o:p>Legal Counsel<o:p></o:p>RIPE NCC<o:p></o:p> </body></html>