May 2023 - ncc-services-wg - mailman.ripe.net

2023-03 Voluntary Transfer Lock
by James Kennedy 12 May '23

12 May '23

Hello, > Why don't we keep it simple? Let's modify ripe-682 and include an opt out clause to disallow transfers. If you invoke this opt out it is a part of ripe-682 so you are not violating it. All the transfer rules are in one policy, self contained and consistent. +1. This is the best permanent solution that I've heard so far. It would take some time to get through the PDP though, and a transfer lock mechanism is urgently needed by some members immediately. So I also support 2023-03 as a stopgap. 2023-03 may contradict ripe-682 as Denis flagged, but IMHO it's more important to get a ‘better-than-nothing’ temporary solution implemented ASAP. Regards, James

1 0

Re: [ncc-services-wg] 2023-03 Voluntary Transfer Lock
by Athina Fragkouli 05 May '23

05 May '23

Dear Rob, all, At the last RIPE meeting in October 2022, a number of Ukrainian members asked for a way to prevent their resources from being transferred, even if a request was submitted that was compliant with RIPE policy. As the RIPE policy does not currently give the RIPE NCC the right to reject a compliant transfer request, we expressed our reluctance to take any decisions that would violate the RIPE policies, as this would potentially expose the RIPE NCC to liability and set a dangerous precedent. If, for example, a resource holder that has asked the RIPE NCC to restrict their ability to transfer resources later sends a policy-compliant transfer request, we would have a hard time rejecting their request without a relevant RIPE policy. In such a case, the resource holder may accuse the RIPE NCC of not adhering to RIPE policies or delaying the transfer without a solid basis. One might argue that the earlier request (to prevent any transfers) accompanied by some form of signed agreement could provide such a solid basis. However, the RIPE NCC cannot enter into agreements that violate RIPE policies or restrict their applicability. Any legal framework the RIPE NCC creates is to facilitate the implementation of RIPE policies, never to violate or restrict them. Recognising the time needed to develop a policy and the related PDP timeframes, and the level of support expressed by the RIPE community for a temporary solution, the RIPE NCC Executive Board decided in December 2022 to allow members and End Users (represented by their sponsoring LIRs) to request the prevention of their resources from being transferred for a period of six months, (i.e. until 1 July 2023): https://www.ripe.net/about-us/executive-board/minutes/2022/minutes-163rd-ex… The RIPE NCC Executive Board will review this decision in June. This temporary solution was based on an explicit understanding that the RIPE community would use this time to develop a RIPE policy that provides a more permanent solution. Kind regards, Athina Fragkouli Chief Legal Officer RIPE NCC

2 2

2023-03 Voluntary Transfer Lock
by Rob Evans 03 May '23

03 May '23

Colleagues, It is four weeks since the end of the discussion phase of 2023-03. During the discussion phase there was no support expressed on the ncc-services-wg list for the policy proposal. Since the end of the discussion phase a small amount of support has been expressed, as well as several questions relating to why this was being handled via the PDP rather than as an NCC process. During the WG meeting in Belgrade, Athina commented that the NCC believed that denying members a service that existed in policy (transfers) was not something the NCC had done before and the NCC believed that without a policy backing up the process, it opened them up to liability. Could I invite the NCC’s legal counsel to confirm that is the case, to explain what liability the NCC believes they would be open to, and how the adoption of this policy would reduce that? Many thanks, Rob o.b.o NCC Services WG Chairs.

2 1