- members-discuss - mailman.ripe.net

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
by Hans Petter Holen 21 Oct '20

21 Oct '20

Hi Nick, > On 29 Sep 2020, at 17:06, Nick Hilliard (Network Ability Ltd) <nick(a)netability.ie <mailto:nick@netability.ie>> wrote: >> > > Hi Hans Petter, > > couple of queries here. > > 1. RIPE atlas measurements are growing much faster than ripe probe / anchor deployment. In addition, some of the older deployed probe stock is decaying. Is the capex allocation of €130k enough expenditure as part of the long term funding plan for Atlas to ensure that the current rate of increase of measurements can be sustained in the long term? Yes. In terms of measurements data storage and processing, we are aiming to migrate live storage and processing of the ever-growing dataset to the cloud (with proper in-house, offline backup plans). That significantly reduces the investments required for that part. Next to introduction of Software Probes and on replenishing the hardware probe network and keeping up and growing with new or uncovered ASes, so far we have generally relied on contributions from our sponsors. We are currently developing mid- and long-term plans for the supply of hardware probes, and we will inform the community and our membership as soon as we complete our proposal. > > 2. IT security: presumably this encompasses RPKI TA and hosted CA security management too? No. The security budget is not fully centralised. The costs for RPKI TA and hosted CA security management is budgeted as part of the RPKI budget. > 3. RIPE Chair Team: the allocation of €205k for Chair, Vice Chair and travel + subsistence looks surprisingly low given that the average personnel cost per FTE is listed as €102k. Separately, the board committed to ensuring independence of the RIPE Chair Team from the NCC. Can you provide information on how this independence will be maintained, and also reassurance that the RIPE Chair Team remuneration package has been designed or at least reviewed by an independent third party to ensure that it's appropriate for the positions? The remuneration component of the package covers the RIPE Chair but not the Vice Chair. Travel and expenses for both are covered, however. The travel expense budget is based on the travel expense budget for the previous RIPE Chair. For 2021 we have only budgeted for travel 75% of the previous years. The contract between the RIPE Chair and the RIPE NCC has been negotiated between the RIPE Chair and the RIPE NCC Executive board represented by the Chair and Treasurer. The contract includes multiple clauses that enforce the separation of the Chair position from influence by the RIPE NCC and its board. This contract has been reviewed by external legal experts for compliance with Dutch labour laws. The remuneration package is aligned with the RIPE NCC salaries which have been benchmarked by an external party. > 4. Software development: there's been some discussion about the RPKI validator. One issue that hasn't been touched on is the RIPE NCC's general involvement with software development where there are other third party packages available on a commercial or commercially-supported basis. This is an issue that was raised before (many years ago), specifically in the context of development of DNS software. Can you provide some info on what the RIPE NCC's governing policies are in this area? In this case, we follow the RIPE NCC’s roles and responsibilities as laid out here: https://www.ripe.net/about-us/what-we-do/ripe-ncc-association-roles-and-res… <https://www.ripe.net/about-us/what-we-do/ripe-ncc-association-roles-and-res…> We do not have specific policies for software development. Such decisions are made in consultation with the board and community. From what I recall there was no other viable RPKI validator when we started this development work, so an investment to bootstrap the whole system was needed. > 5. E-voting: as there are no alternatives in the short-term future, has the RIPE NCC confirmed that the E-voting platform will be fully GDPR compliant for the upcoming GM and also on Jan 1, 2021? I.e both in terms of potential brexit outcomes and also in terms of transatlantic data transfer following the Schrems 2 ruling. The e-voting platform for the upcoming GM is GDPR compliant. Our third-party platform provider has confirmed that no personal data is transferred to the USA, therefore the recent Schrems II ruling does not have an impact in our relationship. Regarding the legal implications due to Brexit, we are following the relevant developments. When the data protection legal framework is clarified, we will make sure that all amendments necessary are performed in order to comply with the law. I hope this answers your questions, but are happy to further clarify if needed. Hans Petter Holen Managing Director, RIPE NCC

1 0

Webauthn
by Bogdan I. 14 Oct '20

