- ripe-list - mailman.ripe.net

[meetings] RIPE 87 and RIPE 88 Call for Hosts
by RIPE NCC Event Team 20 Sep '22

20 Sep '22

Dear colleagues, Are you interested in hosting RIPE 87 from 27 November – 1 December 2023, or RIPE 88 from 13 – 17 May 2024? We are looking for organisations within the RIPE NCC service region to submit their proposal for host consideration no later than *11 November 2022*. 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 *11 November 2022* to: meeting(a)ripe.net. I look forward to hearing from you. Kind regards, Alexandra Vos Event Organiser

1 0

New on RIPE Labs: Is It Possible for Encryption to Harm Cybersecurity?
by Alun Davies 19 Sep '22

19 Sep '22

Dear colleagues, Andrew Campling gives an update on developments in encrypted DNS and asks whether it’s possible that protocols intended to safeguard privacy might actually have a negative impact on cybersecurity for end users. Read more on RIPE Labs: https://labs.ripe.net/author/andrew_campling/is-it-possible-for-encryption-… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Re: [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
by Cynthia Revström 17 Sep '22

17 Sep '22

Hi, I agree with Keith that it seems appropriate to provide indemnification for the CoC team members (current and past) for their actions on behalf of the CoC team. However I am by no means a lawyer so the NCC Legal team should evaluate if this is feasible and how to implement it. -Cynthia On Fri, Sep 16, 2022 at 6:05 PM Keith Mitchell <keith(a)smoti.org> wrote: > > On 9/16/22 04:00, Kurtis Lindqvist wrote: > > > >> On 14 Sep 2022, at 20:43, Alex de Joode <alex(a)idgara.nl> wrote: > > >> Those depositions could than be used in court for damage claims > >> (loss of employment, libel/defamation). You can sue RIPE, the event > >> or (individual) members of the CoC. > > > What you are describing (I think) is a situation where the RIPE NCC > > is considered the organiser and the legal home of any activity > > covered by the CoC. In this case the officers implementing the CoC > > would have to be appointed by the RIPE NCC and considered legally > > employed (or covered) by the RIPE NCC and therefor their indemnity > > insurance would cover it and it would be dealt with in the NL. > > Under the RIPE NCC Arbitration process, there is a means by which > community volunteers (who are not NCC employees) are formally > indemnified against potential legal blowback of any decisions they make. > > Parties to the arbitration are required to commit to this when entering > into a dispute resolution. It does seem appropriate that a similar such > indemnification measure should be in place for CoC volunteer officers, > it that is not already envisaged. > > Keith > > _______________________________________________ > diversity mailing list > diversity(a)ripe.net > https://lists.ripe.net/mailman/listinfo/diversity

2 1

Communities & Codes of Conduct
by Brian Nisbet 16 Sep '22

16 Sep '22

Good Afternoon, In the last few days there have been a few emails about the draft CoC documents and, without any hat on, I want to address a few things. The RIPE community is special. It's amazing and wonderful and I love it… but also in so many ways, it is not special at all. It is not immune to the issues that have cropped up elsewhere and, importantly, also crop up in RIPE. This may be hard to hear but it's true. There are people who have left our community due to unwelcome attention, incidents of sexual harassment or repeatedly being told - through deeds if not words - that they are not welcome here. Worse are the people who could contribute so much to the operation of the Internet who look at our community, talk with others about it, and simply shake their heads - "That's not a place for me." These are the sad commonalities between communities, these are the ways in which RIPE is decidedly not special. A suitably, carefully, fairly, enforced Code of Conduct is just one of the many ways of making things better. It sets out the norms of behaviour and, importantly, it says "If you come here and people act badly towards you – we want to know about it, we will care, and we will act." If you want, you can think of it like MANRS or similar. It says that as a community, we have thought about things, that we acknowledge the issues we have, and we are working to improve them. This is not a court of law. It is a community driven effort, and so, like every other effort, we put our trust in those who we appoint, while maintaining the ability to course correct, knowing that there are checks and balances. In fact, I'm extremely happy for those that need to make reports that it isn't a court of law, as such courts, in countries around the world, have been seen to be adversarial towards those who seek justice for things like sexual assault. They put great hurt on the victims and have a truly awful record in bringing that justice. But again, this is not a court of law. Nor is it a way to attack the correct (or whatever passes for correct) use of grammar. But it can be a way to improve communications. It can be a way for a community to clearly say "That isn't a good way to interact, especially if we want to be open." There are many, many ways to have robust technical discussion without giving people the impression that their opinions are not wanted, as has happened many times in the past. And we are getting better at this as a community, but a CoC will help us more. As I have said repeatedly over many years, things happen at RIPE Meetings that the community does not, or should not, want to happen. The previous system gave the victims of those things someone to talk to, which is important, but little more than that. A CoC provides a means of recourse, which has been proven to work in communities around the world. There will be a few growing pains, for sure. There will be people who prejudge all of this, who decide that this changes the community too much. It might even cause them to leave. In many cases that will be a great pity and I hope they stick around - but if this prevents others leaving because they feel unsafe, or from being subjected to behaviour that all of us agree is unacceptable, then, well, I know where I'm happier. No process is perfect, we're humans, but this is a really, really good next step (and yes, I would say that, of course). I believe it will make a difference in who joins our community and for how long they stay. I believe it will, in some small way, improve the sector in which we all work. And thankfully my beliefs are backed up by what we've seen in other communities. Importantly, we can do other things at the same time and I look forward to what other new things this community does, and what excellent initiatives it continues, which will make it better for all. I know I will not convince everyone (this is not the first time I've had this discussion in a community, not even in the RIPE community), and I know that a lot of people in the community are convinced (or convinced enough) already, but I didn't want to stay silent on this thread. This is too important for the community right now, and for the future, for those of us here, and those of us we hope will join us. Thanks, Brian Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

