- ripe-list - mailman.ripe.net

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