- ripe-list - mailman.ripe.net

RIPE84 Call for Presentations is now open!
by Jan Zorz - Go6 28 Feb '22

28 Feb '22

Dear RIPE community, The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE 84 is going to be a hybrid meeting this year so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is Sunday, 20 March 2022. Proposals submitted after this date will only be considered if there are still time slots available. Red more about CfP amd submit your presentation proposal at: https://ripe84.ripe.net/submit-topic/cfp/ More about RIPE84 meeting: https://ripe84.ripe.net/ Cheers, Jan Žorž on behalf of RIPE PC -- Anything that can be configured can be misconfigured. [RFC5505]

1 0

virtualUKNOF Panel on Hybrid Meetings
by Leo Vegoda 23 Feb '22

23 Feb '22

We are pleased to announce an exciting panel about what NOG and other industry events across the world have learned about running hybrid events over the last year. It will look at the technical, social and organisational impacts of making our industry's events successful as speakers and participants increasingly join over the Internet as well as in person. The panel will be chaired by the RIPE Chair, Mirjam Kühne and will include a panel of representatives from UKNOF, NANOG, RIPE, NLNOG, and AV Department. 1 March, 2022 at 15:00 UTC. Free registration is available at https://virtualuknof-march2022.eventbrite.co.uk/ Kind regards, Leo Vegoda for the UKNOF Communications Committee

1 0

SEE10 RIPE regional meeting CfP - second call!
by Jan Zorz - Go6 23 Feb '22

23 Feb '22

Dear RIPE community, The SEE Programme Committee (PC) is still seeking content proposals from the community for the talks at SEE 10 RIPE regional meeting. Proposals for plenary session presentations, panels, lightning talks and workshops in this second call must be submitted for full consideration no later than 11 March 2022 using the meeting submission system: https://meetings.ripe.net/see-pc/submit-topic/submission-form/ Please read more at: https://www.ripe.net/participate/meetings/regional-meetings/see/see-10/call… We already received and accepted some great presentation proposals in first CfP round, but we still hope to get from you all more excellent submissions and finally see again each other at the proper in-person meeting in April in Ljubljana! Cheers, Jan Žorž RIPE SEE PC chairman -- Anything that can be configured can be misconfigured. [RFC5505]

1 0

Re: [ripe-list] LAST CALL EXTENDED to 18 Feb: Draft Document: RIPE Task Forces - Definition and Guidelines
by denis walker 20 Feb '22

20 Feb '22

