- ripe-list - mailman.ripe.net

RIPE Working Group Chairs Collective Meeting Summary (March 2021)
by Mirjam Kuehne 13 Apr '21

13 Apr '21

Dear colleagues, The RIPE Working Group Chairs met in March to discuss recommendations for possible changes to the RIPE Policy Development Process. We also discussed how the proposed new RIPE Code of Conduct would work in practice and what the role of a WG chair would be in the process. You can find a summary from the meeting here: https://www.ripe.net/participate/ripe/wg/wg-chairs/working-group-chair-coll… Kind Regards, Mirjam Kühne RIPE Chair

7 9

New on RIPE Labs: A Brand New Look at the Best of RIPE Labs
by Alun Davies 12 Apr '21

12 Apr '21

Dear colleagues, We're proud to announce the launch of the new RIPE Labs! We're very happy with the redesign and we hope you'll all agree that the new layout is a big improvement on the old. To get a feel for what's changed, our latest article looks back at some of the great contributions authors have made over the past couple of years so you can enjoy their articles all over again in their fresh new setting. We also cover how to contribute to RIPE Labs and invite readers to give us their feedback. Read more now on the new and improved RIPE Labs: https://labs.ripe.net/author/alun_davies/a-brand-new-look-at-the-best-of-ri… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Register Now for RIPE 82
by RIPE NCC Event Team 12 Apr '21

12 Apr '21

Dear colleagues, RIPE 82 will be held as a virtual meeting and will take place from 17-21 May 2021. You can now register for free at: https://ripe82.ripe.net/attend/register/ ------------- RIPE 82 Conference Platforms ------------- We are pleased to inform you that the RIPE 82 Meeting will use Meetecho as its conference platform and SpatialChat as its virtual networking space. In addition to Meetecho, you will be able to watch the presentations live on the RIPE 82 website and on YouTube. Please note that in both cases, there will be no separate IRC channel or chat functionality. If you would like to participate in the discussions and ask questions, you will have to register for the meeting and join Meetecho. More information on how to participate to the meeting is available on the RIPE 82 website: https://ripe82.ripe.net/attend/how-to-participate/ ------------- Programme ------------- The RIPE 82 Meeting plan uses the CEST time zone (UTC+2): https://ripe82.ripe.net/programme/meeting-plan/ -- Pre-meeting events on Friday, 14 May Keep some time free on the Friday before RIPE 82 begins to participate in these pre-meeting events: - Platform-testing for Meetecho and SpatialChat - Newcomers' Introduction - Newcomers' Social and Mentoring Programme Meet up -- Plenary Sessions The draft plenary programme is online: https://ripe82.ripe.net/programme/meeting-plan/plenary/ BoFs and lightning talk proposals can still be submitted at: https://ripe82.ripe.net/submit-topic/cfp/ -- WG Sessions Each working group has a dedicated session in the RIPE Meeting agenda for presentations on topics relevant to the working group’s agenda. If you want to present in one of the WGs, get in touch with the relevant WG chairs via email: https://ripe82.ripe.net/programme/ripe-wg-chairs/ ------------- RIPE Meeting Mentoring ------------- Experienced RIPE Meeting attendees can help newcomers make the most of their meeting by volunteering to be a mentor. We match mentors with mentees based on interests and areas of expertise. You can sign yourself up to be a mentor or mentee when you register for the meeting. The deadline is *3 May*. Learn more at: https://ripe82.ripe.net/attend/mentoring-programme/ ------------- 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 82: https://ripe82.ripe.net/sponsors/become-a-sponsor/ ---- More information on RIPE 82 can be found at: https://ripe82.ripe.net/ For the latest updates, you can follow us on Twitter at @ripemeeting and by using the hashtag #RIPE82. Best regards, RIPE Meetings Team

1 0

Improving Mitigation of Web-based Threats
by Oliver Payne 02 Apr '21

02 Apr '21

Dear colleagues, In order to help mitigate Distributed Denial of Service (DDoS) attacks against our web infrastructure, we have started testing Cloudflare's DDoS protection services in parts of our production environment as of today. We have seen an increase in the amount and severity of attacks in recent weeks, and this measure will give us added protection. Cloudflare will be used on an experimental basis, with our 24x7 engineers on standby to monitor the situation closely. If we encounter any issues in configuring it, we have the capability to roll the entire infrastructure back to its original state within 60 seconds. We are also investigating other options for longer-term improvements to the resilience of our web infrastructure during DDoS attacks in the coming months. If you have any questions or would like to share your feedback, please reach out to me. Kind regards, Oliver Payne Web Services Team Manager RIPE NCC

