- ripe-list - mailman.ripe.net

The RIPE Chair Team Reports: September 2023
by Mirjam Kuehne 05 Sep '23

05 Sep '23

Dear colleagues, Continuing to increase RIPE's visibility, taking part in industry events, keeping up with policy discussions, and preparing for a RIPE Meeting in Rome - as we go into September, we report on the work ahead in the months to come: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-septe… Kind regards, Mirjam Kühne RIPE Chair

1 0

Register Now for RIPE 87!
by RIPE NCC Event Team 04 Sep '23

04 Sep '23

Dear colleagues, You can now register for the RIPE 87 Meeting at: https://ripe87.ripe.net/attend/register/ RIPE 87 will take place at Sheraton Rome Parco de' Medici from 27 November till 1 December 2023. ------------- Ticket Options ------------- Week ticket: EUR 400 Day ticket: EUR 130 Student (week) ticket: EUR 50 You can find more information about ticket options at: https://ripe87.ripe.net/attend/register/ ------------- Call for Presentations ------------- The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of Feather sessions), workshops, tutorials and lightning talks at RIPE 87. Proposals must be submitted for full consideration no later than 18 September. More information at: https://ripe87.ripe.net/submit-topic/cfp/ ------------- Call for Sponsors ------------- Supporting a RIPE Meeting through sponsorship gives your organisation fantastic exposure in the global Internet community. Get in touch with the RIPE Meeting team if you are interested in sponsoring RIPE 87: https://ripe87.ripe.net/sponsors/become-a-sponsor/ ------------- RIPE Fellowship ------------- If you are in the RIPE NCC service region and need financial assistance to attend RIPE 87, please consider applying for a RIPE Fellowship. We will cover travel, accommodation and a full-week meeting ticket. Apply before 11 September at: https://www.ripe.net/participate/ripe/ripe-fellowship ------------- RACI ------------- The RIPE Academic Cooperation Initiative (RACI) will cover the cost of the meeting ticket, travel and accommodation for successful applicants to present their research at RIPE 87. Apply before 11 September at: https://www.ripe.net/raci/ ------------- Discounted Room Rates ------------- The Sheraton Rome Parco de' Medici is offering RIPE 87 attendees a discounted room rate, which is subject to availability. Reserve now to avoid disappointment at: https://ripe87.ripe.net/attend/accommodation/ ------------- On-site Childcare ------------- We're making it easier for parents to fully participate in the RIPE Meeting by offering professional, on-site childcare at the meeting venue for children aged 6 months to 10 years. Space is limited, so be sure to register soon to confirm your child's place. For more information, visit: https://ripe87.ripe.net/attend/diversity/childcare/ ---------------- Important Dates and Deadlines ---------------- RACI: 11 September RIPE Fellowship: 11 September RIPE 87 CfP: 18 September RIPE 87: 27 November till 1 December Discounted hotel rooms: First come, first served – limited rooms available On-site childcare: First come, first served – limited places available More information on RIPE 87 can be found at: https://ripe87.ripe.net/ Track the #RIPE87 hashtag on social media for the latest updates. See you in Rome! Kind regards, RIPE 87 Meeting Organisation Team

1 0

NRO NC Nominations 2023: Call to Fill Two Seats
by Hans Petter Holen 04 Sep '23

04 Sep '23

