May 2023 - ripe-list - mailman.ripe.net

The Future of Discussion Lists
by Leo Vegoda 08 Jun '23

08 Jun '23

Dear RIPE community, At yesterday’s community plenary I asked whether mailing lists are sustainable as our main communication channel. For those who were not able to attend, the slide and a recording are available here: - https://ripe86.ripe.net/wp-content/uploads/presentations/12-Mailing-Lists-R… - https://ripe86.ripe.net/archives/video/1115 I am obviously concerned that discussion lists might not serve us with fidelity in the future. If that is the case, I want us to manage any change we need to make. We should not be bounced into rapid change. There was more discussion than I expected. I’m sending this message to ask the questions: - Am I wrong? Are e-mail discussion lists a sustainable communication channel for the foreseeable future? - Are e-mail discussion lists an acceptable technology to people joining the industry? The text below is similar to something I shared with the WG Chairs several months ago. Kind regards,. Leo ripe-781 describes four fundamental principles supporting our policy development process. The first two principles are openness and transparency. Changes in the treatment of e-mail by large industry players presents a challenge to these two principles. In 1992, when ripe-001 was published, anyone could run e-mail services on any Internet infrastructure they could use. It is now far more difficult to run e-mail services. Technology developments, like DMARC, have made discussion mailing lists less effective. Validation failures increase the probability of messages being treated as junk. Subscribers to RIPE's discussion lists will miss messages when their e-mail services provider treats them as junk. When a legitimate message to a RIPE discussion list is treated as junk the sender's voice has been moderated by a third-party mail provider. RIPE's transparency is diminished when its discussion lists are subjected to gatekeeping by third-party mail providers. In 1992, e-mail was an improvement to postal services and telephony protocols. In 2023, we have a wide choice of communication protocols and platforms. I believe that new protocols and platforms are preferred over e-mail by potential participants in RIPE at the start of their careers. We want these people to take part in RIPE. They are the future of coordination for the operators of IP networks in Europe and the rest of the world. We must offer all current and potential participants in RIPE an effective set of tools. Any tools we use must support the principles of openness and transparency. An ideal set of tools might have features like this: 1. An open protocol available for implementation by anyone. 2. Free(ly available) software implementations for popular operating systems (Android, iOS, Linux, macOS, and Windows). 3. Allows a user to choose to have activity pushed to them. They must not be forced to maintain a login to be informed of activity they are interested in. 4. A public archive that cannot be retrospectively edited (barring exceptional situations). While the technology choices need to support the principles of openness and transparency, they do not need to do all the work. Announcements, blog posts, and other kinds of communications can be built into our processes. The combination of technology and process can make the whole more effective.

29 36

RIPE86 results
by Alex de Joode 02 Jun '23

02 Jun '23

RIPE86 has closed, so first congratulations to Raymond, Maria and Harald! Second thanks to the RIPE NCC for organising a marvellous event (even if in Rotterdam ;) and a lunch without nasi and sateh :( ). This time the event venue and hotel's were separate, as this also was the largest RIPE ever, we might see this a new way to do meetings. Personally I feel having a 'event hotel' gives me more of a community feeling. Would be nice if we could have some data concerning this (do ppl not care as some might opt for cheaper hotels anyways, do they have a preference for one/other). Third, as to the GM results, could the RIPE NCC give some background on the actual numbers for the votes of the charging scheme? Did option D receive a clear majority, or only in the run-off? This might be very relevant for finding the way forward. Thanks, Alex -- IDGARA | Alex de Joode | alex(a)idgara.nl | +31651108221

16 20

Re: [ripe-list] The Future of Discussion Lists
by Petra.Zeidler＠dlr.de 31 May '23

31 May '23

Hi, Maria Matejka wrote: > There may be also different approaches altogether. We may be missing e.g. some visually impaired or dyslectic people, who often rely more on sound than on text ? yet keeping in mind that sound may be on the other hand a showstopper for not only hearing-impaired but also e.g. for lots of ADHD people. I'm not proposing anything specific here, just trying to shed some light on other factors we haven't yet covered. I have a different "disability": I read legalese, and I believe that it is intent to actually take away rights I usually have if I am asked to explicitly sign them away. Thus, I used to have a Discord account, but I deleted it after a Terms change not too long ago. Now, if I don't participate because I don't like the terms Discord demands, that is probably not that great a loss for the RIPE community. OTOH, if by the last terms of Discord I saw you discuss/create a new policy document on Discord, you afterwards cannot publish it anywhere else because Discord owns copyright for the thing. Is that useful? Also, I can simply choose to not take part in RIPE processes, but for other people, it's their job. Asking them to accept the terms of a single third party (i.e. with no ability to choose a different set of terms with a different supplier) to be able to do it does not seem like progress to me. (That is a suggestion to use as communication add-on or replacement something where RIPE can set the terms). Regards, Petra Zeidler PS: Usenet has been reinvented, badly, so many times.

