- members-discuss - mailman.ripe.net

Consultation on RIPE NCC Charging Scheme 2025
by Fergal Cunningham 18 Mar '24

18 Mar '24

Dear RIPE NCC members, I want to remind you that this Wednesday, 20 March, from 10:00-11:30 UTC (11:00-12:30 CET) we will have an Open House where members can give their input on the RIPE NCC Charging Scheme 2025. You can register to attend now at: https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-schem… This open house will kick off discussion on the charging scheme and will give the Executive Board valuable input ahead of its meeting on 25 March, where it will decide on the draft charging proposal it will present to the members. All those who register to attend will receive a Meetecho link to participate in the open house on Wednesday morning. This year, we want to receive input from members before publishing any draft charging scheme. We believe this will help to arrive at a good proposal well in advance of the General Meeting. To help with discussions, we also provide a consultation page where members can see relevant facts and documentation about the charging scheme as well as the financial landscape the RIPE NCC is operating in. We will develop this page with further information as the consultation progresses: https://www.ripe.net/membership/mail/member-and-community-consultations/cha… We look forward to your involvement in this important process for RIPE NCC members. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC Key Dates 20 March - Consultation with members begins at Charging Scheme 2025 Open House 25 March - RIPE NCC Executive Board discusses charging scheme proposal to put forward to members 27 March - Registration for RIPE NCC General Meeting opens 10 April - Draft charging scheme proposal published for members to discuss 24 April - Final charging scheme proposal published for members to vote on 22-24 May - RIPE NCC membership votes on charging scheme options for 2025

1 0

RIPE NCC Charging Scheme 2025: Open House on 20 March 11:00-12:30 UTC+1
by Fergal Cunningham 05 Mar '24

05 Mar '24

Dear members, We invite you to take part in an Open House on 20 March to discuss the RIPE NCC Charging Scheme 2025. This year, we would like to get input from the members before the Executive Board proposes one or more charging schemes to be discussed and voted on by members. You can register to attend now at: https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-schem… The RIPE NCC will give a presentation at the Open House that explains the current outlook and financial considerations, and then take input and guidance from the members on this important topic. The Open House will be recorded for those who can not attend on the day. The following Monday, 25 March, a RIPE NCC Executive Board Meeting will take place where the Board and Management will discuss the input from members and decide on one or more draft charging schemes to propose to the membership to be voted on at the May General Meeting. We will provide background information and data that can help guide discussions ahead of the Open House. And of course we encourage members to continue to discuss the 2025 charging scheme on this list after the Open House takes place. We look forward to your participation. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

[GM] Call for Volunteers for Executive Board Election Code of Conduct Team
by Ondrej Filip 14 Feb '24

14 Feb '24

Dear members, This is a call for volunteers from the membership to join the Executive Board Election Code of Conduct Team for the May 2024 General Meeting elections. The Executive Board election of 2024 will be the fourth to have a Code of Conduct (CoC) for Executive Board Election candidates. I should make it clear that this is a separate Code of Conduct to the RIPE NCC and RIPE community CoCs. This code has been established and is only in effect for confirmed candidates during the election process. An Executive Board Election Code of Conduct Team was also established to evaluate reports of violations of the Code of Conduct. The team for 2023 was made up of six volunteers and the Executive Board would like to express its gratitude to Cynthia Revström, Arnold Nipper, Annie Yanyan Yang, Kris Edgar, Nat Morris and Sebastian Becker who carried out this important work. The Executive Board would now like to ask for volunteers from the membership to be on the Executive Board Election Code of Conduct Team for the May 2024 election. The task of this team will be to evaluate any reports of violations of the election Code of Conduct by candidates. If the team confirms that a violation of the election Code of Conduct has taken place, disqualification of the candidate in question can take place. If you are willing to participate in this role, please send a mail to <agm(a)ripe.net> by *6 March 2024*. The Board will appoint members of the team from the list of those that volunteer. Members should not volunteer if they expect to become candidates in the election. The Executive Board Election Code of Conduct can be found at: https://www.ripe.net/membership/meetings/gm/meetings/may-2024/executive-boa… Kind regards, Ondřej Filip Chair, RIPE NCC Executive Board

1 0

The redesigned www.ripe.net is now live
by Phillip Oldham 26 Jan '24

26 Jan '24

Dear colleagues, If you visit www.ripe.net today, you might notice some changes. For the past few months, we’ve been working on redesigning ripe.net, and we released the new version yesterday at approximately 18:00 UTC+1. Here are some of the major changes: • The design of the website has changed • The content management system has been changed from Plone to Wagtail • We migrated servers to make this switch • The website is now significantly more mobile and tablet friendly • We are using a new search engine on the website, so search results should be more relevant, and we will be investing time to make this experience even better • Accessibility has been improved, and we aim to align with WCAG 2.1 standards as soon as possible • Visitors should see some performance improvements, and we aim to continue adding improvements for usability and energy efficiency • The RIPE community is more prominent and easy to access from the top-level navigation under “community”, and we are applying a new community design to community-related pages: https://www.ripe.net/community/ The overall navigation of the website has not been significantly altered to ensure a smooth transition. We will be making more changes to the navigation to improve readability and discoverability. Many of you shared input in a survey and some of you joined us for user interviews at RIPE 86 and for conversations following my presentation at RIPE 87. Thank you for helping us through this process. While we have launched the newly redesigned website, with over 8,000 web pages migrated to the new platform, we know there will be fixes and tweaks needed in the weeks to come. If you notice any issues or have feedback, please let us know on the forum: https://forum.ripe.net/t/www-ripe-net-redesign-is-live/820 For anything urgent, please email us at webmaster(a)ripe.net Kind regards, Phillip Oldham (he/him) <poldham(a)ripe.net> Manager, Web Services RIPE NCC Stationsplein 11, 1012 AB Amsterdam

