Skip to main content

You're viewing an archived page. It is no longer being updated.

RIPE 81

Wednesday, 28 October 2020, 16:00 – 16:45
Co-Chairs: Bijal Sanghani, Kurt Erik Lindqvist, Rob Evans
Scribes: Boris Duval / Cecile Pecheur
Status: Final

A. Administrative Matters

Kurtis Lindqvist, WG co-Chair

The presentation is available at:
https://ripe81.ripe.net/presentations/56-ncc-services-ageda81.pdf

The minutes from RIPE 80 were approved.

Kurtis Lindqvist was re-elected as WG co-Chair for another term.

B. RIPE NCC Update: Finding True North

Hans Petter Holen, RIPE NCC Managing Director

The presentation is available at:
https://ripe81.ripe.net/presentations/54-RIPE-NCC-Update-RIPE-81.pdf

Erik Bais, A2B Internet, asked when the RIPE NCC’s internal restructuring started and how long it will take before it’s completed.  Rüdiger Volk asked a similar question regarding the restructuring’s timeline.

Hans Petter answered that the restructuring process started prior to 2019 and that its implementation is detailed in the Activity Plan and Budget. He added that he hoped that several projects (e.g. Project Phoenix) linked to the organisation’s restructuring will be completed by the end of 2020 but that there is no end date as it’s an on-going process.

Daniel Karrenberg asked about the RIPE NCC’s activities review process, how it will work in practice and how the RIPE NCC will identify if a service needs to be discontinued.

Hans Petter replied that this will be done via a service level analysis evaluating all services independently. He added that this product lifecycle analysis was standard in the industry. 

Dmitry Kohmanyuk, Hostmaster.UA, asked if the RIPE NCC had a strategy in place to stop the brain drain of talents and if RIPE NCC’s salaries were competitive enough compare to the rest of the industry.

Hans Petter replied that the RIPE NCC had a project in place (Project Phoenix) that is looking at roles and remuneration. He added that even though salaries were good at the RIPE NCC, there was also other aspects that attracted employees to join the RIPE NCC such as working for a non-profit organisation and the good of the Internet.

C. Operational Update

Felipe Victolla Silveira, Chief Operations Officer, RIPE NCC

The presentation is available at:
https://ripe81.ripe.net/presentations/43-RIPE-81-Operational-Update-Final.pdf

Erik Bais and Rüdiger Volk asked if it was possible to receive a copy of the RPKI audit report.

Felipe Victolla Silveira mentioned that this was impossible to disclose the report’s content for security reasons but that the RIPE NCC will share more details once the fixes are implemented.

There were no more questions.

D. RIPE NCC Language Support

Fergal Cunningham, RIPE NCC

The presentation is available at:
https://ripe81.ripe.net/presentations/42-Language-Support-at-the-RIPE-NCC.pdf

Brian Nisbet (HEAnet) commented that this was a great initiative. 

Daniel Karrenberg (RIPE NCC) asked if community involvement had been considered to ask for volunteers to increase the number of languages to be translated into, and to choose to which languages to translate.

Fergal confirmed that community involvement is being considered - RIPE Atlas is already sourcing translations on GitHub for instance. He also confirmed that the six languages selected were based on feedback from the community and from RIPE NCC staff experience based on requests, and that the presentation will hopefully trigger feedback as well.

Benedikt Stockebrand (Stepladder IT) stated that this is a very good idea and suggested that RIPE NCC should also aim at simplifying the English used for non-native speakers. Fergal agreed that this was also important and that an internal project was started a year ago to make information and documents clearer and more relevant. 

E. RIPE NCC Executive Board Election Task Force report

Sergey Myasoedov, Taskforce Chair

The presentation is available at:
https://ripe81.ripe.net/presentations/57-ripe-81-ncc-myasoedov.pdf

Rob Evans (Jisc) pointed out that the trusted contacts may not be the most appropriate person(s) to decide whether the Code of Conduct was breached due to their role of a confidant. Sergey stated that someone from the community needed to make that decision and that the decisions made by the trusted contact(s) would be reviewed by the Executive Board, together with the members.

F. RIPE NCC Services WG chair selection

This was discussed during the first session of the RIPE NCC Services Working Group.

G. Open Microphone Session 

There were no questions.

 Z. Any other business

There were no comments.

Fergal reminded attendees to use the correct link to join in the RIPE NCC General Meeting taking place shortly after.