1 0

New addresses for b.root-servers.net
by Robert Story 30 May '23

30 May '23

USC/ISI is renumbering both its IPv4 and IPv6 addresses for b.root-servers.net on 2023-11-27. Our new IPv4 address will be 170.247.170.2 and our new IPv6 address will be 2801:1b8:10::b. USC/ISI will continue to support root service over our current IPv4 and IPv6 addresses for at least one year (until 2024-11-27) in order to provide a stable transition period while new root hints files are distributed in software and operating system packages. We are renumbering to increase the resilience of the Root Servers System by further diversifying the number of Regional Internet Registries (RIRs) that have allocated IP addresses to Root Server Operators. Our addresses will be the first in the Root Server System to have been allocated by LACNIC and our routes will be verifiable through LACNIC’s Resource Public Key Infrastructure (RPKI) Trust Anchor Location (TAL). We thank LACNIC for helping make this renumbering possible, and ARIN for supporting our prior addressing assignments. The LACNIC announcement, with English, Spanish and Portuguese translations, can be found on their website here: https://www.lacnic.net/6868/1/lacnic/lacnic-asigna-recursos-de-numeracion-a… Please direct any comments or questions to b-poc <at> isi.edu. Regards, Robert P.S. Apologies to anyone receiving multiple copies of this announcement. -- Robert Story USC Information Sciences Institute <http://www.isi.edu/> Networking and Cybersecurity Division

1 0

Re: [ripe-list] The Future of Discussion Lists
by Mathias Westerlund 27 May '23

27 May '23

I personally would like to see more interactive alternatives be officially recognized, while mail is great for archival and for a-sync communications it is dated and not very alluring to newer players in the market. Another upside is of course that pretty much everyone have mail access while anything else would require agreeing across the community on a tool we are all okay with. But my opinion is strongly that i would like to see something complement the use of mailing lists but not replace. Regards, Mathias W. West digital Management AB. --------------------Original message-------------------- From: Leo Vegoda <leo(a)vegoda.org> Sent: Friday, May 26, 2023 10:07 To: ripe-list(a)ripe.net Subject: [ripe-list] The Future of Discussion Lists Dear RIPE community, At yesterday’s community plenary I asked whether mailing lists are sustainable as our main communication channel. For those who were not able to attend, the slide and a recording are available here: - https://ripe86.ripe.net/wp-content/uploads/presentations/12-Mailing-Lists-R… - https://ripe86.ripe.net/archives/video/1115 I am obviously concerned that discussion lists might not serve us with fidelity in the future. If that is the case, I want us to manage any change we need to make. We should not be bounced into rapid change. There was more discussion than I expected. I’m sending this message to ask the questions: - Am I wrong? Are e-mail discussion lists a sustainable communication channel for the foreseeable future? - Are e-mail discussion lists an acceptable technology to people joining the industry? The text below is similar to something I shared with the WG Chairs several months ago. Kind regards,. Leo ripe-781 describes four fundamental principles supporting our policy development process. The first two principles are openness and transparency. Changes in the treatment of e-mail by large industry players presents a challenge to these two principles. In 1992, when ripe-001 was published, anyone could run e-mail services on any Internet infrastructure they could use. It is now far more difficult to run e-mail services. Technology developments, like DMARC, have made discussion mailing lists less effective. Validation failures increase the probability of messages being treated as junk. Subscribers to RIPE's discussion lists will miss messages when their e-mail services provider treats them as junk. When a legitimate message to a RIPE discussion list is treated as junk the sender's voice has been moderated by a third-party mail provider. RIPE's transparency is diminished when its discussion lists are subjected to gatekeeping by third-party mail providers. In 1992, e-mail was an improvement to postal services and telephony protocols. In 2023, we have a wide choice of communication protocols and platforms. I believe that new protocols and platforms are preferred over e-mail by potential participants in RIPE at the start of their careers. We want these people to take part in RIPE. They are the future of coordination for the operators of IP networks in Europe and the rest of the world. We must offer all current and potential participants in RIPE an effective set of tools. Any tools we use must support the principles of openness and transparency. An ideal set of tools might have features like this: 1. An open protocol available for implementation by anyone. 2. Free(ly available) software implementations for popular operating systems (Android, iOS, Linux, macOS, and Windows). 3. Allows a user to choose to have activity pushed to them. They must not be forced to maintain a login to be informed of activity they are interested in. 4. A public archive that cannot be retrospectively edited (barring exceptional situations). While the technology choices need to support the principles of openness and transparency, they do not need to do all the work. Announcements, blog posts, and other kinds of communications can be built into our processes. The combination of technology and process can make the whole more effective. -- 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

