- members-discuss - mailman.ripe.net

Future RIPE NCC Charging Scheme Proposals
by office＠mrejitor.com 15 Dec '25

15 Dec '25

Dear community, I looked at both Category-based and Formula-based models and found a destructive issue with both. The root issue The scheme is too logarithmic. The average fee per IP ranges 5744 times! * The issue leads to the following consequences. Consequence one - market competition Members with fewer addresses should pay a significant share of their income to RIPE. There are many services in the â¬10 or less category in Bulgaria, Romania, and other countries. Small /24 operators should spend at least 4.47% of their income on RIPE fees alone. A prominent /8 owner will spend 0.00001% of that income. The ratio of 5,743 is significant. Consequence two - delaying the move to IPv6 Given the significant historical IPv4 address space, larger companies have fewer reasons to switch to IPv6. If we agree to further multiply this advantage, there will be fewer and fewer economic reasons to switch to IPv6. Consequence three - possible reduction in the number of LIRs With ratios of up to 5,743 times the fees per IP, one can expect the consolidation of LIR accounts to continue. Renting small blocks will be preferable to acquiring them. We already suffer from the declining number of LIR accounts. A decision that leads to future consolidation may require additional rebalancing in the coming years. Possible solutions * Better-balanced fees, with wider boundaries in both directions. A difference of no more than 256 times in per-ip fees. * A fee reduction for big entities if they return address space to RIPE. This reduction will actually pay off by reducing IPv4 queue wait time and, therefore, increasing the number of new members. Best Regards, Alexander 5744 is calculated by dividing the minimum fee per IP for /8 by the cost for /24. It could be up to 11,487 in case the address space is close to /7 IPv4 CIDR Max fee/ IP Discount from /24 /24 to /23 3.41016 0.00% /23 to /22 2.47656 27.38% /22 to /21 1.64746 51.69% /21 to /20 1.03906 69.53% /20 to /19 0.63306 81.44% /19 to /18 0.37598 88.97% /18 to /17 0.21918 93.57% /17 to /16 0.12585 96.31% /16 to /15 0.07143 97.91% /15 to /14 0.04013 98.82% /14 to /13 0.02237 99.34% /13 to /12 0.01237 99.64% /12 to /11 0.00681 99.80% /11 to /10 0.00372 99.89% /10 to /9 0.00203 99.94% /9 to /8 0.00110 99.97% /8 to /7 0.00059 99.98%

1 0

Re: Systematic RIPE DB abuse
by Lu Heng 12 Dec '25

12 Dec '25

