- ripe-list - mailman.ripe.net

2019 NRO NC Election Results
by Axel Pawlik 18 Oct '19

18 Oct '19

Dear colleagues, We are pleased to announce that Filiz Yilmaz was re-elected to the Number Resource Organization Number Council (NRO NC) at a plenary session of the RIPE 79 Meeting in Rotterdam on 18 October 2019. After completion of her current term on 31 December 2019, Filiz will begin another three-year term from 1 January 2020 to 31 December 2022. Details on the election process and the NRO NC are available online: https://www.ripe.net/nro/nro-rc/nominations2019 We would like to congratulate Filiz on her appointment. Best regards Axel Pawlik Managing Director RIPE NCC

1 0

RIPE 79 Highlights - Day 4
by RIPE NCC Event Team 18 Oct '19

18 Oct '19

Dear Colleagues, The fourth day of RIPE 79 had 736 attendees checking in, including 188 newcomers. Yesterday was the second day of the Working Groups (WG): Anti-Abuse, IPv6, Routing, IoT, MAT and Database. For the first time, we held the RIPE community plenary - a forum to discuss matters that effect the community. The session was very well attended and can be viewed online. The highlights of Thursday are available at: https://ripe79.ripe.net/programme/report/#thu Today's the last day of the RIPE Meeting. If you can't attend in person, you can participate remotely: https://ripe79.ripe.net/live/main/ Stay tuned to what's happening at RIPE 79 by following @RIPEMeeting on Twitter and using the #ripe79 hashtag. Kind regards, Martina de Mas Event Organiser RIPE NCC

1 0

Re: [ripe-list] [diversity] [comms-circle] Towards a more inclusive community
by Hank Nussbacher 17 Oct '19

17 Oct '19

On 17/10/2019 17:32, Julia Freeman wrote: Julie, at no time did I say it is not happening. I just said that *I *am clueless about it since I didn't see it or hear about it. Now that you have come forward as well as Jordi, hopefully people will be kinder and more importantly, if you see such behavior being imposed on someone else, and you are a bystander, then you should say something - not only the victim. -Hank > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, Oct 17, 2019 at 04:10:47PM +0200, Amanda Gowland wrote: >> On 17/10/2019 16:08, Hank Nussbacher wrote: >>> On 17/10/2019 17:00, Leslie wrote: >>> >>> Indeed. I am clueless since I haven't seen a single incident >>> message among the various mailing lists. I would expect that RIPE >>> should name and shame those harassing people at meetings. I am >>> truly speechless that this goes on in 2019. >> I, too, am speechless. > What always amazes me with these things, whether it's at a ripe level, or > as we've seen wider in society. "But I haven't seen it" > >>>> Perhaps you are not the one being harassed and the folks who are >>>> haven't told you about their experiences. >>>>> I have not been to as many meetings as you but I have never seen any >>>>> incident, even in the slightest, where the people attending were acting >>>>> inappropriately in any sort of way. I consider RIPE meetings >>>>> extremely safe and inclusive, so just paint me clueless as to what the >>>>> issue is. > I've been to exactly 1 ripe meeting. Ripe 77. > > Within 3 minutes of arriving, while in the queue to pick up my badge, the > guy behind me in the queue was hitting on me and making me feel > uncomfortable. > > Three. > > Minutes. > > Part of what we are dealing with here is the "acting inappropriately in > any sort of way". What you consider appropriate behaviour may not be the > same as what I consider appropriate. > > While in the diversity lunch, there was a disagreement between myself and > another attendee. Someone who I've been told is known for being a pain. > That interaction left me stood outside the room in tears being comforted > by one of the approved contact people. I spent the rest of the event > trying to avoid being anywhere near that individual. > > It was suggested by one speaker that people talk to those in minorities > about the harrassment we experience both at RIPE and as members of the > wider tech community. Don't, if we want to volunteer the information we > will. But for most of us, we don't want to. We don't want to have to > relive it to tell it every time. > > I'm sat here at my laptop at home, watching the live stream, writing this, > in tears, as I relive the experiences. > > It hurts even more when people say "I've not seen it, so it can't be > happening". It devalues our experience. It's basically gaslighting. > > I don't want to talk about this shit. I don't want to be the one who has > to go to tech conferences and do presentations on how we can make a nicer > environment for everyone. But I realise that if I don't speak up, then I'm > doing a disservice to those who come after me. > > You may not have experienced it. You may not have seen it. But its there. > > Believe us. > > J > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFdqHth42M0lILkmGIRAlsHAKCO+inrLZqMiuVm+0frOdVZuQO2yQCgrFco > GohEUBgA3N2Uzy7ck9bAo2E= > =JnLM > -----END PGP SIGNATURE----- >