2 1

RIPE 86 Highlights and Thank You!
by Mirjam Kuehne 26 May '23

26 May '23

Dear colleagues, RIPE 86 ended with a total of 863 attendees checked in onsite in Rotterdam and 501 unique participants on Meetecho across the meeting week, with more joining in via the livestream and YouTube. Thank you all for making this RIPE Meeting such a success! We were happy to see active participation at this meeting from both online and onsite participants. We would like to thank all the speakers, Working Group Chairs, the Programme Committee and sponsors for their contributions. It was also great to hear from our younger attendees at the Diversity in Tech session. Over the past week, we have had several plenary sessions and lightning talks, Working Group sessions followed by the Closing Plenary. You can find some highlights from the day in the Daily Meeting Blog at: https://labs.ripe.net/author/ripe-ncc/ripe-86-daily-meeting-blog/ All presentations from the meeting are archived: https://ripe86.ripe.net/archives/ Save the date for RIPE 87, taking place in Rome, Italy from 27 November – 1 December 2023. You can get updates via the RIPE Discussion list, social media and the RIPE 87 website: https://ripe87.ripe.net Best regards, Mirjam Kühne, RIPE Chair, and Niall O’Reilly, RIPE Vice-Chair

1 0

Take the RIPE NCC Survey 2023
by fergalc＠ripe.net 24 May '23

24 May '23

Dear colleagues, The RIPE NCC Survey 2023 is now available online. https://www.ripe.net/survey Your participation is important to provide valuable feedback on the RIPE NCC’s services and activities. We want to know how we can best meet your needs, what direction the RIPE NCC should take in the coming years, and what challenges you face in your work that we can help with. We encourage you to take the time to complete it, and please encourage your colleagues and contacts to participate - the more feedback we get, the better we can do. The survey is anonymous and open to both RIPE NCC and RIPE community members in ten languages: Arabic, English, Farsi, French, Italian, Polish, Russian, Spanish, Turkish and Ukrainian. Prize Draws ----------- To encourage participation, we are giving you the chance to win a prize in our weekly prize draw. Prizes include flights and accommodation to RIPE 87, a Meta Quest 2, Apple Watches SE, and Bose QuietComfort headphones. Any of these gifts can be exchanged for a EUR 250 donation to a charity listed on our website. The earlier you fill out the survey, the more chances you will have to win a prize. If you complete the survey today, you will have six chances to win a prize! If you have any questions about the survey, you can email us at survey(a)ripe.net. You have until 30 June 2023 to participate. Remember, 15 minutes can make a big difference. Best regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

BoF on Tuesday Evening: The Impact of the Latest Developments in Artificial Intelligence on the RIPE Community
by Daniel Karrenberg 23 May '23

23 May '23

Dear colleagues, There will be a BoF on Tuesday evening at RIPE86. I proposed it to the PC like this: "We suspect that many RIPE participants are paying attention to the increased discussions about AI within society as-a-whole. Therefore we propose to reserve a space in the meeting agenda for participants to share their opinions about this and hear the views of their peers. We suggest to consider the impact on the RIPE community as a way to frame the discussion. We do not propose new formal work by the community at this point in time." The goal is an exchange of opinions and ideas as a way for everyone to learn and enhance their own views on the subject. We do not want long monologues and the optimal outcome is a lively and entertaining discussion. Therefore the format will be that of a 'speed discussion'. If at all possible we want to avoid sitting facing the stage but rather in something resembling a circle as far as the layout of the room permits. In order to avoid microphone queues there will be two tokens in the room passed from one speaker to the next. We will not use microphones unless the group is too big. People will get to speak for no more than two minutes each followed by a two minute question and discussion period. If the discussion is fruitful the chair may extend it for another two minutes. Then the next person will get to speak for two minutes, ... . We will have a traffic light clock to keep the time and everyone will strictly respect the timing. We aim for an open and respectful discussion among peers. After the discussion we ask everyone not to reveal who said what to people who have not been present. It is OK to report *what* was said but not *who* said it. If the discussion is as good as we hope, we may publish a short report to the community. I am looking for two or three people to commit to speaking first to get things going. Please contact me off list. Also, if you have suggestions for reading material about the subject, please share them in this thread. I am very much looking forward to see you in the BoF. Daniel RIPE co-founder, first and current employee of the RIPE NCC, speaking only for himself.