4 4

Re: [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
by JORDI PALET MARTINEZ 14 Sep '22

14 Sep '22

Extra points (clicked too fast send) ... very important ones in my opinion, regarding the appointment of CoC Team members. 1) Don't see the need to ask for one person from the community, and it is fair easy to fake (again same point regarding enforcement). 2) I don't agree that the Chair is the one to appoint CoC members. It should be the community (and this will solve 1 above). 3) I even less agree on "own discretion", it is prone o subjectivity, "my friends", etc., we have seen this happening already many times, here and in the IETF. Is not right, and it is discriminatory. Again, 2, solves this. 4) I'm not convinced there is an objective way to judge "emotional intelligence", and even if there is, I feel this is discriminatory, the same as considering age and gender. Again, 2 above, will solve this. Regards, Jordi @jordipalet El 14/9/22, 12:31, "diversity en nombre de JORDI PALET MARTINEZ" <diversity-bounces(a)ripe.net en nombre de jordi.palet(a)consulintel.es> escribió: Hi Leo, all, I've several inputs/questions related to both documents. 1) I understand that if actions on someone are applied, for example, leaving the meeting, and then the appeal is in his/her favor (there was a misunderstanding, false or wrong perception of witness, etc.), there are legal risks if not properly compensated and even publicly recognized the mistake. I think we should have some text on that. 2) I don't agree that the CoC Team, even being different persons, is the right way to take care of possible Appeals. 3) I don't think is right to "permanently" ban anyone. It is like long-term prison, and everyone can make a mistake and correct the situation or his behavior. I understand that this will happen only in expectational circumstances, however, I feel that just having "for a period of time" is a more prudent path. 4) Is not clear to me if someone removed from a f2f event will also be banned from the mailing lists. I understand that not? 5) I don't think it makes any sense to "remove" someone from a virtual event. I will agree in only disallowing him to speak up. 6) Same a 3 above, I don't think anyone can be removed permanently from a mailing list. In fact, if he/she want to keep participating, it is plain easy to create an alternative email and rejoin, even if not posting. Similarly, can happen 5 above. Should we be realistic in what we can enforce? Regards, Jordi @jordipalet El 14/9/22, 8:34, "ripe-list en nombre de Leo Vegoda" <ripe-list-bounces(a)ripe.net en nombre de leo(a)vegoda.org> escribió: Dear RIPE community, Earlier today, the Code of Conduct TF published two documents for the community's review. We updated the document describing the Code of Conduct Team's operational procedures based on community input. We have also published a document describing a selection process for the Code of Conduct Team. You can find a blog post summarising the changes and linking to the drafts here: https://labs.ripe.net/author/leo_vegoda/two-documents-from-the-code-of-cond… Please review the documents and share feedback by the end of September. Comments on any aspects of either document are welcome. We're particularly keen to get feedback on the term length for the Code of Conduct Team. Kind regards, Leo Vegoda for the Code of Conduct TF -- 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 ********************************************** 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. _______________________________________________ diversity mailing list diversity(a)ripe.net https://lists.ripe.net/mailman/listinfo/diversity ********************************************** 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. ********************************************** 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

New on RIPE Labs: Push the Button - SIDN Lab's DDoS Testbed in Action at CONCORDIA Open Door 2022
by Alun Davies 12 Sep '22

12 Sep '22

