- ripe-list - mailman.ripe.net

Call for Hosts for RIPE 89, 90 and 91 (Deadline 30 June)
by RIPE NCC Event Team 23 Jun '23

23 Jun '23

Dear colleagues, We have extended the deadline for submitting proposals to host RIPE 89 (28 October – 1 November 2024), RIPE 90 (19-23 May 2025) or RIPE 91 (20-24 October 2025). Interested parties should submit their proposals latest by *30 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 Please send in your proposals to meeting(a)ripe.net I look forward to hearing from you. Kind regards, Sandra Gijzen On behalf of the RIPE Meetings Team

1 0

RIPE NCC Internet Country Report: Central Europe
by Suzanne Taylor 20 Jun '23

20 Jun '23

Dear colleagues, How far do traffic paths travel between networks in Poland? How many IPv4 addresses has Czechia exported? Which domestic networks provide international connectivity into and out of Hungary and Slovakia? We delve into all of this and much more in our latest RIPE NCC Internet Country Report, which focuses on four countries in Central Europe: https://labs.ripe.net/author/suzanne_taylor_muzzin/ripe-ncc-internet-countr… The report provides an analysis of the Internet landscape in Czechia, Hungary, Poland and Slovakia, including these countries’ market players, capacity for future growth in the wake of IPv4 run-out, connections between networks, upstream providers, access to K-root, traffic paths, routing security and more. The RIPE NCC Internet Country Reports draw mainly on data collected by the RIPE NCC and serve to provide insight for both technical communities and policymakers across our service region. I hope you’ll find our latest report interesting and will consider sharing it with anyone else who you think may benefit from its findings. Please let me know if you have any questions or feedback to share - we’d love to hear from you. Best regards, Suzanne ______________ Suzanne Taylor Public Policy & Internet Governance RIPE NCC www.ripe.net

1 0

New on the RIPE Labs Podcast: To Serve the Board
by Alun Davies 15 Jun '23

15 Jun '23

Dear colleagues, In this new episode of the RIPE Labs Podcast, my colleague Anastasiya Pak talks to Christian Kaufmann about his 12 years on the RIPE NCC Executive Board and how the demands of the role have changed dramatically in that time: https://labs.ripe.net/author/anastasiya-pak/to-serve-the-board/ Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

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

The Chair Team Reports: Highlights from RIPE 86
by Mirjam Kuehne 01 Jun '23

01 Jun '23

Dear colleagues, Another RIPE Meeting packed full of presentations, conversation, and socials took place last week in Rotterdam. Looking back over the event, we share some highlights, new initiatives and other news from RIPE 86: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-highl… Kind regards, Mirjam Kühne RIPE Chair

1 0

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