4 4

Open Call: IGF MAG Nominations from the Internet Technical Community
by Chris Buckridge 22 May '23

22 May '23

Dear colleagues, With a very active and interesting couple of years ahead for the Internet Governance Forum (and Internet governance more generally), the Internet Technical Collaboration Group (ITCG) is opening a call for volunteers to represent the Internet technical community on the IGF Multistakeholder Advisory Group (MAG). The MAG serves primarily as a Programme Committee for the annual IGF event, while also advising on the strategy and direction of the IGF, and working closely with the Secretariat. Since the early 2000s, the IGF has embodied the UN’s commitment to a multistakeholder approach to Internet governance, ensuring that stakeholders (like the Internet technical community) have a seat at the table and a voice in global governance processes. With some important discussions upcoming (including a 20-year review of the UN World Summit of the Information Society, which gives the IGF its mandate), maintaining a strong commitment to that approach is very important! Details of the open call are available on the ITCG website: https://www.internetcollaboration.org/2023/05/itcg-call-for-nominations-202… The nomination form is here: https://www.internetcollaboration.org/2024-igf-multistakeholder-advisory-gr… I am a current member of the MAG, so please feel free to reach out to me with any questions (or grab me in the corridor during this week’s RIPE Meeting in Rotterdam), particularly about time and work expectations. Best regards, Chris —— Chris Buckridge Advisor to the Managing Director, Global Strategic Engagement RIPE NCC

1 0

RIPE 86 starts today!
by RIPE NCC Event Team 22 May '23

22 May '23

Dear colleagues, RIPE Chair Mirjam Kühne will open the RIPE 86 Meeting in Rotterdam today at 14:00 local time (UTC+2). If you cannot be at RIPE 86 in person, you can follow the meeting online and participate remotely by viewing the live webcast: https://ripe86.ripe.net/live/main/ To stay up-to-date with all RIPE Meeting updates, Follow us on Facebook, LinkedIn and Twitter: @ripemeeting, #RIPE86 Best regards Alexandra Event Organiser RIPE NCC

1 0

BoF on IETF Overview of Technical Work and Hot Topics, Tuesday 17:30
by Mirja Kuehlewind 22 May '23

22 May '23

Hi all, We will hold a BoF on Tuesday evening at RIPE86 about hot topics in the IETF. In this session, we will provide an overview of new and on-going technical work and discussions in the Internet Architecture Board (IAB) as well as new and hot topics in the IETF. The meeting will be held in the Main Room (agenda to be updated), and the time is 17:30-18:30. Example topics that will be covered include: - DNS: Useful error codes, finally? And probing which encrypted DNS protocols are available - IPv6: Registering SLAAC addresses in DHCPv6? - The environment: Can standards organizations reduce the environmental impacts of the Internet? - QUIC: What extensions are being actively worked on? - TLS: Removing the last piece of visible metadata with encrypted ClientHello? - Encrypted networks: Can we manage them? - New work: New WG on time-variant routing & others We look forward to discussions on these topics and other topics of your interest! Also feel free to approach us before or after the session by email or in-person with any further questions about the IETF and the work work of the IETF! See you soon! Mirja Kühlend (IAB Chair), Warren Kumari (OPS AD), Éric Vyncke (INT AD), Jari Arkko (former IAB member)

1 0

[meetings] Call for Hosts for RIPE 89, RIPE 90 and RIPE 91
by RIPE NCC Event Team 22 May '23

22 May '23

Dear colleagues, Are you interested in hosting RIPE 89 from 28 October – 1 November 2024, or RIPE 90 from 19-23 May 2025, or RIPE 91 from 20-24 October 2025? We are looking for organisations within the RIPE NCC service region to submit their proposal for host consideration no later than *18 June 2023*. A RIPE Meeting Host helps with venue scouting, Internet connectivity, social events, finding local sponsors and administrative and on-site support. As a host, we must be able to depend on you to help organise a smooth, professional and top-quality meeting for our attendees. In return, the host organisation enjoys excellent visibility among the RIPE community and the prestige of hosting a RIPE Meeting. Interested? You can find more information at: https://www.ripe.net/ripe-meetings/call-for-host You can send your proposal by *18 June 2023 * to: meeting(a)ripe.net. I look forward to hearing from you. Kind regards, Alexandra Vos Event Organiser

1 0

Introducing the RIPE Code of Conduct Team
by Mirjam Kuehne 19 May '23

19 May '23