5 6

Re: [members-discuss] The redesigned www.ripe.net is now live
by Phillip Oldham 24 Jan '24

24 Jan '24

Hi Luca The LIR Portal is managed by a different team within the RIPE NCC, however I do know that there is an ongoing effort across teams to align the designs of our various applications with the refreshed www.ripe.net <http://www.ripe.net/> website design. Unfortunately I don’t have any further information at this time. I’ll forward your question to that team so they can reach out with further details. Best regards, Phillip Oldham (he/him) <poldham(a)ripe.net> Manager, Web Services RIPE NCC Stationsplein 11, 1012 AB Amsterdam > On 19 Jan 2024, at 14:55, Luca Marini <marini.luca(a)c1vhosting.it> wrote: > > Thanks for the new design, it looks cool! > > Do you plan to update the UI of the LIR portal too? > > > Luca Marini > Chief Commercial Officer > C1V Hosting > Direct: +39 324 6939 048 | Email: marini.luca(a)c1vhosting.it <mailto:marini.luca@c1vhosting.it> > Website: www.c1vhosting.it <http://www.c1vhosting.it/> | Telegram: t.me/c1vhosting <http://t.me/c1vhosting> > Empowering your digital world with sustainability and innovation: > 🌿 Sustainable Solutions: Committed to net zero with renewable energy. > 🌐 Broadband Services: Local and international connectivity. > 🔗 Data Services: WDM paths, Dark Fiber, IP transit. > ☁️ Cloud & Datacenter: Robust, eco-friendly infrastructure. > 🛡️ Cybersecurity: Advanced D/DoS defense and system integration. > > C1V Hosting: Pioneering sustainable digital connectivity. > > Confidentiality Notice: This email may contain confidential information for the sole use of the intended recipient. If you are not the intended recipient, please notify the sender and delete this email. Unauthorized use is prohibited. > > Thank you for choosing C1V Hosting, your partner for sustainable and innovative digital solutions. > > Warm regards, > > Luca Marini > > >> On 19 Jan 2024, at 14:51, Michele Neylon - Blacknight via members-discuss <members-discuss(a)ripe.net> wrote: >> >> >> This is great. Well done to all involved! >> >> >> >> -- >> Mr Michele Neylon >> Blacknight Solutions >> Hosting, Colocation & Domains >> https://www.blacknight.com/ >> https://blacknight.blog/ >> Intl. +353 (0) 59 9183072 >> Direct Dial: +353 (0)59 9183090 >> Personal blog: https://michele.blog/ >> Some thoughts: https://ceo.hosting/ >> ------------------------------- >> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 >> >> I have sent this email at a time that is convenient for me. I do not expect you to respond to it outside of your usual working hours. >> >> >> From: members-discuss <members-discuss-bounces(a)ripe.net> on behalf of Phillip Oldham <poldham(a)ripe.net> >> Date: Friday, 19 January 2024 at 12:18 >> To: members-discuss(a)ripe.net <members-discuss(a)ripe.net> >> Subject: [members-discuss] The redesigned www.ripe.net is now live >> >> [EXTERNAL EMAIL] Please use caution when opening attachments from unrecognised sources. >> >> Dear colleagues, >> >> If you visit www.ripe.net <http://www.ripe.net/> today, you might notice some changes. For the past few months, we’ve been working on redesigning ripe.net, and we released the new version yesterday at approximately 18:00 UTC+1. >> >> Here are some of the major changes: >> • The design of the website has changed >> • The content management system has been changed from Plone to Wagtail >> • We migrated servers to make this switch >> • The website is now significantly more mobile and tablet friendly >> • We are using a new search engine on the website, so search results should be more relevant, and we will be investing time to make this experience even better >> • Accessibility has been improved, and we aim to align with WCAG 2.1 standards as soon as possible >> • Visitors should see some performance improvements, and we aim to continue adding improvements for usability and energy efficiency >> • The RIPE community is more prominent and easy to access from the top-level navigation under “community”, and we are applying a new community design to community-related pages: >> https://www.ripe.net/community/ >> >> The overall navigation of the website has not been significantly altered to ensure a smooth transition. We will be making more changes to the navigation to improve readability and discoverability. >> >> Many of you shared input in a survey and some of you joined us for user interviews at RIPE 86 and for conversations following my presentation at RIPE 87. Thank you for helping us through this process. >> >> While we have launched the newly redesigned website, with over 8,000 web pages migrated to the new platform, we know there will be fixes and tweaks needed in the weeks to come. If you notice any issues or have feedback, please let us know on the forum: >> https://forum.ripe.net/t/www-ripe-net-redesign-is-live/820 >> >> For anything urgent, please email us at webmaster(a)ripe.net >> >> Kind regards, >> >> Phillip Oldham (he/him) <poldham(a)ripe.net> >> Manager, Web Services >> RIPE NCC >> Stationsplein 11, 1012 AB Amsterdam >> >> >> _______________________________________________ >> members-discuss mailing list >> members-discuss(a)ripe.net >> https://lists.ripe.net/mailman/listinfo/members-discuss >> Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/michele%40blacknight… >> _______________________________________________ >> members-discuss mailing list >> members-discuss(a)ripe.net <mailto:members-discuss@ripe.net> >> https://lists.ripe.net/mailman/listinfo/members-discuss >> Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/support%40c1vhosting…

