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