Dear colleagues, I am very pleased to introduce to you the new RIPE Code of Conduct Team: Cynthia Revstrom, Franziska Lichtblau, Randy Bush, Maria Stafyla, Saloumeh Ghasemi, Vesna Manojlovic. All team members have been trained and will be available for you during RIPE 86 either in person or online. I am very happy that we have such an excellent team in time for the next meeting. This team will replace the Trusted Contacts who have served the community very well over the last years and who I cannot thank enough for serving in this role. I would also like to thank the RIPE Code of Conduct Task Force who has done an amazing job in working with the community to develop the RIPE Code of Conduct and the accompanying documents. You can find all relevant information including a reporting form and email address on the RIPE 86 website: https://ripe86.ripe.net/attend/code-of-conduct/ All RIPE Code of Conduct related documents are now published as RIPE documents (see below) and also linked from this page: https://www.ripe.net/participate/ripe/code-of-conduct Kind regards, Mirjam Kühne RIPE Chair [1] RIPE Code of Conduct: https://www.ripe.net/publications/docs/ripe-766 [2] RIPE Code of Conduct: Process and Consequences: https://www.ripe.net/publications/docs/ripe-792 [3] RIPE Code of Conduct Team: Appointment and Responsibilities: https://www.ripe.net/publications/docs/ripe-793

1 0

Help for Ukrainian schoolchildren on RIPE86
by Alex Semenyaka 18 May '23

18 May '23

