- ripe-list - mailman.ripe.net

Axel Pawlik Stepping Down as RIPE NCC Managing Director
by Christian Kaufmann 16 Oct '19

16 Oct '19

Dear colleagues, Today, at the RIPE 79 Meeting in Rotterdam, Axel Pawlik announced that he would step down as Managing Director of the RIPE NCC. Axel's announcement comes 20 years to the day since he joined the organisation. The Executive Board would like to extend its sincere gratitude to Axel for his outstanding service to the RIPE NCC membership and the RIPE community over the past two decades. The RIPE NCC had 1,600 members in 1999 when Axel joined, and during his tenure the organisation has grown to well over 20,000 members. This massive increase corresponds with the growth of the Internet into a tool that is essential to billions of people around the world. Axel's assured leadership meant that the RIPE NCC was more than able to meet the challenges involved in that growth. As the Internet grew, new actors became involved in the Internet ecosystem, and Axel embraced the role of representing the technical community to governments and intergovernmental organisations, making the voice of our community heard at the highest levels. He worked closely with RIPE Chairs Rob Blokzijl and Hans Petter Holen to develop the RIPE community as it not only grew but also incorporated new participants, developed new topics for discussion, and dealt with no small amount of contentious issues that needed to be addressed professionally and effectively. Axel was also integral to efforts to grow technical communities throughout our service region, and he was instrumental in the establishment of the ENOG, MENOG and SEE communities. He is personally proud of the RIPE NCC's efforts to accommodate the voices of everyone who is interested in the development of the Internet. Axel's very first Managing Director's Report in 2000 concluded with "... we look forward to continue working on the solid foundation of the RIPE NCC principles of neutrality, impartiality and openness to serve the Internet community and especially the RIPE NCC membership." Axel continued to make this the core sentiment of the RIPE NCC for 20 years. For this, and for so much more, we thank Axel and we look forward to his continued involvement in our community. The Executive Board will quickly start the process of recruiting a new Managing Director. In the meantime, the Board has appointed a new Management Team of Gwen van Berne (CFO), Kaveh Ranjbar (CIO) and Felipe Victolla Silveira (COO), who will lead the RIPE NCC and ensure there is continuity of service and operations during the interim period. Kind regards, Christian Kaufmann RIPE NCC Executive Board Chairman

1 0

Code of Conduct 3.0
by Malcolm Hutty 16 Oct '19

16 Oct '19

Dear all, I understand that on Thursday afternoon the RIPE Plenary will be invited to adopt “Code of Conduct v3.0”. Unfortunately I must leave Rotterdam at lunchtime, so I am writing to share with you my reasons for believing it should not be approved. Code of Conduct v3.0 proposes the creation of a new entity, the “CoC Team” who will be invested with the power to hear allegations of breach of the Code of Conduct and decide what sanctions, if any, to apply to the community member in violation. Planned sanctions include, amongst other things, 1. Not allowing someone to participate further in RIPE Meetings and/or other RIPE community spaces, for a set period or an indefinite period 2. A public reprimand 3. Requiring that a public apology is made Denying someone the opportunity to participate in RIPE is clearly a serious step. Issuing a public reprimand, or requiring a public apology (i.e. admission of guilt) is potentially seriously damaging to a person’s reputation. Since a public reprimand might make reference to the purposes of the Code, including the prevention of sexual harassment and racist abuse, and assert that the person was found to have violated the Code, but not necessarily say what the individual is alleged to have actually done, a public reprimand from the CoC team could have lasting impact on a person’s career prospects. It is therefore a matter of great importance to every member of this community that if such sanctions are ever applied, the most scrupulous process is used. Unfortunately, in my view the process set out in Code of Conduct 3.0 is very far from fit for purpose. For a start, given the gravity of the intended sanctions, I am stunned to see that the Code neither requires nor suggests that the CoC Team should attempt to speak to the accused individual to get their side of the story. Indeed, there is no requirement that the accused person is even informed of the details of the allegation against them. A public reprimand could be the first the subject hears of the matter. The right to be heard before being punished is not an obscure legalistic procedural device. It is fundamental to basic fairness. Granted, a right of appeal has been added to the Code (thank you Daniel Karrenberg for your urgent intervention!), but I do not think appeal after the fact is sufficient correction to a basically abusive process. Although the most egregious, that is far from the only flaw with Code of Conduct 3.0. It positively encourages anonymous complaints. Complaints are also encouraged not only from alleged “victims”, but also from “witnesses” The Code promises that the identity of the complainant will not be disclosed to the subject of the complaint, potentially making it impossible to understand the circumstances or provide an explanation. The person submitting a complaint is not disqualified under the Code from sitting as a member of the CoC Team adjudicating the complaint. Given that the Code also invites witness reports and assures witnesses that their reports will not be viewed less favourably because they have made multiple reports, it would be entirely consistent with the Code for the CoC Team to also act as as a Code of Conduct patrol, making reports of violations and then sitting in judgement on their own allegations. Thanks to anonymity, nobody outside the CoC team would even know if this were occurring. There are other problems, but this message is already too long. Throughout the Code, the emphasis is consistently on the CoC Team’s responsibility to the reporter. There is no such recognition of a responsibility to the person ‘under investigation’ – by which I mean, the person who is the subject of the complaint; there is actually no expectation set in the Code that the CoC Team would actually conduct an investigation, rather than proceeding directly to judgement on the basis solely of the information contained in the allegation. I have described some serious flaws, but in my view, it is not worth trying to rescue this proposal with patches to each of them. The document as a whole is riddled with bias, and should be abandoned. The Diversity Taskforce has demonstrated that it is not an appropriate body to be undertaking this work. Any serious attempt to create a process for enforcement of a Code of Conduct should be predicated on the basis that a grievance and disciplinary process (which is what this is) owes a serious duty of fairness to all parties, not only to one side. Malcolm. -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | web: www.linx.net London Internet Exchange | London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA

