- ripe-list - mailman.ripe.net

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

You are not alone: RIPE Community Resilience in a Pandemic
by Vesna Manojlovic 22 Mar '21

22 Mar '21

Dear colleagues and friends, I’ve been missing you for a whole year; it’s been a demanding and painful period for many of us. In addition to being networkers with an important job of maintaining resiliency of the Internet infrastructure, RIPE Community is a collection of human beings; I was wondering how are we taking care of our own "capacity to recover quickly from difficulties". That's why I wanted to reach out and say: you are not alone! ... but, it turned out that I had so much more to share! While I was struggling to organise the many topics of what pandemic resilience might mean to the RIPE community, it occurred to me to map the classification of universal needs - illustrated by the popular Maslow’s pyramid - to the OSI Layers model, familiar to all networkers: Layer 1: Physical / Physiological needs Layer 2: Data Link / Safety needs Layer 3: Network / Belonging needs Layer 4: Transport / Esteem needs (ACK = acknowledgement) Layer 5: Session / Need for Understanding (cognitive) Layer 6: Presentation / Need for Beauty (aesthetic) Layer 7: Application / Need for (self) actualisation Layer 8: Financial / Need for Contribution (community-actualisation) Layer 9: Political / Need for Justice (cultural perpetuity) Please find the first two articles on RIPE Labs: Article 0 = introduction: https://labs.ripe.net/Members/becha/you-are-not-alone-ripe-community-resili… Layer 1: Physical / Physiological needs: https://labs.ripe.net/Members/becha/ripe-community-resilience-physical-layer Stay tuned for the next layers! And please do share your BCP on how you are coping! Wishing you health and well-being, Vesna Manojlovic -- Community Builder RIPE NCC

2 1

warning - next week will be nice week
by Randy Bush 19 Mar '21

19 Mar '21

ok folk. get the snark and demanding privileged behavior out of your (and my) system now because, in honor of the start of spring (in the northern hemisphere) next week will be nice week. we will remember to say thank you to folk who support us, such as other list members, ncc staff, tool builders, and other infrastructure folk. we will be helpful to others on list; and even show them how to use the wonderful tools provided by the community and the ncc. we will be welcoming to n00bs as they walk into walls as we did when we were n00bs. we will look for opportunities to give credit to others. we will view that new spam as a serendipitous opportunity to better train our bayesian filters. we will encourage and be supportive of ripe/ncc staff if they try to participate as if they were fellow humans who are part of the community; because they actually are. maybe hph will even let them come out and play with us other children. and we will keep our sense of humor at all times. so get that bile out now, because we're gonna be nice next week. randy

8 8

NRO NC Call for Nominations
by Hans Petter Holen 18 Mar '21

18 Mar '21

Dear colleagues, This is a call for nominations from the RIPE NCC service region to fill Filiz Yilmaz’s seat on the Number Resource Organization (NRO) Number Council (NC). Filiz recently stepped down from her position and will end her term on 31 May 2021. On behalf of the RIPE NCC, I would like to express our appreciation for the contribution that Filiz made during her time on the NRO NC. The election for this NRO NC seat will take place during the RIPE 82 meeting that will be held virtually from 17-21 May 2021. All members of the Internet community who are attending the RIPE Meeting may vote in the election. The deadline for nominations is 23 April 2021. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. The nomination process is available at: https://www.ripe.net/nro-nc-nominations-process-may-2021 Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 23 April 2021. All confirmed nominations will be listed on the RIPE NCC website by 26 April 2021. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other people can express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/nro-nc-may-2021 Regards Hans Petter Holen Managing Director RIPE NCC Important dates: 23 April 2021: Deadline for NRO NC nominations 26 April 2021: Deadline for all confirmed nominations to be published on the RIPE NCC website 17-21 May 2021: Election to fill NRO NC seat during RIPE 82 21 May 2021: Announce successful candidate in closing plenary of RIPE 82

1 0