Dear colleagues, This is a call for nominations to fill two seats on the Number Resource Organization Number Council (NRO NC). A single list of nominees will be used to fill both seats. We encourage those interested to familiarise themselves with the work of the NRO NC, and to reach out to current or former NRO NC members to understand the workload and responsibilities involved. To read more about the NRO NC and the election process, please see: https://www.ripe.net/nro-nc-nov-2023 ---------------------------- About the NRO NC ---------------------------- The NRO NC performs the role of the Address Supporting Organization Address Council (ASO AC), including: - Overseeing the Global Policy Development Process. - Providing recommendations to the ICANN Board concerning the recognition of new RIRs. - Nominating individuals to serve in the ASO’s two seats (Seat 9 and Seat 10) on the ICANN Board of Directors and other ICANN bodies. - Advising the ICANN Board on Internet number resource allocation policy, in conjunction with the RIRs. - Developing procedures for conducting business in support of their responsibilities, in particular, for the appointment of an ASO AC Chair and definition of the Chair’s responsibilities. For more information about the ASO AC, please see: https://aso.icann.org/aso-ac/ ---------------------------- Nomination Process ---------------------------- Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on Monday, 30 October 2023. All confirmed nominations will be listed on the RIPE NCC website by Monday, 6 November 2023. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other people can express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. The nomination process is available at: https://www.ripe.net/nro-nc-nov-2023/nro-nc-nomination-process ---------------------------- Seat 1: Executive Board Appointment ---------------------------- The RIPE NCC Executive Board will select a candidate from the list of nominees to fill the first seat for a three-year term, starting in January 2024 and ending on 31 December 2026. The selected candidate will then be removed from the list of nominees, and the remaining nominees will be eligible for election for the second seat. This post is currently filled by Hervé Clément whose term expires on 31 December 2023. I would like to thank Hervé for his time spent both as representative for the RIPE community and as chair of the NRO NC. ---------------------------- Seat 2: Election ---------------------------- The second seat will be filled by an election held during RIPE 87 from the remaining pool of eligible nominees. The election is to fill the seat for the remainder of the three-year term started by James Kennedy in January 2023 and ending on 31 December 2025. The candidate elected will therefore serve on the NRO NC for two years of the three-year term. James is stepping down from his position on the NRO NC to take on his new role as the RIPE NCC's Chief Registry Officer. I would like to thank James for having represented the RIPE community on the NRO NC/ASO AC from 2022-2023, and also welcome him back to the RIPE NCC. Regards, Hans Petter Holen Managing Director and CEO RIPE NCC ------------------- Important Dates ------------------- 30 October 2023: Deadline for NRO NC nominations 6 November 2023: Deadline for all confirmed nominees to be posted on the RIPE NCC website 27 November 2023 (Latest): Board appointment announced 27 November-1 December 2023: Election to fill one NRO NC seat during the RIPE 87 Meeting 1 December 2023: Announce election results at closing plenary of RIPE 87

1 0

Updated NRO NC Election Process (v2) and Preparation for NRO NC Elections at RIPE 87
by Mirjam Kuehne 01 Sep '23

01 Sep '23

Dear colleagues, This mail has two - related - parts: 1. Updated NRO NC Election Document v2: Review Deadline 25 September 9:00 UTC 2. Candidate eligibility criteria for NRO NC Elections at RIPE 87 1. Updated NRO NC Election Document v2 Earlier this year, we published a revised version of the election process for the Number Resource Organization (NRO) Numbering Council (NC) [1] and received a number of useful suggestions and comments. In this new version [2], we made some changes based on the comments received: - We removed the general description of the NRO and the tasks of the NC members and published this information separately on the website [3]. - We strengthened the candidate eligibility criteria. - We strengthened the voter eligibility criteria. - We moved the section about the IANA Numbering Services Review Committee to the end of the document. - We added References, Provenance and Document History as appendices. If you have any more comments, questions, suggestions, please send them to this list or to me directly before 25 September 2023, 9:00 UTC. Statements of agreement are of course also welcome. 2. Candidate eligibility criteria for NRO NC Elections at RIPE 87 In his mail from 16 August 2023, Hans Petter Holen announced that James Kennedy will start as Chief Registry Officer at the RIPE NCC [4]. James will step down from his position as a member of the NRO NC. This means James' seat will become available and we will organise elections at RIPE 87 in November. The RIPE NCC will issue a call for nominees in the next few days. I propose that we already implement the improved candidate eligibility criteria as described in the Draft NRO NC Election document since this was strongly suggested by the community after the last NRO NC elections and there were no comments on this part of the draft document. Kind regards, Mirjam Kühne RIPE Chair [1] Draft NRO NC Election Process v1 https://www.ripe.net/publications/docs/ripe-documents/other-documents/nro-n… [2] Draft NRO NC Election Process v2 https://www.ripe.net/publications/docs/ripe-documents/other-documents/nro-n… [3] About the NRO NC https://www.ripe.net/participate/internet-governance/internet-technical-com… [4] James Kennedy Appointed as Chief Registry Officer https://www.ripe.net/ripe/mail/archives/ripe-list/2023-August/002988.html

