- ripe-list - mailman.ripe.net

RIPE 83 Community Plenary Minutes
by Mirjam Kuehne 23 Dec '21

23 Dec '21

Dear colleagues, The draft minutes of the RIPE 83 Community Plenary Session are now online: https://www.ripe.net/participate/ripe/ripe-community-plenary/minutes/ripe-83 Please let me know if you have any questions or corrections. Kind regards, Mirjam Kühne RIPE Chair

1 0

RIPE community session on revised PDP - 26 January 2022
by Mirjam Kuehne 21 Dec '21

21 Dec '21

Dear colleagues, Based on input received during RIPE 83, we decided to organise a dedicated session to gather more feedback on the suggested changes to the Policy Development Process as presented to you at the RIPE 83 community plenary and in my mail to this list from 28 October: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-October/002350.html This online session will take place on 26 January 2022 at 15:00 - 16:30 UTC on zoom. Closer to the date, I will send more information and an agenda. Kind regards, Mirjam Kühne =============

1 0

Post-RIPE 83 Working Group Chair Meeting Summary
by Mirjam Kuehne 20 Dec '21

20 Dec '21

Dear colleagues, The RIPE Working Group Chairs met to review the RIPE 83 meeting. You can find a summary of the meeting here: https://www.ripe.net/participate/ripe/wg/wg-chairs/working-group-chair-coll… Kind regards, Mirjam Kühne RIPE Chair

1 0

SBAS Operator Survey
by Adrian Perrig 16 Dec '21

16 Dec '21

Dear RIPE, Knowing how challenging it is to apply new technologies to current networks, in a collaboration between ETH, Princeton University, and University of Virginia, we constructed a system that provides security benefits for current Internet users while requiring minimal changes to networks. Our design can be built on top of the existing Internet to prevent routing attacks that can compromise availability and cause detrimental impacts on critical infrastructure – even given a low adoption rate. This provides benefits over other proposed approaches such as RPKI that only protects a route’s origin first AS, or BGPsec that requires widespread adoption and significant infrastructure upgrades. Our architecture, called Secure Backbone AS (SBAS), allows clients to benefit from emerging secure routing deployments like SCION by tunneling into a secure infrastructure. SBAS provides substantial routing security improvements when retrofitted to the current Internet. It also provides benefits even to non-participating networks and endpoints when communicating with an SBAS-protected entity. Our ultimate aim is to develop and deploy SBAS beyond an experimental scope. We have designed a survey to capture the impressions of the network operator community on the feasibility and viability of our design. The survey is anonymous and takes about 10 minutes to complete, including watching a brief 3-minute introductory video. https://docs.google.com/forms/d/e/1FAIpQLSc4VCkqd7i88y0CbJ31B7tVXyxBlhEy_zs… We thank you for helping inform our further work on this project. We will be happy to share the results with the community. With kind regards Prateek Mittal, Adrian Perrig, Yixin Sun

1 0

Rob Blokzijl inducted in Internet Hall of Fame today
by Mirjam Kuehne 14 Dec '21

14 Dec '21

Dear colleagues, I am very happy to share with you that Rob Blokzijl, one of the founders of the RIPE community and its chair for 25 years, is being inducted posthumously today into the Internet Hall of Fame. The Internet Hall of Fame recognises individuals who have played “an extraordinary role in the conceptualisation, building, and development of the global Internet”. You can see this year's inductees here: https://www.internethalloffame.org/inductees During the ceremony I was able to share some thoughts on Rob's work, his legacy, and the principles he developed with this community that he was so instrumental in creating. You can read more here: https://labs.ripe.net/author/mirjam_kuhne/on-the-legacy-of-rob-blokzijl/ Kind regards, Mirjam Kühne

1 0

New Paper on Deployment and Scalability of SCION
by Thorben Krüger 09 Dec '21

09 Dec '21