You are mixing two fundamentally different things: *1. Community-platform rules (like mailing lists)* *2. Number-resource administration (the registry function)* A registry absolutely may moderate its mailing list or remove someone from a community forum. That is *not* the issue. That is not resource governance. That is not number administration. The problem arises when you conflate the mailing list with the registry function and assume the same “ban power” applies to number resources. It does not. A registry’s authority over number resources is *administrative*, not discretionary: • It has no sovereign power. • It cannot impose penalties outside the law. • It cannot “ban” someone from holding number resources because it dislikes their actions. • It cannot create new enforcement powers through internal rules. Mailing-list rules are internal community guidelines. Number-resource allocation is part of global critical infrastructure. These are not equivalent domains. The fact that a registry can enforce behavior on a mailing list does *not* grant it the authority to punish a member by altering or revoking their number resources. The two functions exist on different legal, operational, and governance layers. If you do not separate these layers, you end up with exactly the instability we see today: registries treating essential resource administration as if it were a social-media moderation problem. A registry is allowed to moderate conversations. A registry is *not* allowed to weaponize the address book. That is the distinction you must not blur. On Thu, 11 Dec 2025 at 12:33, Peering <peering(a)all-for-one.com> wrote: > This is not about punishing or violating laws but violating the rules of > usage of the registry. While doing so, it should be normal to get banned > from that registry and the usage of the abused resources like the Mailing > list. So far fully fits in your position, as the rules of usage are given > by the registry it’s also the only given authority that can enforce them. > > > > *Von:* Lu Heng <h.lu(a)anytimechinese.com> > *Gesendet:* Mittwoch, 10. Dezember 2025 21:49 > *An:* Michele Neylon - Blacknight <michele(a)blacknight.com> > *Cc:* Sergey Myasoedov via members-discuss <members-discuss(a)ripe.net> > *Betreff:* [members-discuss] Re: Systematic RIPE DB abuse > > > > Michele, > > > > Let me clarify, because this is not a question of “no rules.” > > > > My position is straightforward: > > > > A registry is a registry. > > Its mandate is to maintain accurate records—nothing more. > > You do not use an address book as an instrument of punishment. > > > > When a registry begins using essential administrative functions to reward > or punish individuals, the system becomes unpredictable and open to abuse. > This is, in fact, a major reason the RIR environment has struggled with > instability and governance issues: registries have, at times, stepped > outside their neutral role and attempted to use resource administration as > leverage. > > > > Rules absolutely must exist, and compliance is essential. > > But those rules are defined and enforced by sovereign law—courts, > regulators, and proper authorities—not by a voluntary address book. A > registry cannot impose its own rules above nations, nor can it act as > police, prosecutor, and judge. > > > > Punishment, when warranted, must come through established legal channels. > A registry that assumes enforcement powers beyond its mandate ultimately > undermines its own legitimacy and the trust of the global community. > > > > That is the core of my position. > > > > Regards, > > Lu > > > > > > > > > > On Wed, Dec 10, 2025 at 16:19 Michele Neylon - Blacknight < > michele(a)blacknight.com> wrote: > > Lu > > > > Sorry but I cannot agree with your position on this. > > > > By your logic RIPE NCC would have zero right to take action against a > member who was in breach of the policies, rules etc., > > > > Trust in the system is only possible when the system is stable and > predictable, which you seem to agree with, however if there are no rules > then any system will be abused by somebody at some point. > > > > Regards > > > > Michele > > > > -- > > Mr Michele Neylon > > Blacknight Solutions > > Hosting, Colocation & Domains > > *https://www.blacknight.com/ <https://www.blacknight.com/>* > > *https://blacknight.blog/ <https://blacknight.blog/>* > > Intl. *+353 (0) 59 9183072 <+353599183072>* > > Personal blog: *https://michele.blog/ <https://michele.blog/>* > > Some thoughts: *https://ceo.hosting/ <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: *Lu Heng <h.lu(a)anytimechinese.com> > *Date: *Wednesday, 10 December 2025 at 13:15 > *To: *Brett Sheffield <ripe(a)gladserv.com> > *Cc: *Sergey Myasoedov via members-discuss <members-discuss(a)ripe.net> > *Subject: *[members-discuss] Re: Systematic RIPE DB abuse > > *[EXTERNAL EMAIL]* Please use caution when opening attachments from > unrecognised sources. > > Hi > > > > I agree entirely NCC should not do anything. A registry’s role is > administrative, not enforcement. Asking a bookkeeping-type institution to > police behavior is simply outside its mandate and purpose. > > > > There are countless legitimate ways to address concerns or resolve > disputes. But withholding a fundamental registry service—such as assigning > an address—because someone “did or did not do X” is irrational and > unprecedented. It is the equivalent of a government refusing to give a home > an address instead of contacting law enforcement or using proper legal > channels. No responsible system operates that way, and no credible > governance framework treats essential registry functions as a tool for > punishment or leverage. > > > > A registry should remain neutral, predictable, and strictly procedural. > Using it as an enforcement mechanism undermines trust in the entire system. > > > > > > -- > Kind regards. > Lu > > > > > > On Wed, Dec 10, 2025 at 14:38 Brett Sheffield <ripe(a)gladserv.com> wrote: > > On 2025-12-08 12:57, Sergey Myasoedov via members-discuss wrote: > > Dear RIPE NCC members, > > > > I’d like to raise the topic of introducing and applying administrative > anti-spam measures against RIPE NCC members who deliberately violate > Article 4 of the RIPE Database Terms and Conditions. > > > > RIPE NCC requires members to publish up-to-date contact email addresses > in the RIPE DB. However, these publicly listed addresses are actively > harvested and used for spam by IPv4 brokers and address traders, while RIPE > NCC does not take any measures to protect members from this type of abuse. > > > > This issue has been around since the IPv4 market appeared, and although > it’s well known, at some point the RIPE NCC staff chose not to act against > members who don’t follow the RIPE Database T&C. > > > > My proposal is to freeze transfer operations for members who are > repeatedly abusing the RIPE Database. > > > > I’d be glad to hear your thoughts and discuss this further. > > Compared to other sources, our RIPE contact address gets a tiny amount of > spam, > and all of it from IPv4 brokers. > > I've now received more emails in this single thread in the past 24 hours > than I > have spam to our RIPE contact address in the past 5 years. No action from > RIPE > is required here. > > Tighten your spam controls if this is a problem for you, and lets move on. > > Cheers, > > > Brett > -- > Brett Sheffield (he/him) > Gladserv > To unsubscribe or manage your subscription, log in to the LIR Portal with > your > RIPE NCC Access account and go to the LIR Account page: > https://my.ripe.net/#/account-details. > > Scroll down to Membership Mailing Lists to update your 'members-discuss' > subscription. > > Having issues unsubscribing? More information about managing your > subscription > can be found at: > https://www.ripe.net/s/members-discuss-subscription-options/ > > -- -- Kind regards. Lu