2 2

New IAB Technical Program: Environmental Impacts of Internet Technology (EIMPACT)
by Vesna Manojlovic 28 Aug '23

28 Aug '23

Dear colleagues, in the spirit of cooperation between similar technical communities, please find here an announcement for a new IAB Technical Program: "Environmental Impacts of Internet Technology (EIMPACT) Program" For additional information, please contact the Program Leads: • Suresh Krishnan <suresh.krishnan(a)gmail.com> - IAB • Jari Arkko <jari.arkko(a)piuha.net> Mailing list: • Address: e-impact(a)ietf.org • To subscribe: https://www.ietf.org/mailman/listinfo/e-impact • Archive: https://mailarchive.ietf.org/arch/browse/e-impact/ Program Page: https://datatracker.ietf.org/group/eimpact/about/ Program Description: The E-Impact Program is a venue for discussing environmental impacts and sustainability of Internet technology. Within this scope, the program looks at trends, issues, improvement opportunities, ideas, best practices, and subsequent direction of work related to Internet technology, architecture, and operations, including visibility and efficiency on energy and other environmentally-impacting attributes. In particular, the group focuses on Internet architecture's role in these topics. The program targets topics not yet progressed into concrete standards or research efforts in the IETF or IRTF while also being a coordination point for work across multiple WGs/RGs, and a venue to highlight ongoing work in the IETF/IRTF as well as external SDOs. The program will use the existing E-Impact mailing list [2] as the venue for discussions. The program's progress and the quality of discussion may point to the need to organize additional workshop(s) to continue the 2022 IAB workshop on the Environmental Impact of Internet Applications and Systems [1]. The program may work on documents that analyze areas where Internet technology faces challenges related to the program's topics or provide architectural guidance. Potential examples of such documents include ones that describe sustainable network architectures, and those that document tradeoffs between environmental impacts and other characteristics such as performance and availability. Publishing any document as an RFC will be at the discretion of the IAB. The program intends to have regular virtual meetings along with periodic hybrid meetings that are co-located with in-person IETF meetings. The program is open to all interested participants, and its meetings will be publicly announced. References: [1] https://datatracker.ietf.org/group/eimpactws/about/ [2] https://www.ietf.org/mailman/listinfo/e-impact Regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 0

James Kennedy Appointed as Chief Registry Officer
by hph＠ripe.net 16 Aug '23

16 Aug '23

Dear colleagues, After an extensive search, I am pleased to announce the appointment of James Kennedy as the RIPE NCC’s new Chief Registry Officer. James will begin his new role in September. James has been in our industry for over 15 years and many of you will know him from his extensive involvement in the RIPE community. He was previously co-chair of the RIPE Database Requirements Task Force and is currently serving on the NRO Number Council and as co-chair of the Address Policy Working Group. He has also worked as an IP Resource Analyst with the RIPE NCC in the past. His experience and skills will make for a great addition to our leadership team. James and I have agreed that he will step down from his roles in the Address Policy Working Group and the NRO Number Council before starting at the RIPE NCC, and he will be sure to complete a proper handover with his successors. I also want to thank Felipe Victolla Silveira for his dedication and hard work in leading our registry operations over the past five years. Among other things, he is responsible for significantly improving our internal processes and the service levels we provide to members, and he played a crucial role in our response to a number of critical issues over this period, including sanctions and the war in Ukraine. Please join me in welcoming James to his new position. Kind regards, Hans Petter Holen Managing Director and CEO RIPE NCC

