- ripe-list - mailman.ripe.net

New on RIPE Labs: The RIPE Chair Team Reports - February 2022
by Alun Davies 07 Mar '22

07 Mar '22

Dear colleagues, The RIPE Chair Team shares updates on events and developments that have been taking place across the RIPE community this February. Read more on RIPE Labs: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-febru… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE Community session on proposed revised PDP - Minutes and draft version 2
by Mirjam Kuehne 06 Mar '22

06 Mar '22

Dear colleagues, On 26 January we held an online meeting to gather feedback about the revised Policy Development Process (PDP). The recordings, minutes and slides can be found here: https://www.ripe.net/participate/ripe/ripe-community-plenary/minutes/revise… Below you can find a short summary of the main points discussed at the meeting. Based on this feedback we adjusted the draft document and created a new red-lined version: https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… Please review the changes carefully and provide any additional feedback before 16 March 2022. Kind regards, Mirjam Kühne ============ Meeting Summary: The overall sentiment was to rely on community consensus and common sense as much as possible and to keep formalism at a minimum. 1. Author and Ownership of the Document There was general agreement to make a distinction between the author and owner of the PDP: the community should be listed as owner of the PDP and the RIPE Chair as the author of the document. [1] 2. Scope of the Document There was agreement to shorten the introduction of the document to clarify that the PDP only refers to policy. There was also agreement to keep the section about values and principles. 3. Changes to PDP Most people agreed that the scope of the Policy Development Process should be limited to creating policy. It should not be used to change the PDP itself or other RIPE governance documents. It was suggested however to carefully manage the change process including clear deadlines and announcements to ensure proper community consensus building. 4. Re-introducing Informal Discussion Step There was strong agreement to re-introduce this step and that gathering support prior to a formal proposal is crucial. 5. Appeals Procedure – Process, Deadlines, Recusals There was general agreement to have a well defined appeals procedure with clear deadlines and a certain level of formalism. Some people suggested to create a separate appeals body. Others felt that it will be difficult to find people and that the WG chairs tend to have experience with the PDP. 6. Editorial Changes There was no disagreement about the suggested editorial changes. --- [1] There was a question if the RIPE Vice Chair should also be listed. However, ripe-714 provides the option for the RIPE Chair to delegate to others, e.g. a Vice Chair.

2 1

Offer of help for Ukrainian providers. Please help us share this message widely.
by Simon Besteman 03 Mar '22

03 Mar '22

To whom it may concern, please help us share this message widely among the Ukrainian internet community. The Dutch Cloud Community offers technical assistance to the Ukrainian hosting and cloud industry to help them continue their operations during the attack on their nation. The hosters and cloud providers from the Netherlands acknowledge the extreme hardship of our Ukrainian colleagues. As a community, we passionately believe in a free and open internet, and we want to offer our help to keep the Ukrainian internet safely up and running during these dark hours. Effective immediately, Ukrainian hosting and cloud companies, local and national governments and IT companies are invited to submit requests for assistance through the email address: ukraine(a)dutchcloudcommunity.nl Our members collectively are offering a variety of services at no cost for the requester: backups, virtual servers, hosting of websites, mail services, DDOS protection, IPv4 space, Discord services, datacenter services and a range of other services. Just contact us and we’ll coordinate the requests among the Dutch companies that have offered to help. Important to know: we will offer our services to the best of our ability, but we can and will not assist you in setting up offensive activities. For instance, do not ask us to coordinate DDOS attacks or hacking of sites. We will not allow any spam / scanning activities or hosting of malware or other criminal activities and will act upon this if noticed. We want to help you keep your businesses operating, and we want to help information flow freely. Incoming requests will be evaluated on technical and safety requirements, and then spread among the participating companies in our community. We invite you to contact us and submit your requests for assistance, we are ready to start working to help you with your operation. A reminder of the email address we have created: ukraine(a)dutchcloudcommunity.nl. Do not hesitate to submit requests, however large or small. On behalf of the Dutch Cloud and Hosting community, wishing you all the best at this difficult time in your country’s history Simon Besteman Director Dutch Cloud Community

1 0

RIPE NCC Executive Board Resolution on Provision of Critical Services
by Christian Kaufmann 03 Mar '22

03 Mar '22