14 Oct '20

Hello What would be your opinion of implementing Webauthn / U2F by security keys for the RIPE NCC website's two factor authentication, in addition to the current TOTP system? The current TOTP based system works fine, but i find using a physical security key to be more convenient and more secure. -- Bogdan Ionescu Redcluster LTD

5 5

Draft Activity Plan 2021 - RPKI development
by Erik Bais 01 Oct '20

01 Oct '20

Dear Hans Petter and fellow members, In the draft activity plan, there is a page about the current RPKI cost and plans of the further development. The plans state on Page 14 - 1.6 RPKI: 6 FTE and a 963.000 euro budget ... <begin quote> Activities in 2021 Our priority over the coming period will be ensuring a stable and resilient RPKI Trust Anchor and Certificate Authority. In 2020, we carried out a third-party security and risk assessment of our RPKI platform. We are now working to define a complete audit framework for RPKI, with the aim of having the audit performed early next year by a third party. Next year we will implement changes to our internal processes and documented procedures on the basis of this audit, as well as things like more granular monitoring and small technical changes that ensure compliance with the relevant RFCs. Aside from that, we are planning significant improvements in our infrastructure to allow high availability and resiliency for the RPKI repositories. In last year’s Activity Plan, we said we would consider whether we should continue to support our RPKI Validator, as it needed further development to match the quality of alternative tools that were now available. Because our RPKI Validator remains the second most widely used tool (with 32% “market share”), we decided that we will continue to support it in 2021 and we aim to make a longer-term decision soon. Finally, we will continue to build awareness of RPKI through training, outreach and promotion efforts. </end quote> I would like to argue that further development of Proof of Concept software (the RPKI validator) isn't required anymore now that there are multiple open source tools available on the market. The RIPE NCC isn't a software development house .. and I don't recall the RIPE NCC has the planning to become one ... I would like to see further development of the RIPE NCC RPKI Validator discontinued as of Jan. 1st 2021. The backend software / infra for the signing of the RPKI environment still needs a lot of work and so does the training (awareness) about RPKI .. so I don't think that the resources or budgeted cost should be reduced, but is needs to be revised... I think that the efforts should be put somewhere else on RPKI. That the RIPE NCC RPKI Validator is widely used, is because of the training efforts from the RIPE NCC.. and I think the community is better served with a more open approach about the usage of other validators, instead of trying to keep members to use a Java based software package. When the RIPE NCC started with the development of the RPKI Validator, there was a lack of other software ... but as things stand today, there are multiple open source implementations and this is a nice moment to go back to the core activity of the RIPE NCC. I know that with the above, I would probably not give the internal development team enough credits for their work and effort in the past years. I do value their work to where they brought this, but it is time to put the focus on the core activities like the signing side of the RPKI and a more robust RPKI infra instead of the validation software. Regards, Erik Bais

12 12

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
by Nick Hilliard (Network Ability Ltd) 29 Sep '20

29 Sep '20

Hans Petter Holen wrote on 16/09/2020 15:27: > Dear members, > > The Draft RIPE NCC Activity Plan and Budget 2021 is now available for > your review: > https://www.ripe.net/participate/meetings/gm/meetings/october-2020/draft-ri… > > This document is the clearest way you can learn about our plans for > next year and shape the direction we take as an organisation. We ask > that you read it and share any feedback on <members-discuss(a)ripe.net>. Hi Hans Petter, couple of queries here. 1. RIPE atlas measurements are growing much faster than ripe probe / anchor deployment. In addition, some of the older deployed probe stock is decaying. Is the capex allocation of €130k enough expenditure as part of the long term funding plan for Atlas to ensure that the current rate of increase of measurements can be sustained in the long term? 2. IT security: presumably this encompasses RPKI TA and hosted CA security management too? 3. RIPE Chair Team: the allocation of €205k for Chair, Vice Chair and travel + subsistence looks surprisingly low given that the average personnel cost per FTE is listed as €102k. Separately, the board committed to ensuring independence of the RIPE Chair Team from the NCC. Can you provide information on how this independence will be maintained, and also reassurance that the RIPE Chair Team remuneration package has been designed or at least reviewed by an independent third party to ensure that it's appropriate for the positions? 4. Software development: there's been some discussion about the RPKI validator. One issue that hasn't been touched on is the RIPE NCC's general involvement with software development where there are other third party packages available on a commercial or commercially-supported basis. This is an issue that was raised before (many years ago), specifically in the context of development of DNS software. Can you provide some info on what the RIPE NCC's governing policies are in this area? 5. E-voting: as there are no alternatives in the short-term future, has the RIPE NCC confirmed that the E-voting platform will be fully GDPR compliant for the upcoming GM and also on Jan 1, 2021? I.e both in terms of potential brexit outcomes and also in terms of transatlantic data transfer following the Schrems 2 ruling. Nick