6 9

Systematic RIPE DB abuse
by Sergey Myasoedov 11 Dec '25

11 Dec '25

Dear RIPE NCC members, I’d like to raise the topic of introducing and applying administrative anti-spam measures against RIPE NCC members who deliberately violate Article 4 of the RIPE Database Terms and Conditions. RIPE NCC requires members to publish up-to-date contact email addresses in the RIPE DB. However, these publicly listed addresses are actively harvested and used for spam by IPv4 brokers and address traders, while RIPE NCC does not take any measures to protect members from this type of abuse. This issue has been around since the IPv4 market appeared, and although it’s well known, at some point the RIPE NCC staff chose not to act against members who don’t follow the RIPE Database T&C. My proposal is to freeze transfer operations for members who are repeatedly abusing the RIPE Database. I’d be glad to hear your thoughts and discuss this further. -- Best regards, Sergey Myasoedov > Begin forwarded message: > > From: "HostM" <info(a)hostmaster.lt> > Subject: Quick question about IPv4 > Date: December 8, 2025 at 04:54:23 EST > To: <for-spammers(a)net-art.cz> > > Hello, > my apologies if this message has arrived at an inconvenient time. > > I wanted to check whether you might be interested in acquiring an IPv4 /24 sub-net registered with RIPE. > I also have IPv6 resources and an ASN available, which can be included (for free) if you are interested in the IPv4 block. > > The ipv4 sub-net is currently unused and fully clean. > > The transfer can be completed securely via an escrow service. > > If this could be of interest, please feel free to reply to this email, and we can discuss the next steps in more detail. > > Regards, > Zydrunas

17 25

Analysis on Participation in October 2025 GM
by Ilke Ilhan 24 Nov '25

24 Nov '25

Hi all, Following the GM on 22 October, we analysed participation and shared some stats in this RIPE Labs article. This time, we also tried to distinguish the dedicated and casual voters in the last three years. https://labs.ripe.net/author/ilke-ilhan/gm-october-2025-a-look-at-dedicated… Let us know what else you'd like to see covered in these post-GM pieces. Cheers, Ilke

1 0

RIPE NCC Strategy Open House: Recording and Presentation Available
by Fergal Cunningham 03 Nov '25

03 Nov '25