Dear members, At its meeting yesterday, the RIPE NCC Executive Board approved the following resolution: The RIPE NCC provides critical services to its membership spread across a diverse geographical and political region. The Executive Board of the RIPE NCC believes that the means to communicate should not be affected by domestic political disputes, international conflicts or war. This includes the provision of correctly registered Internet numbering resources. The Executive Board of the RIPE NCC is committed to taking all lawful steps available to ensure that the RIPE NCC can provide undisrupted services to all members across our service region and the global Internet community. The RIPE NCC will publicly document all its efforts to ensure that the registry is not negatively affected by laws, regulations or political developments. —- It is crucial that the RIPE NCC remains neutral and does not take positions with regard to domestic political disputes, international conflicts or war. This guarantees equal treatment for all those responsible for providing Internet services. This is a fundamental reason why the RIPE NCC has been able to maintain its operations in the way it has for the past three decades. It also means that the information and data provided by the RIPE NCC can be trusted as authoritative and free from bias or political influence. Failure to adhere to this approach would jeopardise the very model that has been key to the development of the Internet in our service region. The Executive Board also expresses solidarity with those operators who have the difficult task of maintaining Internet access to assist the people suffering from the terrible effects of armed conflicts and war. Kind regards, Christian Kaufmann Chairman of the RIPE NCC Executive Board

7 6

Register now for RIPE 84!
by RIPE NCC Event Team 02 Mar '22

02 Mar '22

Dear colleagues, We are happy to let you know that registration for RIPE 84 is now open! This RIPE Meeting will take place in a hybrid format in which online and onsite participants can interact with each other using a common platform. Berlin is set to be another exciting host city https://ripe84.ripe.net/register/ RIPE 84 will take place at the InterContinental Berlin from 16 – 20 May 2022: https://ripe84.ripe.net/venue/meeting-venue/ ------------- Ticket Options ------------- Week ticket: EUR 350 Day ticket: EUR 125 Student (week) ticket: EUR 50 Online Attendance: Free! Are you a new LIR? If so, did you know that you have two free tickets to a RIPE Meeting? If you haven’t used them yet, make sure you do for RIPE 84. Find more information at: https://www.ripe.net/participate/member-support/become-a-member/free-ticket… ------------- Accommodation ------------- The InterContinental Berlin is offering RIPE 84 attendees discounted room rates. You can book your accommodation at: https://ripe84.ripe.net/venue/accommodation/ Please note that there are also several other hotels nearby. ------------- Call for Presentations ------------- The RIPE Programme Committee (PC) is seeking presentation proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), workshops, tutorials, and lightning talks at RIPE 84. Find out how to submit a proposal at: https://ripe84.ripe.net/cfp/ Proposals must be submitted using the meeting submission system and no later than 20 March. Proposals submitted after this date will be considered on a space-available basis. ------------- Call for Sponsors ------------- Supporting a RIPE Meeting through sponsorship gives your organisation fantastic exposure in the global Internet community. We offer a range of options aimed to suit organisations of all sizes: https://ripe84.ripe.net/sponsors/become-a-sponsor/ ------------------- RIPE Labs Competition ------------------- RIPE Labs is offering you a free ticket, travel and accommodation to RIPE 84! Submit your article sharing your work and insights about the past, present and future state of the internet for a chance to join us at RIPE 84 in Berlin. 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/ ---- More information on RIPE 84 can be found at: https://ripe84.ripe.net/ We look forward to seeing you in Berlin or online! For updates about the meeting, follow us on Twitter: @ripemeeting, #RIPE84 Kind regards, RIPE Meetings Organisation Team

1 0

New on RIPE Labs: IPv4 Allocations - Is Fairness Still the Goal
by Alun Davies 02 Mar '22

02 Mar '22

Dear colleagues, An interesting discussion took place last December on whether current policies and procedures for the allocation and transfer of IPv4 resources in the RIPE NCC service region are in line with the original policy intent. To help lend clarity on the issue, Angela Dell’Ara (RIPE NCC Policy Officer) gives an overview of the relevant changes that have come into effect since the RIPE NCC started distributing the last /8 we received from IANA: https://labs.ripe.net/author/angela_dallara/ipv4-allocations-is-fairness-st… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

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