1 0

RIPE NCC Executive Board Election Task Force Report Now Available
by Christian Kaufmann 18 Sep '20

18 Sep '20

Dear members, The RIPE NCC Executive Board Election Task Force assembled in July in order to carry out a full evaluation of our Executive Board nomination and election process. The task force has since shared its report with my fellow board members and I, and we are glad to announce that we fully support all nine of the recommendations they have made for improving the existing processes. The final report is now available on the RIPE NCC website as a supporting document for our October GM, which will take place from 28-30 October adjacent to the RIPE 81 meeting. There will be a presentation on the report during the GM, and members will also have a chance to vote on changes to the RIPE NCC Articles of Association that are necessary if the recommendations are to be implemented. https://www.ripe.net/participate/meetings/gm/meetings/october-2020/supporti… The task force has carried out its objective swiftly and diligently. On behalf of the board, I would like to express our sincere appreciation for the work done by each of the eight members of the task force in such a short amount of time: Erik Bais Randy Bush Carlos Friaças Töma Gavrichenkov Sergey Myasoedov (Task Force Chair) Arnold Nipper Cynthia Revström Jan Žorž We look forward to discussing this topic further with all RIPE NCC members at the October GM. Kind regards, Christian Kaufmann RIPE NCC Executive Board Chairman

1 0

Re: [members-discuss] [ncc-announce] [GM] Register for the RIPE NCC General Meeting October 2020
by Sergey Myasoedov 03 Sep '20

03 Sep '20

Dear Hans Petter, There are some confusing dates in your message: > Important Dates and Deadlines > 2 Sep - Invitation to register for GM and voting > 30 Sep - GM documents published > 14 Oct - Deadline for proxy vote nominations > 14 Oct - Deadline for members to propose resolutions > 14 Oct - Deadline to publish final agenda > 28 Oct - GM begins with main meeting (18:00 UTC+1) RIPE-739, AoA: 15.1 The Executive Board shall send the convocations for the General Meeting, including the agenda containing the subjects for the General Meeting, a URL to the verbatim text of the proposed resolutions and, if applicable, the draft Activity Plan and draft budget, to the Members at least _four_weeks_ before the Meeting... As far as I understand, the agenda and resolutions should be published by 28 September, is this correct? Thanks. -- Kind regards, Sergey Myasoedov You wrote Wednesday, September 2, 2020, 10:37:01 AM: > Dear colleagues, > On behalf of our Executive Board, I invite you to register for the RIPE > NCC General Meeting (GM) October 2020. > You can register to participate and vote at: > https://www.ripe.net/s/gm-registration-oct-2020 > The GM will take place from 28-30 October 2020 online, adjacent to the > RIPE 81 meeting. To participate you can follow the GM via livestream, > participate via chat and vote on resolutions electronically. > The GM gives members an opportunity to discuss the operations and > activities of the RIPE NCC. At the upcoming GM, we invite you to > discuss, among other things: > - The Draft RIPE NCC Activity Plan and Budget 2021 > - Redistribution of the RIPE NCC surplus/deficit to the membership (to > be voted on) > - Reports from the RIPE NCC Executive Board and RIPE NCC Management > All supporting documents will be posted and announced to the membership > by 30 September 2020. > Registration for electronic voting will remain open until 16:00 local > time (UTC+1) on the day of the GM, 28 October 2020. > All information on how to participate, including the proxy voting form, > is available from: > https://ripe.net/gm/oct-2020 > If you have questions about the GM, please email us at agm(a)ripe.net. > Kind regards, > Hans Petter Holen > Managing Director > RIPE NCC > Important Dates and Deadlines > 2 Sep - Invitation to register for GM and voting > 30 Sep - GM documents published > 14 Oct - Deadline for proxy vote nominations > 14 Oct - Deadline for members to propose resolutions > 14 Oct - Deadline to publish final agenda > 28 Oct - GM begins with main meeting (18:00 UTC+1) > 30 Oct - GM closes with announcement of voting results (10:45 UTC+1)