5 4

Re: [members-discuss] [ncc-services-wg] The redesigned www.ripe.net is now live
by Petrit Hasani 22 Jan '24

22 Jan '24

Dear Randy, Thank you for your report. We have investigated the reported issue. The issue is not as a result of the recent work carried out on the new ripe.net <http://ripe.net/> website. Your AS number submission receives an error due to the “AS-“ prefix which is not allowed to be used in an as-name. The “AS-“ prefix is is a reserved prefix for AS SET in accordance with RFC 2622: Routing Policy Specification Language (RPSL): https://datatracker.ietf.org/doc/html/rfc2622#section-2 RFC 2622: Routing Policy Specification Language (RPSL) datatracker.ietf.org The error message received in the request form does not properly clarify it, creating confusion, so we will look to fix it as soon as possible. Please do not hesitate to contact us if you have any questions or concerns. Kind regards, Petrit Hasani RIPE NCC > On 22 Jan 2024, at 16:12, Petrit Hasani <phasani(a)ripe.net> wrote: > > Dear Randy, > > Thank you for reporting the bug. > > We will look into it and hope to resolve it as soon as possible. > > I will contact you once a fix has been deployed. > > Please do not hesitate to contact us if you have any other questions or concerns. > > Kind regards, > > Petrit Hasani > RIPE NCC > >> On 20 Jan 2024, at 21:28, Randy Bush <randy(a)psg.com <mailto:randy@psg.com>> wrote: >> >>> Date: Fri, 19 Jan 2024 13:16:42 +0100 >>> If you visit www.ripe.net today, you might notice some changes. >> >> deploy on friday afternoon and go home for the weekend. i think that is >> covered pretty early in the textbook. >> >> <ripe-asn.jpg> >> which i can fudge past by skipping the hyphens, but then i submit the AS >> allocation form and get >> >> <ripe-ouch.jpg> >> was a show stopper. and it reproduces. with safari and firefox. and >> when i go to re-do, it has not saved the data i entered. >> >> randy-- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ncc-services-wg

2 2

two-factor authentication mandatory
by Mike B 22 Jan '24

22 Jan '24

Hello, I agree completely with the use of 2FA and do agree with the spirit of this being mandatory. However the current state of RIPE NCC MFA is not suitable to be made mandatory. Namely the TOTP requires a phone (sms) or TOTP App. I would like to see support for FIDO2 keys, if this is not possible OTP via email would be a compromise. My rational for this is that some organisations do not allow phones within the office, nor have any Apps available to install on their systems. Perhaps a more generic scenario is if a phone is out of battery. I'm sure you can appreciate while I am in favour of MFA I think this must be in a different format. I'm aware this is a feature many have been keen for for a while. I see two ways forward: 1) RIPE supports another method of MFA (FIDO KEYS or emailed OTP). 2) RIPE makes Mandatory MFA the choice of the LIR admin. I would like to hear other views on this request to the RIPE NCC. I am not looking for suggestions for workarounds such as online TOTP or writing my own code for this. Regards, Michael

13 14

