- ripe-list - mailman.ripe.net

IGF 2023: Call for proposals now open, deadline 19 May
by Chris Buckridge 04 Apr '23

04 Apr '23

Dear colleagues, The Internet Governance Forum (IGF) will be held this year as a hybrid meeting in Kyoto, Japan, from 8-12 October. There is now an open call for session proposals, with the over-arching theme of the event being, "The Internet We Want - Empowering All People”. You can find the proposal forms and further information here: https://www.intgovforum.org/en/content/igf%C2%A02023-call-for-session-propo… The deadline for submissions is 19 May 2023, 23:59 UTC. Please get in touch if you have any questions regarding this process; you can also find further information about the IGF in a recent RIPE Labs article: https://labs.ripe.net/author/chrisb/the-internet-governance-forum-in-2023/ Best regards, Chris Buckridge Advisor to the RIPE NCC Managing Director, Global Strategic Engagement IGF MAG member, 2023

1 0

RIPE NCC's Community Development Plans
by gpetrova 03 Apr '23

03 Apr '23

Dear colleagues, In this RIPE Labs article I've summarised the plans of engagement of the Community Development department at RIPE NCC for 2023. Please have a look and let me know if you have any comments, feedback or suggestions: https://labs.ripe.net/author/gergana_petrova/community-development-plans-fo… Best regards, Gergana Gergana Petrova Community Development Manager RIPE NCC

1 0

Letter to ICANN - Proposal to Re-engage the AFRINIC Community
by Ulka Athale 29 Mar '23

29 Mar '23

This message is sent on behalf of the Number Resource Organization. ------------------------- The original announcement and letter in PDF format are available at: https://www.nro.net/letter-to-icann-proposal-to-re-engage-the-afrinic-commu… ------------------------- Public Letter Sent to ICANN Leadership Regarding Re-engagement with AFRINIC Community ------------------------- AFRINIC is facing governance challenges which need to be addressed with some urgency. Among these is the lack of a functioning board, which requires elections to be held to replace vacant board seats and re-establish quorum. The NRO believes that a free and fair AFRINIC election requires an effective activation of the AFRINIC membership and community towards informed participation. This process is underway, but it requires adequate and urgent resourcing to be as effective as possible in reaching every member of the AFRINIC community. The NRO considers that the best approach would be the launching of a program with the following aims: - Raising awareness and increasing the involvement of AFRINIC’s community in its governance model; - Hosting dedicated events, or collocating with existing community events, aiming to raise awareness of AFRINIC and its governance; - Ensuring high levels of community participation in these events and membership participation in the election; - Identifying capable and experienced candidates to serve on the AFRINIC Board; - Reducing opportunities for capture by any single interest group. To this end, the NRO welcomes the support of ICANN to contribute to the purposes of this program. While the NRO focuses on the above efforts and will contribute resources and leadership as needed, the intention is to collaborate closely with AFRINIC staff under their guidance and leadership to engage AFRINIC members in a fair and neutral manner. The AFRINIC organization and staff need strong support from global and regional institutions to undertake the work on the strengthening of the AFRINIC community and of AFRINIC itself. We thank you in advance for your support for community-based solutions to address the current AFRINIC governance situation. Signed by John Curran 2023 NRO EC Chair ----------------------- Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

2 1

CfP second call for presentation for RIPE86
by Franziska Lichtblau 25 Mar '23

25 Mar '23

Dear colleagues, The RIPE Programme Committee (PC) is now opening the second call for presentations seeking for content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE86 is going to be a hybrid meeting so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is Sunday, 16 April 2023. Proposals submitted after this date will only be considered if there are still time slots available. Already submitted presentations which have not received an acceptance or rejection notification yet are still under consideration. Read more about the CfP and submit your presentation proposal at: https://ripe86.ripe.net/submit-topic/cfp/ More about RIPE86 meeting: https://ripe86.ripe.net/ Regards, Franziska (On Behalf of the RIPE Programme Committee)

1 0

Re: [ripe-list] Request for IPv4 subnet
by Mathias Westerlund 21 Mar '23

21 Mar '23

I second this sentiment, it doesn't make sense that an SP for an government entity cannot make use of government resources... To the point that a message like this smells funny to me. Regards, Mathias W West digital management AB. On 21 Mar 2023 10:59, Gaurav Kansal <gaurav.kansal(a)nic.in> wrote: Can’t you use the IP segments of Ukraine armed forces or of Ukrainian Government ? Just a suggestion. ----- Original Message ----- From: "C. МЕЛЬНИК via ripe-list" <ripe-list(a)ripe.net> To: ripe-list(a)ripe.net Sent: Monday, March 20, 2023 7:13:39 PM Subject: [ripe-list] Request for IPv4 subnet Dear colleagues, Thank you for the opportunity to be part of the global RIPE team. Now we are developing as an Internet provider in the system of the Armed Forces of Ukraine. In 2022, we started building a service-oriented infrastructure for the Armed Forces of Ukraine. Dear RIPE community, we are asking for your kind support to obtain a pool of IPv4 address space to build a geographically dispersed, disaster-resilient infrastructure for the Armed Forces of Ukraine. We applied and are on the waiting list. But considering our state of emergency related to the war in Ukraine, we ask you to support our initiative. It would be great if the anyone in the RIPE community has unused IPv4 subnet with a /23 mask and handed it over to us, to support us in our fight for peace. Kind regards, Serhii Melnyk -- 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 -- 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