3 3

Call for Volunteers to Serve on the 2019-2020 RIPE NomCom
by Daniel Karrenberg 16 Oct '19

16 Oct '19

[Apologies for the repeat. A number of people told me they had missed this message because I sent it from a single purpose address.] Dear RIPE Participant, RIPE will choose its next chair and a vice chair by way of a nominations committee. Ten volunteers, randomly selected from the community, will make that choice with the help of the whole community. These ten people plus a number of non-voting liaisons and advisors will form the NomCom. The NomCom will start to work around January 2020 and make its selection soon after the next RIPE meeting in May of that year. The job of the NomCom is to select people who have what it takes and also have the support of the community. As chair of the 2019-2020 Nomcom, my job is to organise the work and help the volunteers with making their choice. Therefore I call on you to volunteer. Ideally we are looking for about 100 volunteers representing a broad range of RIPE participants. Ten of those people will be randomly selected to serve on the NomCom. To qualify for serving as a voting volunteer you have to have attended three of the five most recent RIPE meetings up to the meeting taking place this week in Rotterdam. For details about the procedures and duties of the NomCom you may refer to documents ripe-727 and ripe-728. The deadline for volunteering is Sunday November 10th 2019. The only way to volunteer is by using the form at https://www.surveymonkey.com/r/ripenomcom Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom

1 0

RIPE 79 Highlights - Day 2
by RIPE NCC Event Team 16 Oct '19

16 Oct '19

Dear colleagues, The second day of RIPE 79 had 662 attendees checking in, 169 of whom joined us for the first time. The plenary presentations included talks on the deployment status of RPKI, the survival of the BGP protocol over 30 years and inter-RIR collaborations to work on better measurements and visualisations. We celebrated 10 years of RIPE Labs and invited everyone to get creative on our RIPE Labs graffiti wall. The wall is also up all day today, so make sure to stop by! The highlights of the day are online: https://ripe79.ripe.net/programme/report/tuesday/ Today’s the first day of the Working Groups, and its a full agenda! The RIPE NCC General Meeting will take place this evening - you do need to register to attend. If you can't attend the WGs here in person, you can participate remotely: https://ripe79.ripe.net/live/main/ And remember to follow @RIPEMeeting on Twitter for the latest updates, and use #ripe79! Kind regards, Martina de Mas Event Organiser RIPE NCC

1 0

RIPE 79 Highlights - Day 1
by RIPE NCC Event Team 15 Oct '19

15 Oct '19