2 1

Apply now for Fellowship and RACI grants for RIPE87
by Vesna Manojlovic 14 Aug '23

14 Aug '23

Dear colleagues, The RIPE NCC is accepting applications for RIPE Fellowship and academics to attend RIPE 87, in Rome, from 29 November to 2 December 2023. *The application deadline is Tuesday, 11 September 2023.* You can read more about the RIPE Meeting at: https://ripe87.ripe.net/ ----------- RACI ----------- RIPE Academic Cooperation Initiative (RACI) is supporting talented academics in the field of Internet technology. Successful applicants receive complimentary tickets, accommodation and travel to the meetings and the opportunity to present their research. To apply, submit a short abstract and draft slides via: https://www.ripe.net/participate/forms/apply/raci-application-form-2023/ More information: https://www.ripe.net/raci Subscribe to the RACI list: https://www.ripe.net/raci/mailing-list ----------- RIPE Fellowship ----------- Having participants with diverse backgrounds, expertise, opinions and experiences enriches the RIPE community. With the RIPE Fellowship, we aim to create opportunities for individuals from underrepresented regions, minority backgrounds, or others who would otherwise be unable to attend without funding, to participate in the RIPE Meetings. The RIPE Fellowship covers the cost of a meeting ticket, travel and accommodation for successful candidates in the RIPE NCC service region. Apply: https://www.ripe.net/participate/forms/apply/ripe-87-fellowship/ More information: https://www.ripe.net/fellowship ----------- We encourage our long-standing community members to share this announcement with others who could benefit from these opportunities. ----------- Warm regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 1

Re: [ripe-list] Last Call for Draft Document: RIPE NCC Staff Participation in the RIPE Community
by denis walker 04 Aug '23

04 Aug '23