Dear all, Last week, we held an Open House on the Draft RIPE NCC Strategy 2027-2031. The recording and presentation are now available at: https://www.ripe.net/meetings/open-house/strategy-2027-2031/ The session saw a presentation on the draft strategy from our Managing Director and CEO, Hans Petter Holen, before we took input from members who attended. We also shared early results from our consultation survey, which we are encouraging all members to take before the end of October: https://www.ripe.net/s/draft-strategy-consultation-survey There will also be a strategy BoF at the RIPE 91 Meeting on Thursday next week. We hope to have a good interactive session with members and community on the direction we need to take in the coming years, so please register to attend the meeting if you wish join online: https://ripe91.ripe.net/ Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

3 3

Time to revisit RIPE and cloud?
by Hank Nussbacher 30 Oct '25

30 Oct '25

Perhaps the time has come to once again review RIPE's cloud strategy: https://labs.ripe.net/author/felipe_victolla_silveira/ripe-ncc-cloud-strate… As recent outage events have shown: https://azure.status.microsoft/en-us/status/history/ https://aws.amazon.com/message/101925/ Hyper-cloud providers have super complex setups with many inter-dependencies, and it is unlikely that any one relevant tier-3 NOC person understands the entire setup. These outages will continue to happen and perhaps even more often than we expect. In regards to security: https://www.darkreading.com/cloud-security/microsoft-azure-cloud-vulnerabil… https://www.wiz.io/blog/38-terabytes-of-private-data-accidentally-exposed-b… Does RIPE still want to place some of their eggs in this extremely fragile cloud? Regards, Hank

1 0

Draft Activity Plan and Budget 2026 Open House: Recording Available
by Karla Liddle-White 09 Oct '25

09 Oct '25

Dear all, Last week, we held an Open House on the Draft RIPE NCC Activity Plan and Budget 2026. The recording is now available at: https://www.ripe.net/s/open-house/Draft-Activity-Plan-and-Budget-2026/ The session saw a statement from our Executive Board Chair and presentations from our Managing Director and Chief Financial Officer. These were followed by a Q&A with members. If you have comments or opinions you'd like to share on the draft activity plan, please discuss on this list so we can consider your input when drafting the final version of the document in December. Also, a reminder that there is an online session today at 11:30 UTC to discuss the Draft Strategy 2027-2031. You can register for the Open House at: https://www.ripe.net/s/open-house/strategy-2027-2031/ Kind regards, Karla Liddle-White Senior Communications Officer RIPE NCC

1 0

Cyberattaques massives en cours – Mesures prises par ASII Télécom
by support＠asii.fr 09 Oct '25

09 Oct '25

