March 2023 - ripe-list - mailman.ripe.net

European Commission: consultation on 'The future of the electronic communications sector and its infrastructure’
by Bastiaan Goslings 28 Apr '23

28 Apr '23

Dear colleagues, Those following the European Union regulatory landscape might already know, as well as subscribers to the RIPE Cooperation WG mailinglist, but we’d like to draw the broader community's attention to a public consultation published by the European Commission on 'The future of the electronic communications sector and its infrastructure’. The deadline of which is the 19th of May. Section 4 of the consultation, 'Fair contribution by all digital players’, states in its introduction: ‘Some electronic communications operators, notably the incumbents, call for the need to establish rules to oblige those content and application providers (“CAPs”) or digital players in general who generate enormous volumes of traffic to contribute to the electronic communications network deployment costs. In their view, such contribution would be “fair” as those CAPs and digital players would take advantage of the high-quality networks but would not bear the cost of their roll-out. Conversely, CAPs and other digital players argue that any payments for accessing networks to deliver content or for the amount of traffic transmitted would not only be unjustified, as the traffic is requested by end-users and costs are not necessarily traffic sensitive (notably in fixed networks), but would also endanger the way the internet works and likely breach net neutrality rules.’ (Et cetera) https://digital-strategy.ec.europa.eu/en/consultations/future-electronic-co… Following the announcement that this consultation was going to be held, the RIPE Cooperation WG chairs called for volunteers to form a small task team and work on a draft submission and position paper on behalf of the community. The list of those who signed up was published on the 25th of February: https://www.ripe.net/ripe/mail/archives/cooperation-wg/2023-February/001648… The small task team members have held weekly calls since and started collating arguments, sources and data to formulate a draft response. As stated in the above mentioned email to the Cooperation WG, the team plans 'to share our draft response prior to its submission and we hope to have time allocated at the RIPE86 meeting Coop WG to discuss it further.’ Details on how to provide input for and feedback on the draft response will be announced later. According to the European Commission the consultation is ‘exploratory’ in nature. However, depending on the outcome, combined with strong lobbying efforts from amongst others the European Telecommunications Network Operators’ Association (ETNO), it could lead to a future EU legislative initiative to intervene because of a perceived imbalance that could negatively impact Europe’s ambitions and the necessary investments in Internet infrastructure to achieve these. As the outcome of this debate is of concern to all operators operating within the European Union, we urge community members to inform themselves about this important topic and engage, if possible, by submitting their own responses to the questionnaire, in particular section 4. Thank you, and with kind regards, -- Bastiaan Goslings Public Policy & Internet Governance RIPE NCC https://www.ripe.net <https://www.ripe.net/>

1 1

LAST CALL: Principles for Remuneration of the RIPE Chairs
by Niall O'Reilly 20 Apr '23

20 Apr '23

Dear friends, On 15 Mar 2023, at 11:47, I wrote: > Please let us know if you think this draft requires material changes. > If not, I expect to declare a last call on this document after taking advice > from the RIPE NCC's Director of HR and Administration. I have received the following comments from Carolien Vos, the RIPE NCC's Director of HR: > I reviewed it and I believe that the described principles are clear and at the same time provide enough flexibility in the implementation of the best suitable approach. I attach the current version of the document. Since the version of 14 March, I have added some extra references to the RIPE-list archive, and made some formatting changes. I believe that the current version is ready for adoption and publication as a RIPE Document. This is therefore a LAST CALL for comment, to expire at 04:00 UTC (06:00 Amsterdam time) on Monday, 17 April. I look forward to declaring consensus and arranging publication shortly after that. Best regards, Niall O'Reilly RIPE Vice-Chair

5 5

Call for Topics for RIPE 85 Community Plenary
by Mirjam Kuehne 19 Apr '23

19 Apr '23

Dear colleagues, The call for proposals for RIPE 85 has been opened. The RIPE community plenary will take place on Thursday, 27 October, in the afternoon. If there are any specific topics you would like to discuss during this session, please let us know before 5 September. Kind regards, Mirjam Kühne RIPE Chair

1 1

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

[meetings] Register now for RIPE 86!
by RIPE NCC Event Team 13 Mar '23

13 Mar '23

Dear colleagues, RIPE 86 takes place at the Rotterdam Ahoy Convention Centre, Rotterdam, the Netherlands from 22 – 26 May 2023. If you haven’t yet registered, follow this link to secure your place: https://ripe86.ripe.net/register/ ------------------ Ticket Options ------------------ Week ticket: EUR 400 Day ticket: EUR 130 Student (week) ticket: EUR 50 Online Attendance: Free! If you register and complete the payment before 23 March, you can make use of the early bird rate! 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 86. Find more information at: https://www.ripe.net/participate/member-support/become-a-member/free-ticket… -------------------- 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 86. Find out how to submit a proposal at: https://ripe86.ripe.net/cfp/ ------------- RIPE Labs Competition -------------- The RIPE Labs Article Competition is back! Once again, we’re offering you a chance to win free tickets, travel, and accommodation to come join us at the next RIPE Meeting.If you have something interesting to say about the past, present or future state of the Internet, submit your article by 31 March for a chance to win free tickets, free travel, and free accommodation for RIPE 86. More information is available at: https://labs.ripe.net/competitions/the-ripe-labs-article-competition-ripe-8… More information on RIPE 86 can be found at: https://ripe86.ripe.net/ Follow us on Twitter: @ripemeeting, #RIPE86 Follow us on Instagram: @ripe_ncc, #RIPE86, #ripemeeting Best regards, Alexandra Vos Event Organiser RIPE NCC