1 0

New on RIPE Labs: The RIPE Chair Team Reports - March 2021
by Alun Davies 01 Apr '21

01 Apr '21

Dear colleagues, March saw the publication of a draft RIPE Code of Conduct, lots of activity from RIPE Working Groups, and ongoing preparation in the lead up to RIPE 82. The RIPE Chair Team reports on all this and more on RIPE Labs now: https://labs.ripe.net/Members/mirjam_kuhne/the-ripe-chair-team-reports-marc… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Fwd: RouteViews is looking for host at AMS-IX
by Randy Bush 31 Mar '21

31 Mar '21

as this is more euro-related From: David Teach <dteach(a)routeviews.org> Subject: RouteViews is looking for host at AMS-IX To: <nanog(a)nanog.org> Date: Wed, 31 Mar 2021 09:39:53 -0700 Hi, Without going into too much detail, RouteViews is looking for a new host at AMS-IX. Our current host has made a considerable effort to keep our collector connected, but has be unable to find a suitable long term solution with AMS-IX. If you would like to help, and have VM resources capable of hosting a linux VM at AMS-IX, please contact me off list. Thanks, - David

1 0

Re: [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
by Mirjam Kuehne 26 Mar '21

26 Mar '21

Hi Alex, On 26/03/2021 15:55, Alex de Joode wrote: > On Fri, 26-03-2021 13h 38min, Mirjam Kuehne <mir(a)zu-hause.nl> wrote: > > 09 Nov 2020: TF Chair advises latecomer that TF is not empowered to > expand its membership, explains the arrangements to be made for > transparency, and encourages latecomer to contribute to the work > of the > TF by posting to the TF mailing list. > https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html > <https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html> > > Thank Mirjam, > > I > <https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html>'m > a bit curious about the word 'empowered'. > > Does that mean that a TF can only do what is explicitly allowed, and > there is no room for 'common sense'/'filling in the blancs' ? > > There is always room for common sense in RIPE. The request was discussed by the TF and as a result, the TF communicated that the membership of the TF had been decided and that it wouldn't make sense at that point to add more members as the work was well underway. In addition to that the TF took a number of steps to increase transparency and to make it easier to contribute to the work of the TF. Kind regards, Mirjam

4 4

Re: [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
by Alex de Joode 26 Mar '21

26 Mar '21

On Fri, 26-03-2021 15h 55min, Alex de Joode <alex(a)idgara.net> wrote: > On Fri, 26-03-2021 13h 38min, Mirjam Kuehne <mir(a)zu-hause.nl> wrote:> 09 Nov 2020: TF Chair advises latecomer that TF is not empowered to > expand its membership, explains the arrangements to be made for > transparency, and encourages latecomer to contribute to the work of the > TF by posting to the TF mailing list. > https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html > Thank Mirjam, I'm a bit curious about the word 'empowered'. Does that mean that a TF can only do what is explicitly allowed, and there is no room for 'common sense'/'filling in the blancs' ? -- IDGARA | Alex de Joode | alex(a)idgara.nl | +31651108221

1 0

internet futures
by Randy Bush 26 Mar '21

26 Mar '21

in 2010, the internet society made some videos on possible internet futures ten years out, i.e. nowish. nothing spot on, but themes can be seen for sure. https://www.youtube.com/watch?v=PB4zfGwctGc randy

1 0

Re: [ripe-list] [routing-wg] Call for Presentations - RIPE 82
by JORDI PALET MARTINEZ 23 Mar '21

23 Mar '21

I've moved this to the plenary list, because I think it deserves some more ample discussion. I'm with Job here. In my opinion pre-recorded material must be fine if the presenter is also available for Q&A. We need to take advantage of time and available resources in all the meetings. In fact, my question here is why those decisions are taken by the WG chairs? It must be a community decision! Regards, Jordi @jordipalet El 20/3/21 14:17, "routing-wg en nombre de Mirjam Kuehne" <routing-wg-bounces(a)ripe.net en nombre de mir(a)zu-hause.nl> escribió: Hi all, The topic of pre-recorded presentations was discussed at the RIPE WG chairs meeting after RIPE 81. Many people on the call felt that while there might be good reasons, this should be the exception as it doesn’t allow for the interaction we would like to see at RIPE Meetings. Some WG chairs are considering to make some (possibly pre-recorded) presentations available prior to the RIPE meeting to allow for more discussion time at the meeting itself. Watching pre-recorded talks live wasn’t seen as the best use of RIPE meeting time. Kind regards, Mirjam ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0