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

Proposed Service Criticality Forms
by Theodoros Polychniatis 12 May '23

12 May '23

Dear Colleagues, During the RIPE NCC Services WG session at RIPE 84 in May, we discussed the Service Criticality Framework (https://ripe84.ripe.net/wp-content/uploads/presentations/101-101-Technology… and https://ripe84.ripe.net/archives/video/811). We mentioned that we would like the Working Group's input on the criticality ratings for www.ripe.net, our email service (MX), RIPE NCC Access (SSO) and the LIR Portal. We have completed the forms internally and would like to share them with you. We hope to receive your feedback by 23 December. Best regards, Theo -- Theodoros Polychniatis Asst. Manager Software Engineering RIPE NCC

1 1

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

2023-03 New Policy Proposal (Voluntary Transfer Lock)
by Angela Dall'Ara 27 Apr '23

27 Apr '23

Dear colleagues, A new RIPE Policy Proposal, 2023-03, “Voluntary Transfer Lock” is now available for discussion. The goal of this proposal is to allow resource holders whose resources are registered with the RIPE NCC to inform them which of these resources must not be transferred for a certain amount of time. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2023-03 As per the RIPE Policy Development Process (PDP), the purpose of this four-week Discussion Phase is to discuss the proposal and provide feedback to the proposers. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal. The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781 We encourage you to review this proposal and send your comments to ncc-services-wg(a)ripe.net before 6 April 2023. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

12 13

RIPE86 call for agenda Items - NCC Services WG
by Bijal Sanghani 18 Apr '23

18 Apr '23

Dear NCC-Services WG, With just over four weeks to go until RIPE86, this is a call for agenda items. If you would like to suggest a topic for discussion or have a presentation you would like to see presented during the NCC Services WG please get in touch with the working group chairs at ncc-services-wg-chairs(a)ripe.net <mailto:ncc-services-wg-chairs@ripe.net>. Remember, this is your opportunity to let the RIPE NCC know what you want from them. Warm regards, RIPE NCC Services WG Chairs

1 0

RIPE85: Draft minutes NCC Services WG
by Bijal Sanghani 18 Apr '23

18 Apr '23

Dear All, You can find the draft minutes from the NCC Services WG in Serbia, here - https://www.ripe.net/participate/ripe/wg/active-wg/services/minutes/ripe-85 <https://www.ripe.net/participate/ripe/wg/active-wg/services/minutes/ripe-84> Please feel free to send comments to the chairs or the mailing list. Kind regards, NCC Services WG Chairs

1 0

New Policy Proposal for Voluntary Transfer Lock
by Михайло Кононихін 18 Apr '23

18 Apr '23

Hello I hope the new 'Voluntary Transfer Lock' does not require a notarized statement as 'Voluntary Registry Lock' It should be a fast working tool. And it should freeze all current transfer requests Nobody lost anything with this button. It just freezes transfers. In opposition without this button there are huge chances that someone can force someone to transfer resources I know what I am talking about because I spent 4 months in the occupation and now I'm a refugee. Terrorists are still looking for our servers (which I move away). I was lucky to run away from them, but my colleague almost 5 months in russian prison (or maybe dead - nobody talking to him since capturing). What I am trying to say is that this is no joke at all. There are lives at stake. Terrorists takes what they want and then get rid of the witnesses This button is what we needed year ago. Maybe it could save one or two lives. Isn't it worth it? Because if there is no possibility to do crime, then there is no crime and no witnesses of crime - no need to kill anyone. I'm sorry if this post was a bit emotional. -- Kind regards, Mykhailo Kononykhin

2 1

Decommissioning RIPE Networking App and RIPE Mailing List Forum
by Fergal Cunningham 11 Apr '23

11 Apr '23

Dear all, By the end of April, we will decommission the RIPE Networking App and also the RIPE Mailing List Forum. In short, these are two services that have not developed in the way we envisioned when we launched them and our research shows they are not widely used. We do not wish to devote development time and maintenance to them when instead we can allow our developers to focus on the services that bring most value to users. More details on the reasons for decommissioning these services are provided below. RIPE Networking App The RIPE Networking App was launched in 2017 and for the next five RIPE Meetings it was widely used by attendees to chat and meet each other virtually. However, this function was largely taken over by the Meetecho platform. The initial reasoning for the RIPE NCC to build our own app rather than using an off-the-shelf product was for RIPE NCC Access integration. The app, as expected, had less usage during the online-only meetings, but our data shows there was no return to normal figures post-pandemic at RIPE 84 and RIPE 85, and even less so at other RIPE NCC-organised events where the app was used. There are also a number of feature requests from attendees and event organisers that would require a complete rewrite of the app needing considerable specialist resources if we were to provide them: - Multi-language support (important for regional events) - Right-to-left (RTL) display - Ability to send images - Phone calendar integration - Displaying both onsite and online attendance status We believe that with the introduction of Meetecho, which has many of the same features of the Networking App, and a possible off-the-shelf solution that supports multi-language and RTL display for smaller RIPE NCC-organised events in Eurasia and the Middle East, we will be able to meet the demands that the Networking App was intended to meet. The RIPE Mailing List Forum Created in 2016, the idea of the forum was to extend the mailing list discussions with an additional interface. However, shortly after implementing the forum, we noticed that spam was being sent to some of the mailing lists via the forum. This was because it was possible to subscribe to the mailing lists using a RIPE NCC Access account and there wasn't very much we could do to combat that. This resulted in us making the forum read-only, which contradicted the reason we created the forum in the first place. We are currently busy with the migration of all RIPE community mailing lists from Mailman 2 to Mailman 3. Mailman 3 will allow better interaction with the mailing lists from a browser than the RIPE Forum does. Decommissioning this will also declutter our website which will help as we continue to redevelop and redesign www.ripe.net. And we will then avoid confusion with the recently-launched RIPE NCC Forum, which we hope you will join: https://forum.ripe.net/ If you have questions or comments on the decommissioning plans, or you have ideas on how we can help with making connections at events or facilitating good online discussions, please let me know. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

RIPE NCC Quarterly Planning Q2 2023
by Fergal Cunningham 30 Mar '23

30 Mar '23

Dear all, We have published our Q2 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 The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and to foster a dialogue with our members and the community about what you would like to see the RIPE NCC work on going forward. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0