[Ticket #675089] Re: The redesigned www.ripe.net is now live
by FlexiScale Flexiscale Support 21 Jan '24

21 Jan '24

Franziska Kunsmann, Thank you for request. We will be in touch shortly. SUBJECT: Re: [members-discuss] The redesigned www.ripe.net is now live STATUS: Open http://myservices.flexiscale.com/?cmd=tickets&action=view&num=675089&hash=s…

1 0

Re: [members-discuss] [ncc-services-wg] The redesigned www.ripe.net is now live
by Randy Bush 20 Jan '24

20 Jan '24

> Date: Fri, 19 Jan 2024 13:16:42 +0100 > If you visit www.ripe.net today, you might notice some changes. deploy on friday afternoon and go home for the weekend. i think that is covered pretty early in the textbook. which i can fudge past by skipping the hyphens, but then i submit the AS allocation form and get was a show stopper. and it reproduces. with safari and firefox. and when i go to re-do, it has not saved the data i entered. randy

1 1

Re: [members-discuss] two-factor authentication mandatory
by Oleksij Samorukov 11 Jan '24

11 Jan '24

On 2024/01/11 14:48, Mark Janssen via members-discuss wrote: > On Thu, 2024-01-11 at 14:35 +0100, Mike B wrote: >> My rational for this is that some organisations do not allow phones >> within the office, nor have any Apps available to install on their >> systems. Perhaps a more generic scenario is if a phone is out of >> battery. I'm sure you can appreciate while I am in favour of MFA I >> think this must be in a different format. > > TOTP can be done without phones or phone apps... it just needs the > shared secret and a HMAC fucntion, this can be done via various > password-managers, simple python-scripts, your Ti-81 calculator or any > number of other methods. > > I would advise against any form of e-mail 2fa, as this really reduces > it to a single-factor (with password-resets via email). BTW, TOTP is supported by a recent Yubi key, so you can use it as a hardware token as well. But +1 for FIDO2 implementation, is a very popular standard with many implementations on the market. And it should be easy to implement on the backend/frondent side, implementation is very straightforward with many examples all-around. -- Oleksij Samorukov

1 0

RIPE NCC Quarterly Planning Q1 2024
by Fergal Cunningham 20 Dec '23

20 Dec '23

Dear RIPE NCC members, The Q1 2024 quarterly plans for our development teams are now published at: https://www.ripe.net/support/documentation/quarterly-planning Our quarterly planning includes the work we will be carrying out in the next few months in: - RPKI - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications - DNS and K-root - RIPE Atlas - RIPEstat - RIS - Information Technology - Information Security, Risk and Compliance The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and to foster a dialogue with our members and the community about what you would like to see the RIPE NCC work on going forward. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

New on RIPE Labs: Who’s Waiting on the IPv4 Waiting List?
by Antony Gollan 24 Nov '23

24 Nov '23

Dear colleagues, Four years after our IPv4 waiting list became active, and with more than a thousand LIRs in the queue for an allocation, how successful has the list been at providing at least a minimal amount of IPv4 space to newcomers? We take a closer look at some of the numbers in this article on RIPE Labs: https://labs.ripe.net/author/antony_gollan/whos-waiting-on-the-ipv4-waiting… Regards Antony Gollan Communications Team Manager RIPE NCC

1 0

RIPE Labs article on RIPE NCC's External Engagement and Community plans in 2024.
by hmi＠ripe.net 21 Nov '23

21 Nov '23

Dear all, Earlier this week, I published a RIPE Labs article in the series focused on the RIPE NCC’s Draft Activity Plan and Budget 2024: https://www.ripe.net/participate/meetings/gm/meetings/november-2023/documen… In the article I talk about: Sustaining the Commons - RIPE NCC External Engagement and Community in 2024. https://labs.ripe.net/author/hisham_ibrahim/sustaining-the-commons-ripe-ncc… If you have feedback on the draft document or my article, please let me know on the mailing list or in person next week in Rome at RIPE 87. Kind regards, Hisham Ibrahim Chief Community Officer RIPE NCC

1 0

RIPE Labs Article on RIPE NCC Registry
by James Kennedy 08 Nov '23

08 Nov '23

Dear all, Earlier this week, I published an article on RIPE Labs where I look at the core work within the Registry and how I see our plans shaping up for the future, including draft activities and budget for next year: https://labs.ripe.net/author/james-kennedy/safeguarding-our-core-function-i… This is the second article in a series focused on the RIPE NCC’s Draft Activity Plan and Budget 2024 which you can find at: https://www.ripe.net/participate/meetings/gm/meetings/november-2023/documen… If you have feedback on the draft document or my article, please let me know on the mailing list. Kind regards, James Kennedy Chief Registry Officer RIPE NCC

1 0

Open House on Draft Activity Plan and Budget 2024: Recording Available
by Fergal Cunningham 06 Nov '23

06 Nov '23

Dear all, Last week we had an Open House on the Draft RIPE NCC Activity Plan and Budget 2024. The recording is now available at: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-dr… The session saw statements from our Executive Board Chair and Treasurer, and presentations from our Managing Director and Chief Financial Officer. These were followed by a Q&A with members. Please view the recording and if you have comments or opinions you'd like to share, please let us know so we can consider your input when drafting the final version of the plans for next year. And we ask that you register for the General Meeting taking place on 29 November, where there will be further presentations on our plans for next year among other items. The draft agenda and all supporting information is available from our GM pages: https://www.ripe.net/participate/meetings/gm/meetings/november-2023 Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

Reminder: Open House on Draft Activity Plan and Budget 2024 on Wednesday, 1 November
by Fergal Cunningham 27 Oct '23

27 Oct '23

Dear all, I want to remind you that an Open House on the Draft Activity Plan and Budget 2024 will take place online this coming Wednesday, 1 November at 11:00 (UTC+1). You can register at: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-dr… A presentation on our focus areas for next year as well as details on how we are reducing our costs to accommodate a reduced budget for next year will be given by our Executive Board Treasurer, our Managing Director and our Chief Financial Officer. We hope to see you there. This is an important process and document for the RIPE NCC and its members, and we hope you can give your input so our plan for next year is as good as can be. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

Re: [members-discuss] [ncc-announce] [news] 168th RIPE NCC Executive Board Meeting - Summary Notes
by Kaj Niemi 25 Oct '23

25 Oct '23

Hi, Thanks for a comprehensive report as always. They are interesting to read. Do you think it would be useful to share the PESTEL analysis (slides and/or report, I assume) with the membership? At least I am curious about the factors NCC itself thinks affect it. Regarding "bigger investment portfolios yield better returns" - I do not think that is how it works.. perhaps something else was originally intended to be written? In terms of return, higher expected returns should equal willingness to accept higher volatility (risk) in relative terms. The portfolio size itself only amplifies the return, whether positive or negative. Kaj ________________________________ From: ncc-announce <ncc-announce-bounces(a)ripe.net> on behalf of Hans Petter Holen <hph+announce(a)ripe.net> Sent: Monday, October 23, 2023 11:42 To: ncc-announce(a)ripe.net <ncc-announce(a)ripe.net> Subject: [ncc-announce] [news] 168th RIPE NCC Executive Board Meeting - Summary Notes Dear RIPE NCC members, The RIPE NCC Executive Board held its 168th Meeting on 6 October 2023. The minutes are now available. Minutes of the 168th Meeting: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.…<https://www.ripe.net/about-us/executive-board/minutes/2023/minutes-168th-ex…> The Executive Board publishes the minutes of its meetings so that the workings of the Board and the decisions it makes are transparent to the membership it represents. The following is a summary of the main items from the meeting. Further details are available in the minutes. ----------------------- Main Items ----------------------- - I presented on the status of Objectives and Key Results (OKRs) and planned OKRs for 2024. I also provided insights on staff engagement and presented a Risk Update. - I updated the Board on the developments around AFRINIC. The Board were pleased to hear that there has been a ruling to appoint an Official Receiver and welcomed the appointment of John Crain as an expert observer to support the Receiver. - Mirjam Kühne shared her report on developments in the RIPE community. - The Board discussed whether to continue providing funding support on request for Working Group (WG) Chairs. It was agreed that this encourages potential WG Chairs and to continue this funding for another three years. - Fergal Cunningham presented the results of a PESTLE analysis carried out with staff in July 2023. - Fergal presented the findings and key takeaways of the RIPE NCC Survey 2023 and shared the draft report with the Board. - Fergal also presented the Draft Activity Plan and Budget 2024 and asked the Board for comments before the draft was published to members. The Board reviewed the document and shared feedback. - Simon-Jan Haytink presented the financial report for August 2023. He also shared the draft budget for 2024 and the status of the Treasury project. - Athina Fragkouli presented proposed amendments to the Articles of Association on requirements for Executive Board candidates. - The Board reviewed and agreed to proposed amendments to the RIPE Database Terms and Conditions which include the provision of geolocation information as a purpose of the RIPE Database. - James Kennedy presented the outcome of the analysis of Membership Non-Payments. - Fergal shared the draft agenda for the upcoming General Meeting with the regular topics for the Autumn General Meeting. - Felipe Victolla Silveira presented on the usability of the IPv4 Transfer Broker List provided by the RIPE NCC. - Felipe also presented a retention strategy for the data from Routing Information Service (RIS) and RIPE Atlas. ---------------------------- Resolutions Adopted ---------------------------- - The RIPE NCC Executive Board approves the minutes of EB#167. - The RIPE NCC Executive Board resolves that the RIPE NCC will continue to provide funds for the physical participation of working group chairs at RIPE Meetings in accordance with the relevant published procedure until the end of 2026. The RIPE NCC Executive Board will re-evaluate this resolution for the RIPE Meetings after 2026. - The RIPE NCC Executive Board approves an initial investment of 10 M EUR with the investment partner. - The RIPE NCC Executive Board approves the amendments to the “RIPE Database Terms and Conditions”. - The RIPE NCC Executive Board approves the amendments to the “RIPE NCC Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Procedure”. - The RIPE NCC Executive Board approves the amendments to the “RIPE NCC Website and Publicly Available RIPE NCC Services Terms of Service”. - The RIPE NCC Executive Board approves the amendments to the “RIPE NCC Privacy Statement”. - The RIPE NCC Executive Board approves the publication of the draft agenda for the RIPE NCC General Meeting in November 2023. - The RIPE NCC Executive Board resolves to decommission the IPv4 Transfer Broker List and the IPv4 Transfer Listing service. Kind regards, Hans Petter Holen Managing Director and Chief Executive Officer RIPE NCC

6 11

RIPE Labs Article on RIPE NCC Budgeting
by Simon-Jan Haytink 23 Oct '23

23 Oct '23

Dear all, Last week we published the Draft Activity Plan and Budget 2024. You can find that document at: https://www.ripe.net/participate/meetings/gm/meetings/november-2023/documen… Today I published an article on RIPE Labs that explains the budget further and what we are doing to keep costs under control. https://labs.ripe.net/author/Simon-Jan/changing-financial-tides-the-ripe-nc… If you have feedback on the draft document please let us know on the mailing list. And next week, there is an open house where myself, Hans Petter and members of the Board will be available to discuss our plans and budget. https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-dr… I hope to see you there. Kind regards, Simon-Jan Haytink Chief Financial Officer RIPE NCC

1 0

RIPE NCC Quarterly Planning Q4 2023
by Fergal Cunningham 29 Sep '23

29 Sep '23

Dear RIPE NCC members, The Q4 2023 quarterly plans for our development teams are now published at: https://www.ripe.net/support/documentation/quarterly-planning Our quarterly planning includes the work we will be carrying out in the next few months in: - RPKI - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications - DNS and K-root - RIPE Atlas - RIPEstat - RIS - Information Technology - Information Security, Risk, and Compliance The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and to foster a dialogue with our members and the community about what you would like to see the RIPE NCC work on going forward. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

About "route" objects and BGP announce
by ANTONETTI Gilles 04 Sep '23

04 Sep '23

Dear list, We are LIR for an organization (org1) and managing their class B. 3 AS are announcing /24 routes on this class B. We own the /16 route object. "mnt-routes" is set for org2 for a route R "mnt-routes" nothing declared for org3 I declared the ROA for org1, org2, org3. What seems strange to me is that org3 announces route R. And it works fine. Is that normal ? Regards, Gilles

2 1

Re: [members-discuss] [news] 167th RIPE NCC Executive Board Meeting - Summary Notes
by Hans Petter Holen 23 Aug '23

23 Aug '23

Dear Kaj, Thank you for your mail and apologies for the delay in our response due to summer vacation. The main objective of our outsourced portfolio management is to minimise risk by preserving the principal amount at the best possible return. Our return target is the 12-month EURIBOR plus 50 basis points, with limited volatility. The management fee is 0.5% per annum of the managed portfolio, plus any associated transaction fees. The expected result will depend on the 12-month EURIBOR, portfolio size, and number of transactions. This is outlined in our recently-published treasury statute: https://www.ripe.net/about-us/legal/corporate-governance/treasury-statute It is important to be clear that our goal isn’t necessarily to beat inflation. We aim to maximise our return within a conservative risk profile. If this partly offsets or outpaces inflation, then we will have significantly improved our situation compared to the past. Considering that all funds held by the RIPE NCC are membership funds, both we and our board agree that maintaining a conservative approach is the correct strategy. Our approach will be reviewed with the board on a yearly basis and can always be updated if necessary. In terms of our costs and budget, the message from the last GM was received loud and clear. We are currently working to spend less than the approved budget for 2023 and present an Activity Plan and Budget that fits within the boundaries of the 2024 Charging Scheme that the membership has approved. At the same time, we need to make sure we can: - Maintain high service levels (and continue to improve them) - Retain and attract talent - Cope with reduced income from: - The consolidation of LIR accounts - Inability to collect fees from members in ‘Ultra High Risk’ countries that our banks do not want to receive money from - Other revenue at risk due to conflicts in our service region - Absorb the impacts of continued high inflation A budget which reduces year-on-year over multiple years is challenging if we assume that the membership values all of the services we provide. This is something the results from our recent survey appear to support (we will present the results of the survey at RIPE 87). It is therefore not our intent at this stage to reduce or discontinue any activities since, as a membership organisation, we provide services to all members, and each individual member values our different services in their own manner. Even if we were to freeze our operations as they are currently, costs would inevitably increase over time due to inflation. There may also be unexpected events, such as urgent legal, regulatory, or political threats that require us to respond and drive up costs as a result. The sudden influx of potential sanctions cases in 2022 that required investigation by our staff is one recent example of this. Requests also come from the RIPE community that fall within our secretariat role, and these will often have a cost attached. With all of this in mind, we cannot rule out increasing membership fees in the future. As a not-for-profit association funded by membership fees and operating on a cost-recovery basis, there is only an indirect link between services provided and income generated. Higher service levels could potentially attract additional members, but after the IPv4 runout, we see a stable membership with a decline in LIRs. This leaves us to look for efficiency gains in terms of reducing our costs or ending or scaling back some services. Ending services will mean laying off staff and terminating existing contracts which will incur transition costs in the short term. This is not something we are planning at this stage, though we are committed to serving our membership while maintaining the health of the RIPE NCC as an association. We will continue to work closely with the Executive Board regarding our 2024 Activity Plan and Budget and 2025 Charging Scheme. As always, we will ensure that the membership has ample opportunity to provide feedback on our proposed plans before they are approved by the Executive Board in December. Kind Regards, Hans Petter Holen Managing Director and CEO RIPE NCC

4 3

[sell] class /24
by Jakub Osuch 22 Aug '23

22 Aug '23

Dear Members I am looking for class /24 for my company. Please send me offer via email. Jakub Osuch +48501203739 Jakub.osuch(a)techgroup.pl -- Jakub Osuch mobile +48501203739 www.techgroup.pl

3 2

Re: [members-discuss] [sell] class /24
by Jakub Osuch 22 Aug '23

22 Aug '23

I have closed several deals via IPv4 listing service. I wish you all the best in Your business. On Tue, Aug 22, 2023 at 12:53 AM Michał Dąbrowski <michal(a)euro-net.pl> wrote: > On 21.08.2023 22:43, Sergey Myasoedov via members-discuss wrote: > > Dear Jakub, > I consider it selfish to use a mailing list of 20.000+ RIPE NCC members > for your personal/company request of /24. Sending a message to a broad > audience is very typical for spam. > > Why do you think you will succeed in business when using such an > inappropriate method for supplier search? > > Did you hear about IPv4 Listing Service section of LIR portal? > > > > +1 from me, to both parts of the answer. > > > > > -- > Kind regards, > Sergey Myasoedov > > On 21. 8. 2023, at 22:13, Jakub Osuch <jakub.osuch(a)techgroup.pl> wrote: > > Dear Members > I am looking for class /24 for my company. > Please send me offer via email. > Jakub Osuch > +48501203739 > Jakub.osuch(a)techgroup.pl > -- > Jakub Osuch > mobile +48501203739 > www.techgroup.pl > > > -- Jakub Osuch mobile +48501203739 www.techgroup.pl

1 0

New Comment - [Ticket # 663] Re: [ncc-announce] [news] 167th RIPE NCC Executive Board Meeting - Summary Notes
by Tassero Support 24 Jul '23

24 Jul '23

There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk Comment added by: Oliver Roth Comment Content: <div>Guten Tag Ich bin vom 17.7.23. bis am 3.8.23 abwesend. Die Nachrichten werden in diese Zeit nur sporadisch gelesen. Für dringende Angelegenheiten wenden Sie sich bitte an: support(a)nexphone.ch Freundliche Grüsse Oli Roth Am 24.07.2023 um 13:19 schrieb Tassero Support <office(a)tassero.de>: > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > >  > Comment added by: > Oliver Roth >  > Comment Content:  > > Guten Tag > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > Für dringende Angelegenheiten wenden Sie sich bitte an: > support(a)nexphone.ch > > Freundliche Grüsse > Oli Roth > > Am 24.07.2023 um 12:53 schrieb Tassero Support <office(a)tassero.de>: > > > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > > > >  > > Comment added by: > > Oliver Roth > >  > > Comment Content:  > > > > Guten Tag > > > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > > > Für dringende Angelegenheiten wenden Sie sich bitte an: > > support(a)nexphone.ch > > > > Freundliche Grüsse > > Oli Roth > > > > Am 24.07.2023 um 12:49 schrieb Tassero Support <office(a)tassero.de>: > > > > > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > > > > > >  > > > Comment added by: > > > Oliver Roth > > >  > > > Comment Content:  > > > > > > Guten Tag > > > > > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > > > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > > > > > Für dringende Angelegenheiten wenden Sie sich bitte an: > > > support(a)nexphone.ch > > > > > > Freundliche Grüsse > > > Oli Roth > > > > > > Am 24.07.2023 um 12:40 schrieb Tassero Support <office(a)tassero.de>: > > > > > > > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > > > > > > > >  > > > > Comment added by: > > > > Oliver Roth > > > >  > > > > Comment Content:  > > > > > > > > Guten Tag > > > > > > > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > > > > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > > > > > > > Für dringende Angelegenheiten wenden Sie sich bitte an: > > > > support(a)nexphone.ch > > > > > > > > Freundliche Grüsse > > > > Oli Roth > > > > > > > > Am 24.07.2023 um 12:34 schrieb Tassero Support <office(a)tassero.de>: > > > > > > > > > Dear Oliver Roth, > > > > >  > > > > > We would like to acknowledge that we have received your request and a ticket has been created. > > > > > A support representative will be reviewing your request and will send you a personal response.(usually within 24 hours). > > > > >  > > > > > To view the status of the ticket or add comments, please visit  > > > > > <a href="https://help.tassero.de/support/tickets/663 " rel="noreferrer">https://help.tassero.de/support/tickets/663 </a>> > > > > > > > > >  > > > > > > > > > >  > > > > > > > > > >  > > > > > > > > > > Sincerely, > > > > > > > > > > Tassero GmbH Team > > > > >  > > > > > > > > > > --------------------------------------- > > > > > > > > > >  > > > > > > > > > > Tassero GmbH > > > > > Mies-van-der-Rohe Straße 8 > > > > > 80807 München > > > > > > > > > > Tel. : +49 (0) 89 – 545 583 26 > > > > > E-Mail: office(a)tassero.com > > > > > > > > > > Registergericht: Amtsgericht München HRB 230669 > > > > > UstId.: DE 310 271 391 > > > > > > > > > > Geschäftsführer: Heinrich Nako > > > > > > > > > > 663:1788124 > > > > > > > > Attachments : 1. attachment > > > > > > > > > > > >  > > > > > > > > Regards, > > > > Tassero GmbH Team > > > > --------------------------------------- > > > > > > > >  > > > > > > > > Tassero GmbH > > > > Mies-van-der-Rohe Straße 8 > > > > 80807 München > > > > > > > > Tel. : +49 (0) 89 – 545 583 26 > > > > E-Mail: office(a)tassero.com > > > > > > > > Registergericht: Amtsgericht München HRB 230669 > > > > UstId.: DE 310 271 391 > > > > > > > > Geschäftsführer: Heinrich Nako > > > > > > > > 663:1788124 > > > > _______________________________________________ > > > > members-discuss mailing list > > > > members-discuss(a)ripe.net > > > > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > > > > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> > > > > > > Attachments : 1. attachment > > > > > > > > >  > > > > > > Regards, > > > Tassero GmbH Team > > > --------------------------------------- > > > > > >  > > > > > > Tassero GmbH > > > Mies-van-der-Rohe Straße 8 > > > 80807 München > > > > > > Tel. : +49 (0) 89 – 545 583 26 > > > E-Mail: office(a)tassero.com > > > > > > Registergericht: Amtsgericht München HRB 230669 > > > UstId.: DE 310 271 391 > > > > > > Geschäftsführer: Heinrich Nako > > > > > > 663:1788124 > > > _______________________________________________ > > > members-discuss mailing list > > > members-discuss(a)ripe.net > > > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > > > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> > > > > Attachments : 1. attachment > > > > > >  > > > > Regards, > > Tassero GmbH Team > > --------------------------------------- > > > >  > > > > Tassero GmbH > > Mies-van-der-Rohe Straße 8 > > 80807 München > > > > Tel. : +49 (0) 89 – 545 583 26 > > E-Mail: office(a)tassero.com > > > > Registergericht: Amtsgericht München HRB 230669 > > UstId.: DE 310 271 391 > > > > Geschäftsführer: Heinrich Nako > > > > 663:1788124 > > _______________________________________________ > > members-discuss mailing list > > members-discuss(a)ripe.net > > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> > > Attachments : 1. attachment > > >  > > Regards, > Tassero GmbH Team > --------------------------------------- > >  > > Tassero GmbH > Mies-van-der-Rohe Straße 8 > 80807 München > > Tel. : +49 (0) 89 – 545 583 26 > E-Mail: office(a)tassero.com > > Registergericht: Amtsgericht München HRB 230669 > UstId.: DE 310 271 391 > > Geschäftsführer: Heinrich Nako > > 663:1788124 > _______________________________________________ > members-discuss mailing list > members-discuss(a)ripe.net > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> </div> Attachments : 1. <a href='https://help.tassero.de/helpdesk/attachments/80236503695'>attachment</a> Regards, Tassero GmbH Team --------------------------------------- Tassero GmbH Mies-van-der-Rohe Straße 8 80807 München Tel. : +49 (0) 89 – 545 583 26 E-Mail: office(a)tassero.com Registergericht: Amtsgericht München HRB 230669 UstId.: DE 310 271 391 Geschäftsführer: Heinrich Nako

1 0

New Comment - [Ticket # 663] Re: [ncc-announce] [news] 167th RIPE NCC Executive Board Meeting - Summary Notes
by Tassero Support 24 Jul '23

24 Jul '23

There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk Comment added by: Oliver Roth Comment Content: <div>Guten Tag Ich bin vom 17.7.23. bis am 3.8.23 abwesend. Die Nachrichten werden in diese Zeit nur sporadisch gelesen. Für dringende Angelegenheiten wenden Sie sich bitte an: support(a)nexphone.ch Freundliche Grüsse Oli Roth Am 24.07.2023 um 12:53 schrieb Tassero Support <office(a)tassero.de>: > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > >  > Comment added by: > Oliver Roth >  > Comment Content:  > > Guten Tag > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > Für dringende Angelegenheiten wenden Sie sich bitte an: > support(a)nexphone.ch > > Freundliche Grüsse > Oli Roth > > Am 24.07.2023 um 12:49 schrieb Tassero Support <office(a)tassero.de>: > > > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > > > >  > > Comment added by: > > Oliver Roth > >  > > Comment Content:  > > > > Guten Tag > > > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > > > Für dringende Angelegenheiten wenden Sie sich bitte an: > > support(a)nexphone.ch > > > > Freundliche Grüsse > > Oli Roth > > > > Am 24.07.2023 um 12:40 schrieb Tassero Support <office(a)tassero.de>: > > > > > There is a new comment in the ticket submitted by Oliver Roth to Tassero GmbH Helpdesk > > > > > >  > > > Comment added by: > > > Oliver Roth > > >  > > > Comment Content:  > > > > > > Guten Tag > > > > > > Ich bin vom 17.7.23. bis am 3.8.23 abwesend. > > > Die Nachrichten werden in diese Zeit nur sporadisch gelesen. > > > > > > Für dringende Angelegenheiten wenden Sie sich bitte an: > > > support(a)nexphone.ch > > > > > > Freundliche Grüsse > > > Oli Roth > > > > > > Am 24.07.2023 um 12:34 schrieb Tassero Support <office(a)tassero.de>: > > > > > > > Dear Oliver Roth, > > > >  > > > > We would like to acknowledge that we have received your request and a ticket has been created. > > > > A support representative will be reviewing your request and will send you a personal response.(usually within 24 hours). > > > >  > > > > To view the status of the ticket or add comments, please visit  > > > > <a href="https://help.tassero.de/support/tickets/663 " rel="noreferrer">https://help.tassero.de/support/tickets/663 </a>> > > > > > > >  > > > > > > > >  > > > > > > > >  > > > > > > > > Sincerely, > > > > > > > > Tassero GmbH Team > > > >  > > > > > > > > --------------------------------------- > > > > > > > >  > > > > > > > > Tassero GmbH > > > > Mies-van-der-Rohe Straße 8 > > > > 80807 München > > > > > > > > Tel. : +49 (0) 89 – 545 583 26 > > > > E-Mail: office(a)tassero.com > > > > > > > > Registergericht: Amtsgericht München HRB 230669 > > > > UstId.: DE 310 271 391 > > > > > > > > Geschäftsführer: Heinrich Nako > > > > > > > > 663:1788124 > > > > > > Attachments : 1. attachment > > > > > > > > >  > > > > > > Regards, > > > Tassero GmbH Team > > > --------------------------------------- > > > > > >  > > > > > > Tassero GmbH > > > Mies-van-der-Rohe Straße 8 > > > 80807 München > > > > > > Tel. : +49 (0) 89 – 545 583 26 > > > E-Mail: office(a)tassero.com > > > > > > Registergericht: Amtsgericht München HRB 230669 > > > UstId.: DE 310 271 391 > > > > > > Geschäftsführer: Heinrich Nako > > > > > > 663:1788124 > > > _______________________________________________ > > > members-discuss mailing list > > > members-discuss(a)ripe.net > > > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > > > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> > > > > Attachments : 1. attachment > > > > > >  > > > > Regards, > > Tassero GmbH Team > > --------------------------------------- > > > >  > > > > Tassero GmbH > > Mies-van-der-Rohe Straße 8 > > 80807 München > > > > Tel. : +49 (0) 89 – 545 583 26 > > E-Mail: office(a)tassero.com > > > > Registergericht: Amtsgericht München HRB 230669 > > UstId.: DE 310 271 391 > > > > Geschäftsführer: Heinrich Nako > > > > 663:1788124 > > _______________________________________________ > > members-discuss mailing list > > members-discuss(a)ripe.net > > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> > > Attachments : 1. attachment > > >  > > Regards, > Tassero GmbH Team > --------------------------------------- > >  > > Tassero GmbH > Mies-van-der-Rohe Straße 8 > 80807 München > > Tel. : +49 (0) 89 – 545 583 26 > E-Mail: office(a)tassero.com > > Registergericht: Amtsgericht München HRB 230669 > UstId.: DE 310 271 391 > > Geschäftsführer: Heinrich Nako > > 663:1788124 > _______________________________________________ > members-discuss mailing list > members-discuss(a)ripe.net > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" rel="noreferrer">https://lists.ripe.net/mailman/listinfo/members-discuss</a> > Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…" rel="noreferrer">https://lists.ripe.net/mailman/options/members-discuss/oliver.roth%40nexpho…</a> </div> Attachments : 1. <a href='https://help.tassero.de/helpdesk/attachments/80236502736'>attachment</a> Regards, Tassero GmbH Team --------------------------------------- Tassero GmbH Mies-van-der-Rohe Straße 8 80807 München Tel. : +49 (0) 89 – 545 583 26 E-Mail: office(a)tassero.com Registergericht: Amtsgericht München HRB 230669 UstId.: DE 310 271 391 Geschäftsführer: Heinrich Nako

1 0