Colleagues I almost decided not to send these thoughts. But after a couple of other related emails this weekend I decided to go ahead with it. I hope they are received in the same good faith they were written in. This document on Task Forces (TF) is interesting, but one problem is that it assumes that a TF will always achieve it's goals. But what if it doesn't? There are many reasons why it may not do so. The goals may be unrealistic or unachievable. The scope may be too wide. The TF members may not have all the necessary skills. The TF may go off in the wrong direction or produce something that wasn't expected. This document does not include any option for a review or even a reset during the course of a TF's operation. Who would call for such a review and who would do it? It assumes the TF will simply run to it's own conclusion and then whatever it produces will become a RIPE document by default. This document will then be considered as the fulfilment of the TF goals. A TF should not work for long periods of time in a quiet, background mode. Keeping the community well informed of it's work and progress are important elements of a TF. You mention that a TF must have a mailing list for community feedback. I would add that it should be an open list. If the community cannot post to that list it is not a mailing list, it is an announcement board. Criticism is a part of life. Most people in most areas of work have their work periodically reviewed, by a manager or senior. Scientific and engineering papers are often peer reviewed, before or after publishing them. This is what keeps developments moving forward. In this community people who offer an honest, objective, professional critique are themselves sometimes criticised for being critical. To suggest something didn't achieve it's goals (sometimes a polite way of saying it failed) is often considered unacceptable. To criticise a piece of work can be seen as criticising the author, who may then feel offended. Everything that has ever been written has one or more authors, editors, contributors. If we can't criticise a piece of work for fear of offending the author then we can never criticise anything. TFs are no exception to this. Criticising the work of a TF in good faith should not be seen as criticising any member of the TF. The active element of this community is not very large. You may well know all the members of a TF and have a high regard for them as individuals. That does not obligate you to accept every piece of work they ever do. If it is wrong, it is wrong. It should not be wrong to say so. If criticism has a good foundation and strong arguments, then it doesn't matter how extensive the criticism is. It is the piece of work that is being criticised, not the people who produced it. If we can't accept that difference then we are in trouble. A TF is not about being praised for effort. On a personal level that is nice, but if you join a TF it is also expected. A TF is about achieving the stated goals. If they are not achieved it should be OK to say that. To praise a piece of work, that you don't believe is correct, simply because of the effort put into it, does not benefit anyone. This is why it is important for a TF to have regular communication with the community, especially over a long period of operation. When criticisms are made a TF should address those concerns. By saying 'address' it does not mean they must agree with the criticism. But they must acknowledge it and either accept it or provide arguments against or justify dismissing the criticism, just as we would in a policy proposal discussion. For a TF to ignore criticism is not acceptable. Someone needs to oversee this. If a TF does not address criticism, that in itself needs to be addressed. This document covers the issue about not meeting the deadlines for the TF operation. But what about a TF that does not follow it's methodology or charter? Who should monitor this and what actions should be taken? Looking at the various TF web pages they are all different. They have similar sections but with different headings. In some cases it is not easy to determine the goals of the TF. These pages need to be standardised. You refer to RIPE NCC staff members as 'support staff'. Why can they not be full and active members of a TF? For the Data Protection TF, Jochem and I were full members of the TF. At the time we were staff members. Chairs should also be eligible as TF members if they have the appropriate knowledge, experience and/or skills, even if the TF relates to their own working group. TF members should always be listed on the web page. You say TF members should make the RIPE Chair aware of any potential conflicts of interest. These should be published on the TF web page for transparency. You say the TF should give regular updates to the RIPE Chair. They should also regularly update appropriate working group chairs. You only refer to consensus in terms of the final report or a community document. There is no acknowledgement that a TF may need to build a clear community consensus at various stages of it's work. Especially when the absence of such consensus may mean the TF is making fundamental decisions which may affect the validity of the later work. Where consensus is needed on a significant point in the work of a TF, that should probably be discussed in a relevant working group with the chairs determining consensus. I am not trying to put people off being part of a TF, but we do need to define what it means to be a part of one...and accept that a TF may not always be successful, no matter how much effort you put into it. cheers denis co-chair DB-WG > Dear colleagues, > > I believed I had sent this message to you all on 21 January, but > discovered only today > that I had picked the wrong recipient, from the list of those beginning > with “RIPE” > which my mail app presented. > > At that time, Mirjam and I felt that a two-week extension to the last > call would be > appropriate, as the suggestions received in advance of the original > deadline > appeared uncontroversial, but ought of course to be subject to community > review. > > This extension would have expired tomorrow. > This would clearly be unreasonable, so we have set 18 February 2022 as > the new deadline, > > Please accept my apologies for my mistake. > > On 16 Dec 2021, at 15:21, I (Niall O'Reilly) wrote: > > > On 19 Nov 2021, at 8:48, Mirjam Kuehne wrote: > > > > Based on experiences and feedback received from existing Task Forces > > and > > other community members, we put together a document describing what a > > RIPE Task Force is and how it usually operates: > > > > https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… > > > > Please let us know if you have any questions or suggestions. This will > > be published as a RIPE Document. > > > > Mirjam and I have updated our draft in line with the suggestions we > > received. > > The new version has been placed at > > https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-…. > > > > We consider that it is now time to make a LAST CALL for further > > comment, > > with a deadline of 17:00 UTC on Friday, 14 January 2022. > > > > Shortly after this deadline, we plan to declare that this document has > > Community Consensus and to arrange for its publication as a RIPE > > Document. > > We have updated the text to take account of some suggestions received > during the last call period, and are therefore extending the last call > period until 17:00 UTC on Friday, 18 (not 4) February 2022 to allow > comment > on the latest changes only. > > Updated draft: > https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… > Tracked changed (PDF): > https://www.ripe.net/resolveuid/4ce5895954d249f59bbb5aaa9f71a421 > > Thanks to Cynthia Revström and Randy Bush for their helpful > suggestions, > and to Boris Duval of the RIPE NCC for preparing the updated document. > > Best regards, > > Niall O’Reilly > RIPE Vice-Chair >

2 1

The RIPE Code of Conduct
by Mirjam Kuehne 20 Feb '22

20 Feb '22

Dear colleagues, I have been thinking about what was said on this list about people being afraid of the Code of Conduct. I did not hear people were afraid of adopting a RIPE Code of Conduct. Instead I heard broad consensus and I believe we managed to build a Code of Conduct that encourages "good behaviour" and positive and constructive engagement. I think as a community we can be proud of that achievement. I have the impression however, that the pure existence of a Code of Conduct can be interpreted in different ways. Some people might see a Code of Conduct as guidance that is there in the background to remind us all how we want to treat each other. In that scenario it might make sense to refer to it from time to time and to nudge each other in a friendly way. Other people might see a Code of Conduct as a threat and as a last resort in case people misbehave badly. In that scenario the Code of Conduct would be used in very exceptional cases only and would potentially have severe consequences for a community member. I believe that the tone in which the RIPE Code of Conduct is written and the way it was accepted and agreed by the community, should make people feel safe and that it would be interpreted more in the former way. I understand from reactions to the list that this is not necessarily the case. How can we change that? I would like to remind you that the work of the RIPE Code of Conduct Task Force is not finished yet and that they are working on the implementation process. I would very much appreciate any feedback from you to make sure we all feel comfortable and safe and protected by a Code of Conduct. It should not be seen as a threat. Kind Regards, Mirjam RIPE Chair

5 5

Draft Document: RIPE Task Forces - Definition and Guidelines
by Mirjam Kuehne 20 Feb '22

20 Feb '22

Dear colleagues, Based on experiences and feedback received from existing Task Forces and other community members, we put together a document describing what a RIPE Task Force is and how it usually operates: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… Please let us know if you have any questions or suggestions. This will be published as a RIPE Document. Kind regards, Mirjam Kühne RIPE Chair

4 5

SEE10 RIPE regional meeting CfP
by Jan Zorz - Go6 17 Feb '22

17 Feb '22

The SEE 10 Call for Presentations is now open! The SEE Programme Committee (PC) is now seeking content proposals from the community for the talks at SEE 10. Proposals for plenary session presentations, panels, lightning talks and workshops must be submitted for full consideration no later than 20 February 2022 using the meeting submission system: https://meetings.ripe.net/see-pc/submit-topic/submission-form/ Sorry for late CfP announcement here, it is completely my fault. Please read more at: https://www.ripe.net/participate/meetings/regional-meetings/see/see-10/call… We hope to get from you all as many presentations as possible and finally see again each other at the proper in-person meeting in April in Ljubljana! Cheers, Jan Žorž RIPE SEE PC chairman -- Anything that can be configured can be misconfigured. [RFC5505]

1 0

The RIPE Labs Article Competition is Live
by Alun Davies 15 Feb '22

15 Feb '22

Dear colleagues, We're pleased to announce the launch of the first RIPE Labs Article Competition. To encourage people to share their work and insights about the past, present and future state of the Internet on RIPE Labs, we’re offering as first prize a free trip to come join us at RIPE 84 this May in Berlin, Germany. You can find out more about the competition and how to enter here: https://labs.ripe.net/author/alun_davies/the-ripe-labs-article-competition/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Rob Blokzijl Award 2022
by Eileen Gallagher 09 Feb '22

09 Feb '22

Hi all, a reminder that the nominations period for the Rob Blokzijl Award 2022 remains open until 18th March at 23:59 UTC. Please give some consideration to nominating someone in your own community and/or the wider industry in the RIPE region who, in your opinion, deserves to be recognised for their work to make the internet and/or internet community better. The Award Committee <https://rob-blokzijl-foundation.org/2021/11/22/2022-award-committee/> are particularly interested to receive nominations of individuals who, in addition to their own contributions have also supported and enabled others anywhere in the world. That may have been discreetly behind the scenes or as the fundamental part of a larger team effort but deserves recognition in your opinion. While you might think your choice may not be the overall winner, please do take the time to nominate them and share with the Award Committee what good you see they have done and what they have achieved either in their local community, the RIPE community or across the world. For the person nominated, it may be a wonderful boost and after all these months (years) of not seeing people at events, it's a nice gesture to let them know you believe they should be considered for this great award and you never know! We are looking forward to reading their stories. Full details here: https://rob-blokzijl-foundation.org/2021/11/25/call-for-nominations-2022/ Best wishes Eileen (on behalf of the Award Committee) -- Eileen Gallagher CEO INEXwww.inex.ie + 353 87 911 9954 Twitter: @comepeerwithme Internet Neutral Exchange Association Company Limited by Guarantee Registered in Ireland No. 253804. Registered Office: 1-2, Marino Mart, Fairview, Dublin 3.

1 0

Call for Public Comments on the 2021 IANA Performance Matrix Summary Report
by Ulka Athale 07 Feb '22

07 Feb '22

This message is sent on behalf of the Number Resource Organization (NRO) ------------------------------------------ More information can be found on the NRO website: https://www.nro.net/call-for-public-comments-on-the-2021-iana-performance-m… ------------------------------------------ Dear colleagues, As a result of the successful IANA Stewardship transition in 2016, the IANA Numbering Services are currently managed through a Service Level Agreement between ICANN and the five Regional Internet Registries (RIRs). As part of the result of the IANA Stewardship transition, the IANA Numbering Services Review Committee (IANA RC) (https://www.nro.net/iana-rc) was established in 2016. The IANA RC is composed of representatives from each RIR region and advises and assists the RIRs in the review of the IANA Numbering Services. The IANA services are currently provided by Public Technical Identifiers (PTI) (https://pti.icann.org/), which publishes monthly performance reports on the IANA Numbering Services website (https://www.iana.org/performance/numbers). Based on these monthly performance reports, the five RIRs have produced the 2021 IANA Performance Matrix Summary Report, available at: https://www.nro.net/2021-IANA-Performance-Matrix-Summary-Report ------------------------------------------ 30-Day Public Comment Period ------------------------------------------ The IANA RC is now launching a 30-day public comment period to seek comments and input from the community on the IANA numbering services performance and the 2021 IANA Performance Matrix Summary Report, which can be viewed at: https://www.nro.net/2021-IANA-Performance-Matrix-Summary-Report The IANA RC encourages all members of the Internet number community to review the public IANA Performance Matrix Summary Report. Comments on the IANA service performance should be sent to: iana-performance [at] nro [dot] net. The IANA RC will publish an annual report in March 2022 as advice to the NRO EC with its evaluation of the IANA Numbering services. The report will be based on the IANA Performance Matrix Summary Report and on any input gathered from the global number community. The public comment period ends on *Wednesday, 9 March 2022 at 23:59 UTC*. All public comments will be published on the NRO Website in the dedicated IANA RC section (https://www.nro.net/iana-rc-reports) and will be considered as input to the final report by the IANA. At the end of the 30-day public comment period, the IANA RC will meet and evaluate all input to the final report. Kind regards, Martin Hannigan Chair, IANA Numbering Services Review Committee ------------------------------------------ Further Information ------------------------------------------ • IANA Numbering Services Review Committee: https://www.nro.net/iana-rc • Public Technical Identifiers (PTI): https://pti.icann.org/ • IANA Stewardship Transition Archive: https://www.nro.net/internet-governance/iana/iana-stewardship-transition/ • The SLA for the IANA Numbering Services: https://www.nro.net/sla • IANA Stewardship Transition Number Community Proposal: https://www.nro.net/crisp-final-proposal • IANA RC Reports 2017-2020: https://www.nro.net/iana-rc-reports ------------------------------------------ Regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0