2 1

Re: [members-discuss] Request to put Members-discuss in moderation
by Elad Cohen 27 Jul '20

27 Jul '20

Mr. Doering, The actual voters are reflecting the whole RIPE community, hence nearly 4000 members are supporting me. And I did receive more votes than the initial votes of the elected #3 and only because the voting system that elected #1 can ask his voters who to support in the next seats, the elected #3 was elected. Kind Regards, Elad ________________________________ From: Gert Doering Sent: Tuesday, July 21, 2020 5:01 PM To: Elad Cohen Cc: Andrei Banu; members-discuss(a)ripe.net; exec-board(a)ripe.net Subject: Re: [members-discuss] Request to put Members-discuss in moderation Hi, On Tue, Jul 21, 2020 at 10:54:46AM +0000, Elad Cohen wrote: > Andrei, I received 15% of the total votes, which are reflecting 15% of the > total members in the RIPE community, approximately 4000 members. 15% of the votes registered. Since not all members voted, this is WAY less than "4000 members supporting you". (I tried to stay out of this, but this is factually wrong and gives the impression that there is large support for Mr. Cohen, which there wasn't. Some protest voters always vote "against the regime!", and of course they are free to do so) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

6 9

Fw: RIPE NCC Executive Board Election Task Force Members
by Elad Cohen 27 Jul '20

27 Jul '20

If a majority in a task force can decide to dismiss one of the task force members then a task force will never be diverse. This is exactly what happened here, a majority of people that know themselves well before the task force decided which task force members they want and which they don't want. Kind Regards, Elad ________________________________ From: Elad Cohen <elad(a)netstyle.io> Sent: Wednesday, July 22, 2020 4:59 PM To: Sergey Myasoedov <kaa(a)net-art.cz>; Cynthia Revström <me(a)cynthia.re> Cc: Arnold Nipper <arnold.nipper(a)de-cix.net>; Carlos Friaças <cfriacas(a)fccn.pt>; Jan Zorz - Go6 <jan(a)go6.si>; Erik Bais <erik(a)bais.name>; Töma Gavrichenkov <ximaera(a)gmail.com>; Randy Bush <randy(a)psg.com>; remco van mook <remco.vanmook(a)gmail.com> Subject: Re: RIPE NCC Executive Board Election Task Force Members Of course, that task force was only created to prevent my nomination in the next elections, thank you for proving it. Kind Regards, Elad ________________________________ From: Sergey Myasoedov <kaa(a)net-art.cz> Sent: Wednesday, July 22, 2020 4:50 PM To: Elad Cohen <elad(a)netstyle.io>; Cynthia Revström <me(a)cynthia.re> Cc: Arnold Nipper <arnold.nipper(a)de-cix.net>; Carlos Friaças <cfriacas(a)fccn.pt>; Jan Zorz - Go6 <jan(a)go6.si>; Erik Bais <erik(a)bais.name>; Töma Gavrichenkov <ximaera(a)gmail.com>; Randy Bush <randy(a)psg.com>; kaa(a)net-art.cz <kaa(a)net-art.cz>; remco van mook <remco.vanmook(a)gmail.com> Subject: Re: RIPE NCC Executive Board Election Task Force Members Dear colleagues, The EB Election Task force has been established on Monday, and it took about a day to understand that at least half of the TF members prefer not to be in the same group with Elad Cohen. It was not clearly stated – we just didn’t have enough time for this – but everyone was expected to follow the Code of Conduct for RIPE Meetings. However, Elad clearly said that he is not following the CoC. The Task Force is expected to produce an useful output for the Executive Board and to help clarify the RIPE NCC election procedures. We have a short time to organise several meetings and exchange opinions. Developing and accepting our own CoC means stealing time from ourselves. We should be able to behave in a small group without a rules written in stone. And the Task Force should be a place for a comfortable work, not for fight and defense. I am sorry that this wasn’t true in the very beginning of our work. I would like to prevent resignations from the Task Force. The TF members should not feel any fears and threats caused by any other TF member. And all this above and the motion from the TF members for removal led me to a decision to dismiss Elad Cohen from the RIPE NCC Executive Board Election Task Force, effective immediately. With Best Regards, Sergey Myasoedov RIPE NCC Executive Board Election Task Force Chair