1 0

Who will be the next RIPE Chair .... and Vice Chair ?
by Daniel Karrenberg 17 Oct '19

17 Oct '19

Dear RIPE participants, Next year, a nominations committee (NomCom) will select two people to fill the positions of RIPE Chair and Vice Chair, with help from the wider community. As chair of the 2019-2020 RIPE NomCom, I invite you to nominate candidates for these positions. As members of the RIPE community, you will have some idea of what the RIPE Chair is responsible for and what kind of person you would like to see in this role - and the revived Vice Chair role. Please think about suitable candidates, talk with them, discuss this with your peers, and nominate people who will have the support of the community. You may nominate any member of the RIPE community for either position. Self-nominations are also permitted. NomCom members are not eligible to be considered. You might also consider volunteering for the NomCom. I have made a separate call for this, which you can find on the ripe mailing list. Send your nominations to <nominations(a)ripe-nomcom.org> and include a description of the skills or expertise that make your candidate a desirable choice. Please also include a working email address or telephone number for the nominee and indicate whether they are aware of your nomination. The Nomcom will also be interested in your opinion about the performance of the incumbent, Hans Petter Holen. The deadline for all nominations is Sunday, 15 December 2019. You can find more information in the relevant RIPE Documents: ripe-714: A brief description of the RIPE Chair’s role. ripe-727: Information about the selection process. ripe-728: Detailed information about the NomCom I am happy to answer any further questions you may have. Daniel Karrenberg Chair of the 2019-2020 RIPE NomCom

3 2

RIPE CoC Draft v3.0
by Brian Nisbet 17 Oct '19

17 Oct '19

Colleagues, Contrary to other reports, as clarified by Hans Petter, the Diversity TF will not be seeking consensus on the new RIPE Meeting Code of Conduct during the Community Plenary at 16:00 CEST today, Thursday 17th October. However the TF is still working towards this CoC and we would like to share the most recent draft with you: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… This draft will form the basis of the discussion this afternoon, and into the future, and we have asked the NCC for an Impact Analysis based upon it. As always, if you wish to work on this, and we would encourage people from all parts of the RIPE Community to do so, please join us in the Diversity TF: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force Brian On Behalf of the RIPE Diversity TF Brian Nisbet 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

1 0

RIPE 79 Highlights - Day 3
by RIPE NCC Event Team 17 Oct '19

17 Oct '19

Dear Colleagues, The third day of RIPE 79 had 711 attendees checking in, including 181 newcomers. Wednesday was all about Working Groups (WG): Address Policy, Cooperation, Connect, DNS, Open Source and ended with RIPE NCC Services. This day was also emotional as Axel Pawlik, RIPE NCC Managing Director, announced that he will step aside for a new generation of leaders after 20 years of service. But we also had fun celebrating networks that have signed their Route Origin Authorisations (ROAs) at the Incredible ROAs party. The highlights of yesterday are available at: https://ripe79.ripe.net/programme/report/wednesday Today is again dedicated to WGs (Anti-Abuse, IPv6, Routing, IoT, MAT, Database) and will end with the RIPE Community plenary. If you can't attend the WGs here in person, you can participate remotely: https://ripe79.ripe.net/live/main/ Stay tuned to what's happening at RIPE 79 by following @RIPEMeeting on Twitter and using the #ripe79 hashtag. Kind regards, Martina de Mas Event Organiser RIPE NCC

1 0

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