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

Final Cloud Strategy Published
by Felipe Victolla Silveira 13 Sep '23

13 Sep '23

Dear colleagues, We have now published the final version of our cloud strategy, which was approved by our Executive Board at its last meeting in September. You can find this on RIPE Labs here: https://labs.ripe.net/author/felipe_victolla_silveira/ripe-ncc-cloud-strate… <https://labs.ripe.net/author/felipe_victolla_silveira/ripe-ncc-cloud-strate…> Those of you who read our earlier draft won't find any surprises in the document. Apart from making it more concise, the only change is that the use of containers is now allowed under the strict interpretation of our 'Avoid vendor lock-in' requirement (this is noted in the table). The final part is to agree on the criticality of specific services with the community. We will give you an update on this at RIPE 83. Regards Felipe Victolla Silveira Chief Operations Officer RIPE NCC

2 2

Discussion summary for 2023-03
by Rob Evans 01 Jul '23

01 Jul '23

All, As part of the policy development process, it is the role of the chairs to summarise the discussion at the end of the discussion phase. As we are now at that point, and we are moving towards the review phase when the documents are ready, here is a brief summary. • 8th March 2023: The RIPE Policy Development Officer announces the policy to the ncc-services-wg and policy-announce lists, with a deadline of the 6th April for discussion. • 21st March 2023: One of the co-chairs of the WG reminds the list we are half-way through the discussion phase and invites comments. • 6th April 2023: Original discussion phase closes with no comments received. • 14th April 2023: Request to the list not to require notarised documents for the transfer lock. • 26th April 2023: One of the proposal authors emails the discussion list to ask for discussion. Over the next couple of days there are a few expressions of support, but also several queries as to whether this should be handled in the PDP. • 3rd May 2023: WG co-chair asked the RIPE NCC’s legal counsel about the requirement for a policy. • 4th May 2023: Athina replied with an explanation. Over the next week or so there were a couple of messages discussing Athina’s response, pointing out a clash with RIPE-682, and further discussing whether the proposal should be in the PDP. • 15th May 2023: Discussion phase extended to 2nd June. • 24th May to 2nd June 2023: About a dozen more expressions of support. Some further discussion about the means by which the request should be properly authenticated, whether a single director is sufficient via the LIR portal or notarised papers would be required. Hope that helps. Cheers, Rob, Bijal & Kurtis.

3 2

RIPE NCC Quarterly Planning Q3 2023
by Fergal Cunningham 29 Jun '23

29 Jun '23

Dear colleagues, We have published our Q3 2023 plans for our development teams. These are available at: https://www.ripe.net/support/documentation/quarterly-planning Our quarterly planning includes the work we will be carrying out in the next few months in: - RPKI - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications - DNS and K-root - RIPE Atlas - RIPEstat - RIS - Information Technology - Information Security, Risk, and Compliance By publishing our plans each quarter, we aim to be transparent about the work items we will be carrying out and start a dialogue on other activities you would like to see the RIPE NCC to focus on moving forward. If you have any input on these plans or suggestions for future work, please reach out to us. And there is still time to give your input on our services in the RIPE NCC Survey 2023 if you have yet to do so: https://www.ripe.net/survey Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

2023-03 moving to review phase
by Rob Evans 28 Jun '23

28 Jun '23

Hi all, Following the extended discussion phase, the proposers are working on updating the policy proposal, whilst the NCC is creating the impact analysis and draft RIPE document to accompany the policy. When these are published, the proposal will then move into the Review Phase. Cheers, Rob, Bijal and Kurtis

1 0

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