Dear colleagues! The war in Ukraine is still going on, and its effects can be seen in many facets of Ukrainian life. This includes children and teenagers who live in close proximity to a hostile area and, in particular, those who reside in territories that have just been de-occupied. It is vitally important for them to keep up with their studies so that they may have a chance to discover who they are after the war is finished. However, schools are often blown up or bombed, and many teachers have left... Luckily, there is online learning, created back in the days of the Covid-19 pandemic. Though, it requires devices that allow you to connect to streaming courses. At the same time, many of us have old smartphones, tablets, and modest laptops on our shelves that we feel sorry to throw away ("they can still be used somehow!"), but for which there is no use ("they are already too outdated!"). During the RIPE Meeting in Rotterdam, from May 22 to 26, 2023, you will have the opportunity to pass on such equipment to Ukrainian schoolchildren. I will take it to Ukraine and give it to the Ukrainian Borders Foundation ( https://rubezhi.org.ua/en/), for which helping children is one of the main activities. There will be a box near the reception where you can just leave it. Alternatively, you can meet me and hand over the device in person. In particular, I will have a session at the Benefactor Desk where I will answer your questions about this project and where we can discuss any suggestions for its development. Also, I will be at the meeting the entire time, so feel free to approach me in the corridor during any of the breaks. Of course, many people wonder what the requirements are for the devices to be suitable for schoolchildren. That's easy: it must be capable of installing and running *Zoom, Google Meet, and Microsoft Teams*. So if you've stopped using your smartphone because its battery no longer holds a charge, it's fine for this task. For its future owners, mobility is not so important, and the device can work perfectly well from an electrical outlet. In advance, I want to express my gratitude to everyone who will join this project to help the schoolchildren who are now in a very difficult situation. -- Alex Semenyaka

2 1

DNS Hackathon 2023 - open doors for presentations on Sunday 16:00, Ahoy, dock 15
by Jerry Lundström 18 May '23

18 May '23

Hi all, The DNS Hackathon 2023 is just in a few days! Hosted by DNS-OARC, Netnod and RIPE NCC If you're attending RIPE 86 and arriving early, then on Sunday 21st at 16:00 CEST we will open the doors (dock 15) for anyone to come watch the project presentations about the work done over the weekend! Thanks to our sponsors: SIDN, NLnet Labs, Internet Systems Consortium, Gcore and ICANN! /Jerry & Vesna & Miguel

1 0

Re: [ripe-list] ripe-list Digest, Vol 139, Issue 10
by denis walker 18 May '23

18 May '23

Hi guys Maybe a middle ground is worth considering. Where a working group has 2 or 3 co-chairs, perhaps allow RIPE NCC staff to take chair positions but not allow them to be in a majority. That allows a WG to benefit from the deep understanding of RIPE NCC staff, who work full time around many of the issues under consideration, without the RIPE NCC being 'seen' as in control. Whilst this is an interesting theoretical discussion, let's have an injection of the unspoken reality. There are many issues here that few will speak of. Having had one foot in both these camps, let me speak up on behalf of those with no voice. We all live in multiple hierarchies of power and control. Corporate life is just one of them. The RIPE NCC is a corporate body. It has a board, a management hierarchy and a hierarchy of workers. Whilst the RIPE NCC acts as an executive body or secretariat for the loosely defined and very public RIPE community, everyone associated with the RIPE NCC is still subject to the norms of corporate life. WE, as part of the community, are discussing how staff members 'can and should' (words taken from the document) be able to interact with this community. It is notable that no staff member has joined this discussion. Whilst WE are discussing how staff members 'can and should' be able to get heavily involved in policy discussions, maybe staff don't feel able to even join the discussion on the discussion. Regardless of the connection between the RIPE NCC and the RIPE community, as a corporate body the RIPE NCC has corporate policy, strategy, rules, discipline and internal ways of working. All of this covers how the RIPE NCC, as a company and secretariat with staff, interacts with the, often difficult to identify, RIPE community. It says in this draft document "In addition to that, the RIPE NCC may have more detailed internal guidelines for staff participation in the RIPE community and other community work." Unless those guidelines are published in full, as a RIPE NCC procedural document, whatever this draft document says is meaningless as it can all be overruled by these internal guidelines. If the RIPE community is going to define how the RIPE NCC should (be able to) interact with the RIPE community then there must also be a condition that no RIPE NCC staff member should be put under any pressure internally to either be or not be a co-chair of a particular working group. We must also offer 'protected rights' of staff to comment freely in a discussion on a working group mailing list if we want them to act as full members of the community. Obviously they must not disclose any confidential internal information. But they should be allowed to comment freely, expressing their own opinion, in a professional manner, EVEN if that goes against the RIPE NCC company policy. No staff member should be internally disciplined if their public opinion contradicts that of perhaps a more senior member of staff. It is good to have this open discussion, but you must also accept that many staff members will never comment on any mailing list discussion because of the fear of an internal backlash. I was a staff member and I know what can happen if you say the wrong thing in public. I once said something in a presentation at a RIPE Meeting. It had been approved by my manager but left another manager very angry. The immediate and very public consequence of that literally left me in tears at that meeting. Some people who saw me may remember it. The follow up internally was not pleasant either. (Just for clarity, it was a long time ago and all concerned parties have since left the RIPE NCC.) So if we want staff to have this level of involvement with the community then we MUST have a clear buy-in from the senior management team at the RIPE NCC and from the OR (staff workers association). There must be safeguards put in place to protect staff from freedom of speech issues, even if what they say goes against company policy or the plans of any manager. It is not enough to have Hans Petter as a co-author of this document. Anything agreed here can be overruled by the "more detailed internal guidelines for staff participation". In any corporate body, staff know that to keep your job means to keep your mouth shut, never say anything contentious and don't rock the boat. As a retired professional I argue passionately for or against issues on any WG mailing list. I say what I believe to be right, professionally and without any malice. No staff member at the RIPE NCC is ever going to say many of the things I say. Even with safeguards it is not worth the risk. This is an interesting discussion, but don't have too much expectation on the outcome. People are human, they have feelings and fears. Now I would also like to extend this discussion in another direction. Whistle blowing. I am NOT for one moment suggesting there are currently any whistles to blow at the RIPE NCC. But who knows what the future holds. If a member of staff is aware of something wrong, whatever it may be, and they feel strongly that the community should be aware of it, can we have a way for them to anonymously raise the issue? Plenty of food for thought... cheers denis > From: Nigel Titley <nigel(a)titley.com> > To: Joe Abley <jabley(a)strandkip.nl>, ripe-list(a)ripe.net > Cc: > Bcc: > Date: Thu, 11 May 2023 15:01:40 +0100 > Subject: Re: [ripe-list] ripe-list Digest, Vol 139, Issue 9 > > > On 11/05/2023 14:51, Joe Abley wrote: > > > Following on from my previous comment, I think it would be better to > > focus on avoiding *actual* conflicts of interest. I think worrying > > about appearances is what happens when there is a lack of understanding > > of the substance and, in the case of managing a useful and > > productive collaboration between the community and > > NCC-as-secretariat,the substance seems important. > > > > If the goal is to avoid a need for understanding, then it seems like the > > natural solution is that NCC staff should never be allowed to > > participate as members of the community at all. I don't think that is > > necessary or desirable. > > If we had a perfect world then I'd agree with you. However I've been in > this business long enough to know that if there is a faintest chance of > a possible thought of a conflict then someone will complain. > > However, I'm not part of this community any longer in any real sense, > and if people think this isn't important then go for it. > > Nigel >

4 3

RIPE Programme Committee Elections @ RIPE86
by Brian Nisbet 16 May '23

16 May '23

Colleagues, RIPE 86 starts next week and there will be an opportunity to join the Programme Committee for the meetings. The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. There are currently two seats up for election to the RIPE PC. Please send nominations, with a biography, statement of interest and photograph, to pc(a)ripe.net The RIPE Meeting Programme Committee: Appointment, Roles and Responsibilities document - https://www.ripe.net/publications/docs/ripe-763 - provides more information about the composition and roles of the RIPE PC. Nominations for the RIPE 86 PC elections can be sent in from today, Tuesday, 16 May, until Tuesday, 23 May, 15:30 CEST (UTC+2). Please include a recent picture and short biography with your nomination. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can already nominate themselves. We will close candidate nominations on Tuesday, 23 May at 15:30 CEST (UTC+2) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 23 May, 16:00 CEST (UTC+2) until Thursday, 25 May, 17:00 CEST (UTC+2), for community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on the morning of Friday, 26 May, during the Closing Plenary session. This information is replicated on the RIPE 86 website with a breakdown of the important dates: https://ripe86.ripe.net/programme/ripe-pc/become-a-member/ Regards, Brian On Behalf of the RIPE PC Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 5 Exchange Place, IFSC, Dublin D01 EK83, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

The RIPE Chair Reports: Get Ready for RIPE 86
by Mirjam Kuehne 15 May '23

15 May '23

Dear colleagues, The RIPE 86 Meeting begins next week! Please find some information about remote participation, opportunities for social interaction, a call for volunteers and lots more in this new article on RIPE Labs: https://labs.ripe.net/author/mirjam_kuhne/get-ready-for-ripe-86/ Kind regards, Mirjam Kühne RIPE Chair

1 0

ICANN Notice of Board Approval of FY24 Operating Plan and Budget and FY24-28 Five Year Operating and Financial Plan
by Ulka Athale 15 May '23

15 May '23

This message is sent on behalf of the Number Resource Organization (NRO) ICANN has published its operating plan and budget for 2024, as well as its five year operating and financial plan for the years 2024-28. Under ICANN Bylaws, it is possible to file a Rejection Action Petition within a 21-day window, ending on 30 May 2023 at 06:59 UTC. The official notification of the publication of these plans and the objection window is available in the text below. -------------- This announcement can be found at: https://www.nro.net/icann-notice-of-board-approval-of-fy24-operating-plan-a… -------------- ICANN Notice of Board Approval of FY24 Operating Plan and Budget and FY24-28 Five Year Operating and Financial Plan -------------- Dear RIR Community, Under the ICANN Bylaws, delivery of the Secretary’s Notices on 8 May: (1) requires Decisional Participants to “promptly inform their constituents” of the delivery of such notices; and (2) triggers two 21-day Rejection Action Petition Periods, during which an individual may submit a petition to any Decisional Participant, seeking to reject the Board action. ICANN's announcement is available at: https://www.icann.org/en/announcements/details/icann-board-adopts-fy24-28-o… These 21-day periods for (1) FY24 Operating Plan and Budget and (2) FY24-28 Five Year Operating and Financial Plan will end at 23:59 PDT on 29 May 2023, or 06:59 UTC on 30 May 2023. Please refer to Article 2, Annex D of the ICANN Bylaws for additional details on the Rejection Process, including all pertinent deadlines and requirements for Rejection Action Petitions at: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD Any Rejection Action Petition should be sent to the ASO Secretariat at secretariat [at] aso.icann.org before the deadline. ASO Secretariat -------------- Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

Fwd: Sanctions and the Internet report
by farzaneh badii 12 May '23

12 May '23

Hello everyone, We just published the "Sanctions and the Internet" report. This report was commissioned by RIPE NCC and it looked at the effect of sanctions on Internet development and access at the infrastructure level. Here is the link: https://digitalmedusa.org/wp-content/uploads/2023/05/SanctionsandtheInterne… In the next few months, Digital Medusa will try to expand on the report and discuss it with various communities. So if you have feedback or suggestions on any aspect of the report, please let me know. Best regards, Farzaneh

1 0

Re: [ripe-list] ripe-list Digest, Vol 139, Issue 9
by denis walker 11 May '23

11 May '23

Hi guys People who work for a national lottery company are also citizens and residents of the country. But they are usually not allowed to buy lottery tickets. Pro footballers are also football supporters. But they cannot gamble on the outcome of a game. There are many examples of a group of people who act as an executive body or secretariat but cannot make decisions for the larger body they serve. For RIPE NCC staff, my view would be that it is fine for them to be involved in making decisions (openly and transparently) about technical and operational matters and to be actively involved in discussions about policies, which they often have a deep understanding of. But to determine the outcome of policy discussions and setting the policies that govern those operations, which they then implement, may be crossing the line on conflict of interest. cheers denis co-chair DB-Wg > From: Leo Vegoda <leo(a)vegoda.org> > To: Franziska Lichtblau <rhalina(a)old-forest.org> > Cc: RIPE List <ripe-list(a)ripe.net> > Bcc: > Date: Wed, 10 May 2023 08:01:45 -0700 > Subject: Re: [ripe-list] New Draft Document: RIPE NCC Staff Participation in the RIPE Community (Please review) > Hi, > > On Tue, 9 May 2023 at 02:29, Franziska Lichtblau <rhalina(a)old-forest.org> wrote: > > [...] > > > > One question, as it's not clearly forbidden, is NCC staff allowed to > > > be a WG chair, partake in NomCom, etc? I would say yes. > > [...] > > > Regarding "to avoid giving direction" I am bit torn. I think to put the > > staff into a safe situation they need a little bit of freedom there. > > The line between what could be perceived as "giving direction" vs > > "sharing expertise" is very thin. > > If a RIPE NCC staff member was a WG chair, could they make a decision > on a policy proposal? > > Kind regards, > > Leo >

3 3

New Draft Document: RIPE NCC Staff Participation in the RIPE Community (Please review)
by Mirjam Kuehne 10 May '23

10 May '23

Dear colleagues, In its final report [1], the 2020 RIPE Nominating Committee recommended to document a consensus on the relationship between RIPE and the RIPE NCC and, in particular, how RIPE NCC staff can participate in RIPE. In this new draft document, we focus on the second part of this recommendation: how RIPE NCC staff can and should participate in the RIPE community and how the RIPE community welcomes participation by RIPE NCC staff: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… Please review this document. If you have any comments, questions, suggestions, please send them to this list or to me directly before 31 May 2023. Kind regards, Mirjam Kühne RIPE Chair [1] RIPE Nominating Committee 2020 https://www.ripe.net/publications/docs/ripe-762

10 9

Re: [ripe-list] New Draft Document: RIPE NCC Staff Participation in the RIPE Community (Please review)
by denis walker 10 May '23

10 May '23

Hi Mirjam I also think one of the key points here is "RIPE NCC staff are part of the community and may participate in RIPE activities on the same terms as anyone else." I would specifically like this to cover RIPE NCC staff being full and active members of a Task Force. Recently staff have been left sitting on the sidelines as 'advisors' or doing 'administrative duties'. cheers denis co-chair DB-WG On Fri, 5 May 2023 at 12:00, <ripe-list-request(a)ripe.net> wrote: > From: Mirjam Kuehne <mir(a)zu-hause.nl> > To: RIPE List <ripe-list(a)ripe.net> > Cc: Mirjam Kuehne <chair(a)ripe.net> > Bcc: > Date: Thu, 04 May 2023 12:59:17 +0000 > Subject: [ripe-list] New Draft Document: RIPE NCC Staff Participation in the RIPE Community (Please review) > Dear colleagues, > > In its final report [1], the 2020 RIPE Nominating Committee recommended > to document a consensus on the relationship between RIPE and the RIPE > NCC and, in particular, how RIPE NCC staff can participate in RIPE. > > In this new draft document, we focus on the second part of this > recommendation: how RIPE NCC staff can and should participate in the > RIPE community and how the RIPE community welcomes participation by RIPE > NCC staff: > > https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… > > Please review this document. If you have any comments, questions, > suggestions, please send them to this list or to me directly before 31 > May 2023. > > Kind regards, > Mirjam Kühne > RIPE Chair > > [1] RIPE Nominating Committee 2020 > https://www.ripe.net/publications/docs/ripe-762 > >

2 1

Reminder - RIPE NCC Community Projects Fund - Apply now.
by projectsfund＠ripe.net 09 May '23

09 May '23

Dear colleagues, I hope you are keeping well. For the seventh year in a row, the RIPE NCC is committed to supporting activities and projects for 'the good of the Internet'. We are pleased to invite applications for funding from the RIPE NCC Community Projects Fund. Through this initiative, the RIPE NCC distributes up to EUR 250,000 per year to support projects of value to the operation, resilience and sustainability of the Internet, with a focus on tools and services benefitting the technical community in Europe, the Middle East and Central Asia. Please don’t forget the deadline for this year's call for applications is Wednesday, 31 May 23:59 (UTC) https://www.ripe.net/support/cpf/call-for-applications Kind Regards, Alastair Strachan RIPE NCC

1 0

Principles for Remuneration of the RIPE Chair and Vice-Chair now published as RIPE Document
by Mirjam Kuehne 04 May '23

04 May '23

Dear colleagues, The document "Principles for Remuneration of the RIPE Chair and Vice-Chair" has now been published as ripe-797: https://www.ripe.net/publications/docs/ripe-797/ Kind regards, Mirjam Kühne RIPE Chair

1 0