Dear colleagues, for those of you who have some interest in the current state of the SCION[1] architecture, we have just published a paper on the "Deployment and Scalability of an Inter-Domain Multi-Path Routing Infrastructure", to be presented tomorrow at CoNEXT 2021[2]: https://netsec.ethz.ch/publications/papers/2021_conext_deployment.pdf Best regards, Thorben Krüger [1]: https://scion-architecture.net/ [2]: https://conferences2.sigcomm.org/co-next/2021/

1 1

New on RIPE Labs: The RIPE Chair Team Reports - Highlights from RIPE 83
by Alun Davies 09 Dec '21

09 Dec '21

Dear colleagues, In their latest report on RIPE Labs, the RIPE Chair Team looks back at important community highlights from RIPE 83: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-highl… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE 83 Highlights Day 5 and Thank You!
by Mirjam Kuehne 29 Nov '21

29 Nov '21

Dear colleagues, RIPE 83 ended with a total of 1,126 registered participants in total, including 240 newcomers with an average of 450 participants per day. This was our fourth virtual RIPE Meeting and we were happy to see a high level of participation and engagement from the community despite the online format. Thank you all for your contributions and all the discussions. And many thanks to the RIPE NCC staff for all the work they've done in the background. On the last day we had the last Plenary session and the Closing Plenary – you can find some highlights from the day in the Daily Meeting Report at: https://ripe83.ripe.net/programme/report/#fri All presentations from the meeting are archived: https://ripe83.ripe.net/archives/ And save the date for RIPE 84: 16-20 May 2021. We hope very much to see you in person for this meeting. You can get updates via the ripe-list, social media and the RIPE 84 website: https://ripe84.ripe.net/ Best regards, Mirjam Kühne, RIPE Chair and Niall O’Reilly, RIPE Vice Chair

1 0

RIPE 83 Highlights - Day 4
by RIPE NCC Event Team 26 Nov '21

26 Nov '21

Dear colleagues, The fourth day of RIPE 83 saw 1124 people registered, with 402 unique participants on Meetecho and more viewers joining in via the livestream on the RIPE 83 website and YouTube. Thursday was the third and last day of the RIPE Working Group sessions – you can find some highlights from the day at: https://ripe83.ripe.net/programme/report/#thu Today we have the last Plenary session followed by the Closing Plenary. The meeting will close at 12:00 (UTC+1). You can find the meeting plan at: https://ripe83.ripe.net/programme/meeting-plan/ Stay tuned for what’s happening at RIPE 83 by following @RIPEMeeting on Twitter and using the #RIPE83 hashtag. Kind regards, RIPE Meeting Team

1 0

New Draft RIPE Policy Development Process (PDP) document - for your review
by Mirjam Kuehne 25 Nov '21

25 Nov '21

Dear colleagues, The RIPE Policy Development Process (PDP) was last updated in 2018. With experience from the first appeal and some other suggested improvements to the process, we felt it was time to work on a new version. The draft version can be found here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… Please send any feedback, questions or suggestions to this list. We will also reserve some time during the RIPE 83 Community Plenary for this topic. We will then issue a last call for consensus after RIPE 83. Here is a list of the most significant changes: - We shortened the introduction to clarify that this document deals with policy only. - We added a section prior to going into details about the formal process: It strongly suggests that an idea for a new policy or a change in policy is first discussed on the relevant mailing list before it enters the formal PDP. This can potentially save the proposer and the community a lot of time and can lead to a better result in the end. - We clarified that the relevant WG chairs need to summarize the state of the discussion after each phase. This will make clear what the state of the discussion is and if community members are required to restate their position. - We clarified the appeals process, especially who should recuse themselves, and we added clear deadlines and responsibilities. - We added a section 5. that describes how the PDP is changed (by community consensus). - In the Policy Proposal Template in Appendix B we added a point 11.a.: Motivation for the proposal. - We made a number of editorial changes in places where it was not clear who is tasked to do what on which list (e.g. the WG chairs or the RIPE NCC Policy Officer). For reference, here is the current version of the PDP: https://www.ripe.net/publications/docs/ripe-710 Kind regards, Mirjam & Niall RIPE Chair Team

8 13