This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
- Previous message (by thread): [anti-abuse-wg] *** Re: New on RIPE Labs: How We Will Be Validating abuse-c
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Thu Oct 11 21:17:03 CEST 2018
In message <DB5PR06MB1590D86126B81C0E1845FB3B94E10 at DB5PR06MB1590.eurprd06.prod. outlook.com>, Brian Nisbet <brian.nisbet at heanet.ie> wrote: >To address one point; Legacy resources are excluded because that is the way >that RIPE Policy works. That's rather like saying that the reason we have hurricanes is because God works in mysterious ways. Maybe you should elaborate and explain. I would appreciate it if you did. I'm sure that will be enlightening and educational, at least for me, as I'm still not even sure that I fully grasp or understand the concept of "legacy" resources within the RIPE region. (Up till now I had always been told that "legacy" resources only existed as such within the ARIN region.) Regards, rfg
- Previous message (by thread): [anti-abuse-wg] *** Re: New on RIPE Labs: How We Will Be Validating abuse-c
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]