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

Transfer Voluntary Lock 2023-03
by Alexander Kozyar 06 Jun '23

06 Jun '23

Hello! I support this policy.

13 18

Re: [ncc-services-wg] Transfer Voluntary Lock 2023-03
by Maria Merkel 02 Jun '23

02 Jun '23

Hi all, By user accounts I meant LIR portal accounts (i.e. LIR staff members), not end users. I don't see a requirement for a lock request having to be from a company director anywhere in the proposal. — Maria Merkel [https://cdn.staclar.com/logos/novecore/newlogo.png] This email was sent by Staclar, Inc. Any statements contained in this email are personal to the author and are not necessarily the statements of the company unless specifically stated. Novecore and Staclar are collective trading names of Novecore Ltd., registered in England and Wales under company number 11748197, Novecore Licensing Ltd., registered in England and Wales under company number 11544982, Staclar Carrier Ltd., registered in England and Wales under company number 12219686, Staclar Financial Services Ltd., registered in England and Wales under company number 13843292 (registered offices 54 Portland Place, London, UK, W1B 1DY); Novecore Professional Services Ltd., registered in England and Wales under company number 13965912 (registered office 13 Freeland Park, Wareham Road, Poole, UK, BH16 6FA); Novecore (Estonia) OÜ, registered in Estonia under registry code 16543205 (local contact Baltic Business Services OÜ, Narva mnt 5, 10117 Tallinn, Estonia); Novecore (USA) Inc., registered in Delaware under file number 6707907, Novecore Licensing (USA) LLC, registered in Delaware under file number 4030866, and Staclar, Inc., registered in Delaware under file number 7413401 (registered agents The Corporation Trust Company, Corporation Trust Center, 1209 Orange St, Wilmington DE 19801, USA). Novecore Licensing Ltd. is registered for VAT in the United Kingdom under VAT registration number 347 4545 80. Novecore (Estonia) OÜ is registered for VAT in the European Union under VAT registration number EE102518979. Novecore Professional Services Ltd. is a trust or company service provider registered with and supervised by HM Revenue & Customs under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (registration number XMML00000178208). Staclar Financial Services Ltd. is an Annex 1 financial institution registered with and supervised by the Financial Conduct Authority under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (firm reference number 989521). Registration is not equivalent to authorisation and is not an endorsement to do business with a firm. Staclar Financial Services Ltd. is not an authorised person within the meaning of the Financial Services and Markets Act 2000 and does not review, approve, or endorse financial promotions for securities issues it is involved in or provide any form of investment advice. [Sent from Front] On June 2, 2023 at 2:06 PM GMT+2 ripedenis(a)gmail.com<mailto:ripedenis@gmail.com> wrote: Hi guys There is no need for any consultation with end users. End Users have no say in what a resource holder does with a resource or how they manage it. Locking a resource does not affect assignments. If anything it actually gives more security to End Users. There is nothing in the transfer policy to prevent a resource being transferred with sub assignments. Locking a resource prevents the resource with assignments being transferred to another LIR. Cheers Denis On Thu, 1 Jun 2023, 13:40 Matthias Merkel, <matthias.merkel(a)staclar.com<mailto:matthias.merkel@staclar.com>> wrote: Maybe it'd be worth requiring all (or a majority) of user accounts on an LIR to confirm the opt-in? This would prevent potential abuse in cases of insider threats (think disgruntled employees, etc). — Maria Merkel [https://cdn.staclar.com/logos/novecore/newlogo.png] This email was sent by Staclar, Inc. Any statements contained in this email are personal to the author and are not necessarily the statements of the company unless specifically stated. Novecore and Staclar are collective trading names of Novecore Ltd., registered in England and Wales under company number 11748197, Novecore Licensing Ltd., registered in England and Wales under company number 11544982, Staclar Carrier Ltd., registered in England and Wales under company number 12219686, Staclar Financial Services Ltd., registered in England and Wales under company number 13843292 (registered offices 54 Portland Place, London, UK, W1B 1DY); Novecore Professional Services Ltd., registered in England and Wales under company number 13965912 (registered office 13 Freeland Park, Wareham Road, Poole, UK, BH16 6FA); Novecore (Estonia) OÜ, registered in Estonia under registry code 16543205 (local contact Baltic Business Services OÜ, Narva mnt 5, 10117 Tallinn, Estonia); Novecore (USA) Inc., registered in Delaware under file number 6707907, Novecore Licensing (USA) LLC, registered in Delaware under file number 4030866, and Staclar, Inc., registered in Delaware under file number 7413401 (registered agents The Corporation Trust Company, Corporation Trust Center, 1209 Orange St, Wilmington DE 19801, USA). Novecore Licensing Ltd. is registered for VAT in the United Kingdom under VAT registration number 347 4545 80. Novecore (Estonia) OÜ is registered for VAT in the European Union under VAT registration number EE102518979. Novecore Professional Services Ltd. is a trust or company service provider registered with and supervised by HM Revenue & Customs under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (registration number XMML00000178208). Staclar Financial Services Ltd. is an Annex 1 financial institution registered with and supervised by the Financial Conduct Authority under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (firm reference number 989521). Registration is not equivalent to authorisation and is not an endorsement to do business with a firm. Staclar Financial Services Ltd. is not an authorised person within the meaning of the Financial Services and Markets Act 2000 and does not review, approve, or endorse financial promotions for securities issues it is involved in or provide any form of investment advice. [Sent from Front] On June 1, 2023 at 1:37 PM GMT+2 jameskennedy001(a)gmail.com<mailto:jameskennedy001@gmail.com> wrote: I support this policy proposal. Thank you, authors, for your work! Please ensure the feature is accompanied with a very clear and strong warning. The LIR – ideally all their users accounts – should be made very aware upfront about what they can and cannot do once the transfer lock is activated. Regards, James On Thu, Jun 1, 2023 at 12:09 PM Alexander Kozyar <kozyar(a)gmail.com<mailto:kozyar@gmail.com>> wrote: > > Hello! > I support this policy. > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ncc-services-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ncc-services-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ncc-services-wg

1 0

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