Dear colleagues, SIDN Labs have been improving the testbed they developed for the DDoS Clearing House. At the CONCORDIA Open Door event (COD2022) this October, they'll demonstrate how the testbed works as part of the CONCORDIA Threat Intelligence Platform. In this new article on RIPE Labs, the team goes over latest changes to the testbed and plans for COD2022: https://labs.ripe.net/author/thijsvandenhout/push-the-button-sidn-labs-ddos… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE Discussion Mailing List Moderation and Archives
by Mirjam Kuehne 09 Sep '22

09 Sep '22

Dear colleagues, In light of recent events on this mailing list, I have put together some thoughts on moderation and a proposed way forward. I will put this topic on the agenda for the RIPE 85 Community Plenary. Context On 22 July, a highly offensive racist email was sent to the RIPE Discussion List. This mail clearly violates the RIPE Code of Conduct. After discussion with the RIPE NCC, we decided to enable moderation on the list. On 23 July, people who had responded to the offender, notably myself, the RIPE NCC’s Chief Community Officer, and another RIPE community member, were sent further offensive mails by this person and were subjected to ‘subscription bombing’ attacks (many thousands of mailing list subscription requests sent to our inboxes). List Moderation All mails sent to <ripe-list(a)ripe.net> have been held for moderation since this incident. They are reviewed by either Niall O’Reilly or myself (as the RIPE Chair Team) before they are allowed through to the list. The RIPE community has always been open to everyone and it has a demonstrated ability to self-govern. We therefore view our decision here as quite a severe one. Nevertheless, we have received a lot of support from community members for these actions. With that support in mind, we propose that we continue with moderation of the list until at least RIPE 85. The moderation queue will be reviewed at least once a day, and together Niall and I will decide how to proceed. If one of us is unavailable, we will coordinate with other community members to ensure that we always have more than one person available to moderate the list. I will also provide a transparency report to keep the community informed of activities and decisions ‘behind the scenes’ (i.e. whether mails have been held/rejected and how many). So far, no mails have been rejected without us first contacting the original sender. This helps to increase understanding of the process. However, it will ultimately be the moderators who decide if a mail is rejected or not. Offensive or Illegal Mails We will remove the mail from 22 July from the RIPE List archives. This message has no content beyond its aim to cause offense. Modifying archives is not something we do lightly. In this case, we believe it is important to avoid the implication that this kind of language is acceptable to us as a community, especially for anyone reading the archives in the future. Rather than simply removing the mail, I asked the RIPE NCC to move the content of the URL in question and replace it with an explanation that makes it clear that a message has been taken out and why. This would also apply to another mail sent in response, as it quoted the offensive mail. We also understand that the offensive email is illegal under Dutch law. Because the RIPE NCC maintains the public archives of our mailing lists, it is regarded as a hosting provider and with this comes an obligation to remove unlawful content from its public infrastructure. Future Archives Some community members have suggested that we set up an ‘unmoderated archive’, which is similar to how the RIPE NCC Member Discussion List is currently set up. I agree that this is a workable solution that supports transparency. It means that the complete archives, including any rejected mails, will be available under a different URL that is separate from the regular RIPE List archives. We propose not indexing these unmoderated archives so they do not appear in search engines. We will also add a warning to this page so that people are informed that they might find rude or offensive content in the unmoderated archives. We believe such an approach is important for transparency, while at the same time avoiding receiving offensive emails that undermine the important work of our community. Kind regards, Mirjam Kühne RIPE Chair

5 5

New on RIPE Labs: RIPE Chair Team Report September 2022
by Mirjam Kuehne 07 Sep '22

07 Sep '22

Dear colleagues, In this edition of the RIPE Chair Team Reports, with summer coming to an end and the community gearing up for a busy autumn period, here's a quick update on what we're focusing on this month and a reminder to send in your content proposals for RIPE 85. https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-septe… Kind regards, Mirjam Kühne RIPE Chair

1 0

RIPE Labs article on sanctions and solutions
by Chris Buckridge 07 Sep '22

07 Sep '22

Dear colleagues, We have just published an article on RIPE Labs regarding economic sanctions and related work that the RIPE NCC is engaged in and funding: https://labs.ripe.net/author/chrisb/towards-a-sanctions-solution-space/ The RIPE NCC’s goal here is to improve our situation with regard to sanctions over the long-term, and we’re looking forward to speaking more with the RIPE community about how we can do that. Best regards, Chris Buckridge RIPE NCC

3 2

Country selection criteria for RIPE meetings
by Vasia Pupkin 05 Sep '22

05 Sep '22

RIPE Chair: Based on what criteria has Serbia - a country that actively supports war in Ukraine - been selected as a host for the upcoming RIPE meeting? Thank you.

4 3