2 2

Re: [members-discuss] Administrative procedures within RIPE NCC: Any way to soften it ?
by Athina Fragkouli 25 Jul '20

25 Jul '20

Dear Clement, all Thank you for sharing your concerns and apologies for the late reply. We recognise that providing documentation can take a lot of time and keeps you from your real work. However, we need to be clear on exactly who the resource holder is - to prevent hijacks as you note, but also to avoid legal disputes over the resources in the future. This is a risk when company structures are changing or companies are being spun off, and untangling this to see what is actually changing is not always straightforward. Our transfer procedure was updated after a board resolution in 2016 which stated that all transfers, including mergers and acquisitions, must follow the RIPE transfer policy unless supported by documentation from a national authority[1]. This closed a well-known and abused loophole that members were using to transfer resources outside of the policy. The other important point to note here is that under Dutch law, memberships are not transferrable. What we therefore need to establish in these cases is whether a separate legal entity is receiving the resources. If this is indeed what's happening, they will need to become a member. This is because a non-member cannot receive resources and they are not able to assume the membership of the company they are getting the resources from. Of course, if the receiving party is already a member, they will not have to open an additional membership to acquire the resources. Finally, it is worth noting that we have invested quite a lot of effort into improving our due diligence processes. We have recently developed an approach that should ease a lot of the burden for members in terms of documentation. We will share some more details about this in the near future. Regards Athina Fragkouli Chief Legal Officer RIPE NCC [1] RIPE NCC Members and Multiple LIR Accounts - Decisions and Next Steps: https://www.ripe.net/ripe/mail/archives/ncc-announce/2016-April/001031.html

6 6

EB Election Task Force and Moderating members-discuss
by Christian Kaufmann 24 Jul '20

24 Jul '20

Dear members, I would like to first address the issues around the Executive Board Election Task Force. We decided to appoint all those who volunteered for the task force. We did so to be as inclusive as possible and to ensure a wide variety of views from as diverse a group of people as possible. The board has no issues with any views regarding the election process, and it is right to give people the benefit of the doubt. However, behaviour on the mailing list and on the task force must adhere to the RIPE Mailing List/RIPE Forum Code of Conduct, which is available at: https://www.ripe.net/participate/mail/ripe-mailing-list-ripe-forum-code-of-… The board has delegated to the task force and its chair the powers to warn and if necessary remove members of the task force who do not adhere to the code of conduct. I also regret to inform you that the Executive Board has decided to again place the members-discuss mailing list in moderation. We had hoped that lifting moderation outside an election campaign would be possible, but this has proven not to be the case. Moderation will remain in place at least until the next RIPE Meeting takes place. Emails will not be approved to be posted to the list that do not meet the requirements of the code of conduct or that do not meet the intended purpose of providing members with a means to discuss membership issues among themselves. The moderators of the list will be one member of the Executive Board and one member of RIPE NCC staff. Mails will be moderated during office hours. A separate archive of all mails including those rejected by the moderators will be available for transparency at: https://www.ripe.net/ripe/mail/archives/members-discuss-unmoderated/ Regards, Christian Kaufmann Executive Board Chairman RIPE NCC

3 3