Hi Mirjam Sorry for yet another long email, but this is an important issue. How RIPE NCC staff talk to the community and the extent to which they are involved in community activities has always been an internal matter for the RIPE NCC to determine. Historically, different managers had different views on how their staff get involved. Now you want to formalise it and define this in a RIPE document, it is open for the community to have their say. I partially support the idea of RIPE NCC staff participating in RIPE activities 'if they choose to do so'. The relationship between the RIPE NCC and the RIPE community is complex. I don't think such a brief and vague document can address this issue. Particularly considering the perceived neutrality of the RIPE NCC as a secretariat and executive body to the RIPE community. As I pointed out in my previous comment, there are no safeguards written into this document. If a member of staff expresses a personal opinion which goes against company policy or (senior) management views, or impacts on company plans, that member of staff must not be subject to any internal disciplinary procedures. Also members of staff must not be subjected to any pressure to (not) say something in public or to (not) take up a community position, for example a WG chair, because it is considered by the RIPE NCC to be in the interests of the company. It has also been mentioned that there is a (private?) internal document on how staff can/should/must engage with the community. In the interests of openness and transparency, that internal document should be published as a RIPE NCC procedural document. Otherwise the community doesn't know the extent to which staff members are able to discuss issues with them in public. Once a staff member has made a comment, the thread may further develop until they find themselves with a conflict of interest between the direction the discussion is now going in and this internal set of rules or guidelines. Any RIPE community member may find themselves in a conflict situation between their personal view and that of their employer. But the fact that the RIPE NCC is the secretariat for the RIPE community and the executive body who implement and enforce RIPE policies may elevate such conflicts to a different level. I also noticed that this document puts the responsibility for avoiding such conflicts onto the staff members, "RIPE NCC staff need to act sensibly", "RIPE NCC staff shall take care". The tone of this document is suggesting that RIPE NCC staff will be allowed, even encouraged, to become more involved in RIPE community matters in the future, "how RIPE NCC staff can and should participate in the RIPE community". In the past such personal involvement seems to have either been discouraged or at best undefined or managed, for most of the staff. It is very rare to see a comment on a mailing list from a staff member who is not a manager, except for technical or legal announcements or responses to direct questions (which may need to be approved by a manager). In fact I have looked back at the archives for all RIPE mailing lists for this year and there are no such comments from any staff anywhere on any list. This new encouragement, by the RIPE NCC CEO, for RIPE NCC staff to freely engage with the RIPE community in public discussions and be more involved in community activities may therefore be considered as a change in the working conditions of the staff. Particularly in view of the potential for conflicts and the responsibility being on the staff to avoid such conflicts and no specified protection for staff if a conflict does arise. I believe this falls under Article 27 section d of the Dutch Works Council Act https://wetten.overheid.nl/BWBR0002747/2023-02-18#HoofdstukIVA_Artikel27 The CEO may need consent from the Works Council at the RIPE NCC in order to implement this change in attitude and responsibility of the staff. The Works Council should seek confidential feedback from staff on how they feel about this potential change to their working conditions and responsibilities. Staff may need some training on how to engage with the community, avoiding conflicts, given the unique relationship, or how to address (the perception of) such conflicts if they should arise. Such a training scheme is also subject to Article 27 section f. If any new regulations need to be considered to protect staff from any consequences of conflicts if they follow this new encouragement to freely engage with the community, that may be subject to Article 27 sections j, g and e. So the RIPE NCC Works Council really needs to take a look at this. The bottom line is that encouraging staff to speak openly and publicly with the community has both benefits and risks. Staff have access to information that the public, and members, don't have. They can see the bigger picture and trends and practises in areas like resource allocations and usage patterns and ways in which the RIPE Database may be (mis)used. They can (and do) analyse data that the public can't even see. Sometimes the line between what you know from public data and what you know from working at the RIPE NCC can get blurred. Either all comments must be approved by management. Or staff must be allowed to speak openly and freely, expressing their personal views, without any sanctions, accepting that sometimes mistakes will be made and lines crossed. Daniel often comments on issues and makes it clear he is speaking personally and not for the RIPE NCC. But Daniel is in a privileged position. Will all staff be given the same privilege to express personal views? If they are expected to only express a collective company view then they may as well just appoint a company spokesperson to express that collective view. The rest of the staff don't need to be involved. If a staff member is a WG chair can they operate completely independently from any collective company view, even if that means opposing a company view if that is in the best interests of the WG, without any penalty? Encouraging staff to be more involved in RIPE community activities is a sensitive issue for the staff. It needs more than a couple of paragraphs and some vague principles. This document looks to have been written from a community perspective, "welcomed by the RIPE community". Is it welcomed by the staff? Has anyone asked them? Works Council or Senior Management? Or has it just been assumed the staff welcome being in both camps? Do staff want to be able to put forward an idea, argue strongly in favour of it, implement it, then take the blame if it is not right? I've been there and done that and it's not a nice place to be. Finally I would like to comment on the principles in this document. I have said many times...wording in RIPE documents is important. I am a native English speaker and an analyst with OCD, so I do see things in words more easily. But the NCC has a whole team of professional, English speaking, communications experts. Perhaps they are not used now to review these docs. Your principle No 2 "RIPE NCC staff expertise is valuable to and welcomed by the RIPE community." cannot be a recommended principle. It can be a supporting fact. But if you recommend, as a principle, that staff expertise is welcomed by the community, this becomes an instruction to the community that they must welcome this expertise. That is what these words actually say. Lastly, your principle No 1 may have unexpected consequences. "RIPE NCC staff are part of the community and may participate in RIPE activities on the same terms as anyone else.". You make no exceptions here, "same terms as anyone else". So a RIPE NCC staff member can be part of a task force, be a WG chair, be the RIPE chair (if it is no longer a full time, paid position), be a member of the next NomCom, make policy proposals, argue for or against policy proposals. So consider this possible scenario. A staff member could make a policy proposal. Other staff members could argue strongly in support of this proposal. Consensus could be declared by a WG chair who is a staff member. Any appeal would end up with the RIPE chair who could also be a staff member. The policy will then be implemented and enforced by the RIPE NCC staff. All of these people could be influenced by RIPE NCC internal company policy and allowed time within working hours to do all this. They are all FTEs paid for by the RIPE NCC membership and expected to be following RIPE activities anyway, perhaps more closely than FTEs of member companies. This is a theoretical scenario. But it does raise the question of how independent and neutral will the RIPE NCC be seen as, if it's staff can be so involved in the bottom up policy process at every level, to the point of dominating and controlling, considering the often lack of other community member involvement. I think some more thought is needed for this document. cheers denis co-chair DB-WG member of RIPE community former RIPE NCC staff member former chair RIPE NCC Works Council (for full disclosure) On Fri, 30 Jun 2023 at 12:00, <ripe-list-request(a)ripe.net> wrote: > > From: Mirjam Kuehne <mir(a)zu-hause.nl> > > Dear colleagues, > > The deadline for comments for the draft document “RIPE NCC Staff > Participation in the RIPE Community” [1] ended. Many thanks for all the > comments sent to the RIPE list. > > There was a lot of support for the document, especially for the > principle that RIPE NCC staff are part of the RIPE community. It is > great to see that RIPE NCC staff is welcome and valued by community > members. > > There were some suggestions to explicitly allow RIPE staff to take on > certain community roles. Other community members disagreed and cautioned > that this could lead to conflict of interests. Hans Petter Holen > clarified that there are also RIPE NCC internal guidelines for staff. > > There were no concrete suggestions for changes in the document. > I believe that the current version is ready for adoption and publication > as a RIPE Document and would like to confirm this. > > This is therefore a LAST CALL for comments, to expire on Monday 10 July > at 06:00 UTC (08:00 Amsterdam time). Unless there are some substantial > comments, I look forward to declaring consensus and arranging > publication shortly after that. > > Kind regards, > Mirjam Kühne > RIPE Chair > > [1] RIPE NCC Staff Participation in the RIPE Community > https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ripe-list