ASII Télécom Logo [https://lih2.mj.am/img2/lih2/349c7458-3f17-400d-977b-5e90b5dd2aaa/content] ⚠️ INCIDENT EN COURS – CYBERATTAQUES SUR LES OPÉRATEURS ET HÉBERGEURS Communication officielle – Sécurité & Réseaux Bonjour, Nous vous informons qu’une cyberattaque massive affecte actuellement plusieurs opérateurs télécom (Orange, Free, SFR) ainsi que des hébergeurs majeurs (OVH, Ionos). Cette situation provoque des perturbations nationales sur certains services. Voici les informations essentielles et les mesures prises par nos équipes. 🔍 Situation actuelle * Des incidents sont confirmés sur plusieurs infrastructures d’opérateurs et d’hébergeurs. * Les attaques sont principalement de type DDoS (saturation de trafic). * Aucune fuite de données n’est confirmée à ce stade. * Les équipes de cybersécurité sont mobilisées pour stabiliser la situation. 🛡️ Nos actions immédiates * Surveillance renforcée de toutes nos infrastructures réseau et serveurs. * Isolation des systèmes critiques pour éviter toute propagation. * Sauvegardes et redondance activées sur nos environnements sécurisés. * Support technique renforcé pour répondre à toutes les alertes clients. ✅ Recommandations pour nos clients ActionObjectif Vérifiez vos servicesSignalez tout dysfonctionnement anormal Changez vos mots de passe sensiblesRenforcez la sécurité de vos accès Activez l’authentification 2FAAjoutez une protection supplémentaire Surveillez vos logsDétectez toute activité suspecte 📆 Prochaines étapes Un rapport d’impact complet sera publié dans les 24 à 48 heures, avec le détail des actions menées et les solutions de résilience à long terme. Notre priorité absolue reste la protection de vos données et la continuité de vos services. Contacter le support ASII [support(a)asii.fr] © 2025 ASII Télécom – Sécurité, Réseaux & Hébergement Cet email est une communication officielle destinée à nos clients professionnels. www.asii.fr [https://asii.fr] Pour ne plus recevoir nos communications : se désabonner http://lih2.mj.am/unsub2?hl=fr&m=AWwAAIC1vpAAAc634sAAA9iqd5UAAAAAAAQAoGfvAA….

1 0

Reminder: Open House on Draft Activity Plan and Budget 2026 This Week
by Fergal Cunningham 30 Sep '25

30 Sep '25

Dear all, At 11:30 UTC on Thursday, 2 October this week, there will be a RIPE NCC Open House to discuss the Draft RIPE NCC Activity Plan and Budget 2026. There will be presentations from our Managing Director, Hans Petter Holen, and our Chief Financial Officer, Simon-Jan Haytink, who will give an overview of our plans for next year and the associated budget. Our Executive Board will also be there to hear your feedback and answer your questions. We hope you will take the time to participate at this online event. You can register to attend now at: https://www.ripe.net/s/open-house/Draft-Activity-Plan-and-Budget-2026/ The Draft Activity Plan and Budget 2026 is available at: https://www.ripe.net/about-us/news/draft-activity-plan-and-budget-2026-publ… For those unable to attend, we will record the session and publish it on our website. I will be moderating the session, so if there are questions you would like to put to the presenters or the Board, please feel free to let me know and I will make sure to raise the topic for you. Below this mail, I also include links to next week’s Open House on the Draft RIPE NCC Strategy 2027-2031 and a link to our member consultation survey on the strategy that we hope you will fill out. We look forward to seeing you online to discuss our plans for next year and beyond. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC Open Member and Community Consultations: https://www.ripe.net/membership/mail/member-and-community-consultations/ Draft RIPE NCC Strategy 2027-2031 Open House: https://www.ripe.net/s/open-house/strategy-2027-2031/ Draft RIPE NCC Strategy 2027-2031 - Document and Consultation Survey: https://www.ripe.net/s/draft-strategy-consultation/

1 0

Moderation of the Members Discuss Mailing List
by Fergal Cunningham 26 Sep '25

26 Sep '25

Dear all, In June this year, the RIPE NCC Executive Board passed a resolution to temporarily place the members-discuss mailing list under moderation following the posting of inappropriate mails to the list. At its recent meeting on 4-5 September, the Board passed a further resolution to keep moderation on the list permanently. The Board took this decision because moderation has been activated for the list periodically when discussions become heated. The Board intends that this will bring a stable situation and ensure discussions are always carried out in a respectful and productive manner. The relevant section of the minutes from the recent Board meeting are available at: https://www.ripe.net/s/188th-executive-board-meeting-minutes/116/ The Board also decided to amend the process by which moderation takes place in order to streamline the process and ensure mails are processed as quickly as possible. Rather than having a RIPE NCC staff member and an Executive Board member jointly moderate the list, now the list will be jointly moderated by a member of the RIPE NCC’s Legal and Communications Departments. With this new process, emails will continue to be moderated in accordance with the RIPE Code of Conduct and the purpose of the mailing list. Members who feel their mails have not been moderated correctly can appeal by sending a mail to the Board at: exec-board(a)ripe.net. If the Board agrees that a mail has not been moderated correctly, they will instruct the RIPE NCC to process the mail through to the list. Additionally, all mails sent to members-discuss, whether moderated or not, are visible on the Unmoderated Members Discussion List for three months should you wish to check how mails are processed: https://mailman.ripe.net/archives/list/members-discuss-unmoderated@ripe.net/ The Board and RIPE NCC staff thank you for your understanding, and we look forward to seeing good discussions in the coming weeks and months on the Draft RIPE NCC Strategy, the Draft Activity Plan and Budget and proposals around the RIPE NCC Charging Scheme. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0