Dear colleagues, RIPE 79 kicked off in Rotterdam yesterday with 563 attendees checked in from 62 countries, 149 of whom are joining us for their first RIPE Meeting. The meeting programme featured two tutorials and the Newcomers' Intro in the morning leading into the Newcomers' Lunch event. A full day of plenary presentations followed. At the end of the day, attendees gathered for a NOG BoF to exchange ideas on whether NOGs should be a regular discussion item at RIPE Meetings. Then everyone gathered in the venue for the first social of the week, the RIPE 79 Welcome Reception. The highlights of the day are online: https://ripe79.ripe.net/programme/report/monday/ Today's sessions have already begun with another full day of plenary presentations, with the Women in Tech Session running from 13:00-14:00. If you can't be here in person, you can participate remotely: https://ripe79.ripe.net/live/main/ And follow #RIPE79 and @RIPEMeeting on Twitter for the latest updates. Kind regards, Martina de Mas Event Organiser RIPE NCC

1 0

NRO NC Election at RIPE 79
by Axel Pawlik 14 Oct '19

14 Oct '19

Dear colleagues, At RIPE 79 this week, there will be an election for a seat on the Number Resource Organization Number Council (NRO NC). The two confirmed candidates are: - Stefan Nikolov - Filiz Yilmaz (standing for re-election) The voting period will open at 19:00 (UTC+2) on Thursday and closes on Friday at 10:30 (UTC+2). All RIPE Meeting attendees can vote in the election. We will send instructions on how to register to vote to everyone who has checked-in at RIPE 79. You can find more information about the candidates and view expressions of support here: www.ripe.net/2019-nro-nc-candidates Kind regards Axel Pawlik Managing Director RIPE NCC

1 0

RIPE 79 Opens Today
by RIPE NCC Event Team 14 Oct '19

14 Oct '19

Dear colleagues, RIPE Chair Hans Petter Holen will open the RIPE 79 Meeting in Rotterdam today at 14:00 local time (UTC +2). If you cannot attend in person, you can follow the meeting and participate remotely by viewing the live webcast and using the chat facilities at: https://ripe79.ripe.net/attend/about-remote-participation To stay up-to-date with all RIPE Meeting updates, follow us on Twitter: @ripemeeting, #ripe79 Kind regards, Martina Event Organiser RIPE NCC

1 0

Re: [ripe-list] Take a RIPE NCC Certified Professionals exam at RIPE 79
by Randy Bush 10 Oct '19

10 Oct '19

[ cc: ripe list ] > For the first time, we will offer you the opportunity to become a RIPE > NCC Certified Professional at a RIPE Meeting. i think this is horribly broken. neither ripe nor the ncc should be certifying anything except recorded ip resources. randy

6 8

Re: [ripe-list] Survey to assist the Diversity Task Force work on Code of Conduct: harassment, intimidation, unwanted behaviour
by Amanda 08 Oct '19

08 Oct '19

Just following from Denesh's email... The introduction text on the survey states: People who experience harassment or intimidation often keep quiet, especially if they come from an underrepresented group (e.g. women, people of colour, LGBTQIA+). This creates a perception that there isn't a need to have things like a Code of Conduct and consequences in place for violations. If you have ever experienced or witnessed harassment or intimidation at a RIPE Meeting, please let us know simply with a Y/N. Our intention is to shine a light on the magnitude of the problem so that we can work together to create a safer RIPE Meeting for all. *This is not a reporting tool* If you would like to share an example of your experience, please submit them separately in the comment boxes below. Please do not include any identifying information (like dates or names). This survey will be open until the end of RIPE 79. The results shared will be: - # of responses received - The results of the Y/N question - # of stories submitted No identifying details in any story will be shared. Please do not include these. The data is visible to one person within the TF. The survey and all related data will be permanently deleted at the end of RIPE 79. Amanda

1 0

Survey to assist the Diversity Task Force work on Code of Conduct: harrassment, intimidation, unwanted behaviour
by Denesh Bhabuta 08 Oct '19

08 Oct '19

Dear colleagues The RIPE Diversity Task Force has been working on a more robust Code of Conduct to ensure a safe meeting space for all. Part of this work is to raise awareness among the community about why this work is necessary. We have created an anonymous survey with just one simple Y/N question: "Have you ever experienced or witnessed harrassment, intimidation or any other unwanted behaviour while at a RIPE Meeting?" ...that question is followed by open text fields where people can share their experiences if they want. This is not a reporting tool. No names, locations, details or any other identifying text should be included here. The results of the Y/N question will be shared with the community by the TF. We will only share stories that are completely stripped of identfying info as a way to lift the veil on why the work we do matters. If you would like to share your stories, the survey is available at: <https://www.surveymonkey.com/r/N6S5SJ3> Regards Denesh

1 0