1 0

Request for IPv4 subnet
by C. МЕЛЬНИК 21 Mar '23

21 Mar '23

Dear colleagues, Thank you for the opportunity to be part of the global RIPE team. Now we are developing as an Internet provider in the system of the Armed Forces of Ukraine. In 2022, we started building a service-oriented infrastructure for the Armed Forces of Ukraine. Dear RIPE community, we are asking for your kind support to obtain a pool of IPv4 address space to build a geographically dispersed, disaster-resilient infrastructure for the Armed Forces of Ukraine. We applied and are on the waiting list. But considering our state of emergency related to the war in Ukraine, we ask you to support our initiative. It would be great if the anyone in the RIPE community has unused IPv4 subnet with a /23 mask and handed it over to us, to support us in our fight for peace. Kind regards, Serhii Melnyk

2 1

Notice to the ASO Community on Rejection Action to ICANN Board Resolution on IANA FY24 Operating Plan and Budget
by Ulka Athale 20 Mar '23

20 Mar '23

Dear colleagues, The ICANN Board has approved the IANA FY2024 Operating Plan and Budget. Under ICANN's bylaws, it is possible to register an objection to the budget within 21 days of receiving the notice. The text below contains the official notification, including the cutoff date of 30 March 2023 at 06:59 UTC to register an objection. This message is sent on behalf of the Number Resource Organization. ---------------- The full text of the announcement is available at the NRO website: https://www.nro.net/notice-to-the-aso-community-on-rejection-action-to-ican… ---------------- Notice to the ASO Community on Rejection Action to ICANN Board Resolution on IANA FY24 Operating Plan and Budget ---------------- Dear RIR Community, The ICANN Board of Directors approved the IANA FY24 Operating Plan and Budget. The resolution approving the FY24 IANA Operaring Plan and Budget is available at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…. The approved IANA FY24 Operating Plan and Budget is available at: https://www.icann.org/en/system/files/files/iana-fy24-operating-plan-budget…. This resolution (FY24 IANA Operating Plan and Budget) is subject to Rejection Action Petitions from the community. As a Decisional Participant, the Address Supporting Organization received a notice from the ICANN Secretary pursuant to Section 22.4(a)(v) of the ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en/#article22 Reception of this notice triggered a 21-day period during which any member of the ASO community can submit a rejection petition on the matter. If you would like to submit a Rejection Action Petition to the ASO, please consult Section 2 of Annex D of the ICANN Bylaws for the requirements which must be met by a Rejection Action Petition. https://www.icann.org/resources/pages/governance/bylaws-en/#annexD This comment period will end at 23:59 PDT on 29 March 2023, or 06:59 UTC on 30 March 2023. Any Rejection Action Petition should be sent to the ASO Secretariat (secretariat(a)aso.icann.org) before the deadline. Regards, ASO Secretariat ---------------- Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

Last Call for RIPE Code of Conduct Process and RIPE Code of Conduct Team Appointment Documents
by Mirjam Kuehne 20 Mar '23

20 Mar '23

Dear colleagues, This is a Last Call for the following two draft documents with adeadline of 3 April 08:00 UTC: - Draft RIPE Code of Conduct: Process and Consequences [1] - Draft RIPE Code of Conduct Team: Appointment and Responsibilities [2] Since the end of the comments period, the RIPE Code of Conduct Task Force made one change to the first document to address a concern about potential conflicts of interest. In section 2 "Assessment Group is Formed", the document now states that "Both the person who made the report and the person who is the subject of the report should be reasonably convinced that there are no significant conflicts of interest among the assessment group." To address another concern, the Task Force verified that the document states that the Code of Conduct Team MUST exercise discretion when evaluating reports. I would like to thank the Code of Conduct Task Force members for all their work and especially for carefully listening to the community when drafting these documents. Kind regards, Mirjam Kühne RIPE Chair [1] Draft RIPE Code of Conduct: Process and Consequences: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… [2] Draft RIPE Code of Conduct Team: Appointment and Responsibilities: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft…

1 0

Join us for the DNS Hackathon on 20 and 21 May in Rotterdam (weekend before RIPE 86)
by Vesna Manojlovic 16 Mar '23

16 Mar '23

