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

Voluntary Transfer Lock
by Alexey Levanenko 02 Jun '23

02 Jun '23

Hi for all! I support Voluntary Transfer Lock policy development and proposals for it. Many thanks to all authors for their work. Olexiy Levanenko

1 0

Voluntary Transfer Lock
by Oleg Zinkov 01 Jun '23

01 Jun '23

Hello, RIPE team I joined the Services Working Group just today with a specific goal in mind. I support the Voluntary Transfer Lock (https://www.ripe.net/participate/policies/proposals/2023-03) and want my vote to be counted. Thank you. -- ---------------------- https://kyivlink.com https://t.me/kyivlink https://fb.com/kyivlink https://instagram.com/kyivlink 044 332 9555 093 332 9555

1 0

Voluntary Transfer Lock Policy
by Максим Смелянец 01 Jun '23

01 Jun '23

I support proposal. Best regards, Maxim Smeltanets

2 1

Voluntary Transfer Lock
by Volodymyr Kuzmin 01 Jun '23

01 Jun '23

+1, I support this

1 0

2023-03 Voluntary Transfer Lock
by Igor Tarasenko 01 Jun '23

01 Jun '23

Hello! I also support this proposal and policy development. Best Regards, Igor Tarasenko

1 0

Status on 2023-03
by Kurt Erik Lindqvist 30 May '23

30 May '23

TL;DR Discussion phase for 2023-03 has been extended to 2nd June, please discuss this proposal on this list. All, We want to clarify the status of 2023-03 and what the chairs have proposed. During the four week discussion phase of 2023-03 we reminded the WG several times about this proposal and by the end of the discussion phase, no feedback or comments had been received. The PDP states that "At the end of the Discussion Phase, depending on the feedback received, the proposer decides whether the proposal should be withdrawn from the RIPE PDP or, with the agreement of the WG chair, it can move to the next phase (Review Phase). This should be done no more than four weeks after the end of the Discussion Phase. " The chairs discussed what to do as there had been no feedback on the proposal, and reached out to the proposers and offered to extend the discussion phase. The proposers sent an email to the WG mailing list which generated supportive comments as well as alternative suggestions including that this proposal should not have run through the policy process but rather been actioned by the RIPE NCC directly. We as chairs asked RIPE NCC's legal counsel to comment on the option of not doing this through the policy process, and Athina posted the reply on May 4th. This outlines that the RIPE NCC believes there is a legal risk in the RIPE NCC entering into an agreement without support or in contradiction to RIPE policy. We have discussed with the AP WG chairs if this policy should be discussed in AP or NCC Services and have agreed that it will continue to be discussed in NCC SErvices. We as chairs believe based on earlier discussions that this is a proposal that the WG has interest in but moving proposals forward without any support is problematic, and given the concerns from the RIPE NCC legal counsel on the legal risks around entering agreements against RIPE Policy, we also do not want to undermine the proposal by side-stepping the PDP. To resolve this, the chairs offered to the proposers to extend the discussion phase until after RIPE86 and that we and the proposers would work to get a discussion going. With this email we therefor extend the discussion phase until June 2nd. Please provide thoughts comments, support and feedback on the proposal! RIPE NCC Services WG Chairs, Kurtis, Bijal, Rob

3 3

2023-03 Voluntary Transfer Lock
by Leo Vegoda 29 May '23

29 May '23

Hi, I support this proposal. I previously questioned whether this should be a policy or just a service implementation. I now understand why it needs to be a policy (thanks, Athina!). Kind regards, Leo

4 3

Re: [ncc-services-wg] Update of RIPE NCC Procedural Document and Transfer Agreement Template
by Max Tulyev 21 May '23

21 May '23

On Sat, 20 May 2023 11:43:19 +0200 Олена Кушнір <kea(a)webpro.net.ua> wrote: > Good day, All/Max > There is no need for fairy tales about 5 thousand euros for a court decision. That is not a fairy tale, I said also "or just for free, if you have enough political resource", like in your master's case. > I am categorically against this proposal 2.2, because in this case, those from whom the IP resources were stolen will NEVER GET THEM BACK. And what then is justice? But yes, you are right. In the case resource was stealed, it should be returned back to the legal owner. The question is how to figure out it was stealed and it is not a seller's fraud. Any ideas? -- Max Tulyev <maxtul(a)netassist.ua>

2 2

2023-03 Voluntary Transfer Lock
by Peter Hessler 20 May '23

20 May '23

I support 2023-03 Voluntary Transfer Lock. This is a good option for all members to have available. Since it is voluntary, and has the same authority requirements as transfers, I feel there is minimal risk that this will be inappropriately used. I also feel that we should _not_ unduely delay acceptance of this policy, even if we wish to propose another policy on this topic. Crucially, the very first sentence of: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/tra… gives us all of the authority needed: """All resource holders in the RIPE NCC region can transfer resources in accordance with RIPE policies.""" Furthermore, I disagree with Denis that there is a conflict between policies. This policy is clearly intended to carve out an exception, and it is very specific in describing how. -peter -- There are no data that cannot be plotted on a straight line if the axis are chosen correctly.

2 1

Update of RIPE NCC Procedural Document and Transfer Agreement Template
by Kevin Brennan 19 May '23

19 May '23

Dear colleagues, 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. Section A.1.2.1 (c) Incorrect registration in the RIPE Database was amended through the deletion of the following wording: “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” 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’. 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. 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. 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. 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”. 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. Members are advised to use the updated Transfer Agreement template (v6.0) from the date of this announcement onwards. You can find the updated documents at: https://www.ripe.net/publications/docs/ripe-798 https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/tra… Kind regards, Kevin Brennan Legal Counsel RIPE NCC

2 1