On Sat, 1 Aug 2026 at 18:32, Serge Droz via Security-wg < [email protected]> wrote:
> Here is what lac ich does: < > https://www.lacnic.net/5733/2/lacnic/how-to-validate-your-abuse-contact-to-unblock-access-to-milacnic > > > Unfortunately this doesn't change anything at all. What do you do with the LIR that just does nothing with abuse reports? The ONLY penalty we have right now is closure. If you are not willing to do that then the LIR is untouchable. The NCC has no IPv4 to give out. The LIR may have enough IPv6 to last them years. If not they can buy it on the open market. If the NCC refuses to administer the transfer that doesn't mean it won't happen. It is just not registered. Or they can lease more space and sub assign it to their customers. You can lock their objects in the RIPE Database. Then they just don't update them. As long as the LIR keeps paying it's fees to the NCC there is nothing you can do to them. As things stand there is no accountability, no penalty. It's either full closure or untouchable. We need a rethink and a reset. This is what I am working on.... cheers denis > > It's more than keeping an elaborate list of numbers, and neither they or > the world has ended. > > > So, this could be an easy start > > Then Morecambe added, e.g no action against specific abuse types. (I very > much favour a well defined list, even if it will miss edge casses). > > > I think if the argument is, ripe should never do more than run a db, > fighting abuse will have to happen elsewhere. > > I see ripe as a community that endures it stays nice. > > So start with some simple things: > > Verify folks reply. > Expand to action in specific casses. > > If we agree on this we can start to work out the mechanics. > > Best > Serge > > > On 1 August 2026 15:45:38 UTC, Gert Doering <[email protected]> wrote: > >> Hi, >> >> On Sat, Aug 01, 2026 at 01:45:15AM +0300, Sergey Myasoedov via Security-wg >> wrote: >> >>> On 7/31/2026, at 16:41, Nick Hilliard <[email protected]> wrote: >>>> >>>> The issue we have in the RIPE security wg, and before that, abuse-wg and >>>> anti-spam-wg, is that the solutions being proposed involves changing the >>>> nature of the RIPE NCC from a registry into an quasi-judicial and >>>> enforcement body. Essentially the arguments are of the form which could >>>> waspily be described as "politicians' logic": >>>> >>> >>> Technically, we crossed this line when we introduced not just the company >>> names, but also their registration numbers into the RIPE Database. NWI-21. >>> >> >> This very much sounds like a thing a registry would do, like, register >> numbers and document who has them, in an unambiguous way? So which line >> exactly was crossed by publishing more unambiguous holder info, for >> legal entities? >> >> Gert Doering >> -- NetMaster >> >> -- > Dr. Serge Droz > Director, Forum of Incident Response and Security Teams > https://first.org > ----- > To unsubscribe from this mailing list or change your subscription options, > please visit: > https://mailman.ripe.net/mailman3/lists/security-wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with > the email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/security-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