Dear colleagues, I am pleased to invite you to participate in the DNS hackathon that will take place the weekend before RIPE 86 at Ahoy in Rotterdam, on Saturday 20 May and Sunday 21 May 2023. The hackathon is organised by DNS-OARC, Netnod and the RIPE NCC and offers projects based on three challenges: DNS &... Sustainability Security (and privacy) Sovereignty You can also bring your own idea or project. To participate, apply before Thursday, 23 March 2023 at: https://www.ripe.net/participate/forms/apply/dns-hackathon-2023/ Read more at: https://www.netnod.se/join-the-dns-hackathon-2023 Feel free to share this invitation with your communities. Regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 0

DRAFT: Principles for Remuneration of the RIPE Chairs
by Niall O'Reilly 15 Mar '23

15 Mar '23

Dear friends, After much unexpected delay, I am at last ready to ask you to read and comment on this DRAFT statement of principles for remuneration of the RIPE Chairs, which follows from a recommendation of the RIPE 2020 Nominating Committee. As your mail-reading app allows, you may choose to read this message either as plain text or as HTML; I also attach a PDF edition. I look forward to reading your comments. Best regards, Niall O'Reilly, RIPE Vice-Chair --- # Principles for Remuneration of the RIPE Chairs ## Notes for editorial attention This section is to be removed prior to publication. - Assign RIPE document number - Identify authors and acknowledge other contributors after obtaining corresponding consent from each. - Ensure that references are current. ## Introduction The RIPE Chair and Vice-Chair (together, the RIPE Chairs) have roles described in *The RIPE Chair* ([ripe-714][]). They are selected according to the process set out in *The RIPE Chair Selection Process* ([ripe-727][]). Over the years taking on the role of a RIPE Chair has become a significant commitment, as recognized in discussions on the RIPE Discussion List in [2017][initial discussion] and [2018][call for further discussion]. The sensitivity to conflicts of interest has increased too. In 2020 the RIPE Nominating committee selected Mirjam Kühne as RIPE Chair. Mirjam needed to resign from her job with the RIPE NCC before taking on the role. On recommendation by the Nominations Committee the RIPE NCC offered to provide reasonable remuneration while making [arrangements][] so that Mirjam can act without undue influence from the RIPE NCC. During this process questions were raised from the community about providing remuneration for RIPE Chairs and specifically whether it is appropriate that the RIPE NCC provides such funding. The RIPE Nominating committee made this recommendation (among others) in its report ( [ripe-762][]), *“Document community consensus about remuneration of the RIPE Chairs”*. At the time of writing the community has had some experience with the [arrangements][] mentioned above. ## Scope This document describes the principles of the RIPE community for remuneration of the RIPE Chairs including requests to the RIPE NCC in this regard. ## Principles The community wishes to be sure that the RIPE Chairs are able to put in the necessary effort for their roles and to stay clear of the perception of undue influence. RIPE Chairs will disclose to the community all potential conflicts of interest arising from their role as RIPE Chair as they arise including how they address them. In particular they will disclose their significant means of subsistence. RIPE Chair nominees will make this disclosure to the RIPE Nominating Committee. The community requests that the RIPE NCC continue to reimburse the expenses incurred by the RIPE Chairs in their roles. The community requests that, upon request by a RIPE Chair, the RIPE NCC provides appropriate remuneration for the time the RIPE Chair spends fulfilling their role. The community requests that the concrete arrangements for this shall ensure that the RIPE Chairs can perform their duties without undue influence from the RIPE NCC and that the RIPE NCC informs the community how this is arranged. The community requests the RIPE NCC Executive Board take responsibility for implementing these concrete arrangements. The community requests that the RIPE NCC continues to disclose the total cost of RIPE Chair support including expenses and any remuneration. ## Provenance The RIPE Chairs started working on this document in mid-2022, taking advice from the RIPE NCC. Daniel Karrenberg subsequently made a more concise draft on request of the RIPE Chairs. The RIPE NCC has indicated that it will consider the requests made in this document once the community reaches consensus on the final text. ## Historical and prospective timeline - 2017-11-25: [initial discussion][] on RIPE Discussion List started by Erik Bais - 2018-02-19: [call for further discussion][] by Nigel Titley - late 2022: preparation of draft proposal - 2023-03-07: initial draft released for community discussion - 202y-mm-dd: call for consensus issued - 202y-mm-dd: consensus declared - 202y-mm-dd: published as RIPE-nnnn ## Acknowledgements - RIPE 2020 Nominating Committee ## References - *The RIPE Chair* ([ripe-714][]) - *The RIPE Chair Selection Process* ([ripe-727][]) - *2020 RIPE Nominating Committee Report* ([ripe-762][]) --- [ripe-714]: https://www.ripe.net/publications/docs/ripe-714/ [ripe-762]: https://www.ripe.net/publications/docs/ripe-762/ [ripe-727]: https://www.ripe.net/publications/docs/ripe-727/ [initial discussion]: https://www.ripe.net/ripe/mail/archives/ripe-list/2017-November/001268.html [call for further discussion]: https://www.ripe.net/ripe/mail/archives/ripe-list/2018-February/001334.html [arrangements]: https://www.ripe.net/ripe/mail/archives/ripe-list/2020-August/001945.html ---

8 11