12 17

New on the RIPE Labs Podcast: Mapping the Geopolitical Internet
by Alun Davies 01 Aug '23

01 Aug '23

Dear colleagues, In the latest episode of the RIPE Labs podcast, I talk to Louis Pétiniaud about the work he and his colleagues at GEODE have been doing to map the dialectical relationship between the development of the Internet and various geopolitical forces: https://labs.ripe.net/author/alun_davies/mapping-the-geopolitical-internet/ As well as giving us a glimpse into specific power relationships between countries and their influence on the growth of the Internet, the project is a fascinating example of how experts from inside and outside the technical community can build common languages and tools to examine how their domains influence each other. I hope you enjoy the conversation! Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Thank you and goodbye
by ntrenaman 28 Jul '23

28 Jul '23

Dear colleagues, After 16 years I’ll be leaving the RIPE NCC. From my first day in Registration Services until my last day in the RPKI team, it has been an honour and pleasure to work with all of you. The RIPE NCC gave me the opportunity to grow as a person and to keep learning every single day. It also gave me the privilege to travel and teach, to meet thousands of people in our community. Some of you became friends for life. I learned from every trip, and from every person I met, making me a proud ambassador of the RIPE NCC. With the RPKI team, we have set high standards for trust, transparency and security for both RPKI and the rest of RIPE NCC. I'm very proud of this achievement and I will miss working with this dedicated, smart and wonderful team. The RIPE community means a lot to me. So many people volunteer their time to improve the Internet in different ways. I’m grateful for all your work, time and effort. My work with NLNOG and Keep Ukraine Connected will obviously continue and I’m deeply passionate about what we work to achieve in both of those community initiatives and their force for good. Also, I will continue promoting IPv6 adoption wherever I can (by now, that’s in my DNA 😉). My last day will be 31 July. After that, you can always reach the RPKI team at <rpki(a)ripe.net>. Best regards, Nathalie Trenaman

7 6