1 0

The RIPE Chair Team Reports - March 2023
by Mirjam Kuehne 02 Mar '23

02 Mar '23

Dear colleagues, February has been an active month for the community with various open policy discussions, active Task Forces and the call for presentations for RIPE 86. Please find some more details on all this and a number of industry events that have been taking place in this new report from the RIPE Chair Team: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-march… Kind regards, Mirjam Kühne RIPE Chair

1 0

[news] Apply now for the RIPE NCC Community Projects Fund
by projectsfund＠ripe.net 01 Mar '23

01 Mar '23

Hello, For more than 25 years, the RIPE NCC has been supporting activities and projects for the “Good of the Internet”. Community-driven, non-commercial work has been fundamental to the success of the Internet from its earliest days, and continues to play an important role in making the Internet resilient, secure and accessible for everyone. Under the RIPE NCC Community Projects Fund, the RIPE NCC will provide up to EUR 250,000 per year to support projects of value to the operation and resilience of the Internet, with a focus on tools and services benefitting the technical community in the Europe, the Middle East and Central Asia. Apply now to get your project funded! The call for applications will close on Wednesday, 31 May 2023 at 23:59 UTC. More details on the application procedure and criteria are available at: https://ripe.net/community-projects-fund If you or your organisation is working on a new or existing project that fits the criteria below, and need some financial support to get it off the ground or keep it going, we want to hear from you! Is your project of benefit to the Internet, particularly the RIPE community? Is your project non-commercial in nature? Do you have a clear project plan and timeline? A couple of things to keep in mind: Funding may be used to purchase equipment, but this cannot be the sole expenditure Funding cannot be used for humanitarian aid, donations, or to encourage political reform Funding cannot be used to provide scholarships or cover tuition fees Funding cannot be used to support any form of commercial activity See the RIPE NCC Community Projects Fund website for more details! If you’re interested in hearing from our previous funding recipients, we are hosting a RIPE NCC Open House session online on Tuesday, 7 March. If you are thinking of applying for the Community Projects Fund, I encourage you to join this session: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-co… Kind Regards Alastair Strachan RIPE NCC Community Projects Fund Coordinator

1 0

ASO Call for Nominations to 2024 ICANN NomCom
by Ulka Athale 01 Mar '23

01 Mar '23

This message is sent on behalf of the Number Resource Organization (NRO) ------------- The full text of the announcement is available at the NRO website: https://www.nro.net/aso-call-for-nominations-to-2024-icann-nomcom/ ------------------------------ ASO Call for Nominations to 2024 ICANN NomCom ------------------------------ The Address Supporting Organization Address Council (ASO AC) is pleased to call for nominations for candidates from the Internet Number Community to run for an open seat on the ICANN NomCom 2024 as delegates of the ASO. The Nominating Committee (NomCom) is responsible for appointing a number of seats to the ICANN Board of Directors, the Public Technical Identifiers (PTI) Board, the At-Large Advisory Committee (ALAC), and the Councils of the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO). The term for the elected delegate will be one year starting in the Annual General Meeting ICANN 78 in October 2023. Specific criteria and requirements regarding the NomCom composition and NomCom delegates are outlined in Article 8, Sections 8.2 and 8.4 of the ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en/#article8 ------------------------------ Important dates ------------------------------ The ASO AC will be responsible for the selection of the delegate based on the following timeline: - Announcement of call for nominations for 2024 ICANN NomCom: Wednesday, 1 March 2023 - Nomination period ends: Tuesday, 25 April 2023 - Evaluation of nominations by the ASO AC: Wednesday, 3 May to Wednesday, 17 May 2023 - Voting period by the ASO AC: Thursday, 18 May to Wednesday, 24 May 2023 - Results reported internally to the ASO AC: Thursday, 25 May 2023 - Announcement of selected delegate: around Friday, 26 May 2023 Nominations should be sent to secretariat [at] aso [dot] icann [dot] org by 25 April 2023 at 23:59 UTC, along with answers to the following questions (all of which are mandatory): 1. Have you read the time commitment for the NomCom and are you willing to commit the time required to fulfil this role? 2. Have you been part of a Nomination Committee in the past with ICANN or with any other organization? 3. Please describe your involvement in your RIR community. 4. Please describe your involvement in the ICANN community. 5. Please briefly share why you would like to join the NomCom as the ASO AC appointee. Additionally, all candidates must provide their background in the Internet industry. A CV is not mandatory but recommended. For more information about the required knowledge, skills, and abilities, eligibility requirements, key responsibilities, and time commitment, please see the following announcement: https://aso.icann.org/aso-call-for-nominations-to-2024-icann-nomcom Sent on behalf of the ASO AC The ASO Secretariat ------------------------------ Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0