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] Introducing the RIPE NCC Report Form
- Previous message (by thread): [anti-abuse-wg] Introducing the RIPE NCC Report Form
- Next message (by thread): [anti-abuse-wg] Introducing the RIPE NCC Report Form
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Heinze
Chris.Heinze at consol.de
Wed Apr 11 14:49:13 CEST 2012
On 04/11/2012 02:13 PM, Brian Nisbet wrote: >> ripe's core is allocation. that's what they do. your mission is your private error. > > http://www.ripe.net/lir-services/ncc/functions right, that sums it up nicely, thanks. > Once all of v4 space is allocated (soon now, soon), the primary job of the NCC and the other four RIRs will be keeping a good registry. ripe's job isn't defined by and doesn't depend on whether or not v4 space is completely allocated (which it btw probably never will). keeping a good registry is as explained a service kindly provided by ripe to help - and it did that since the beginning. regards, Chris
- Previous message (by thread): [anti-abuse-wg] Introducing the RIPE NCC Report Form
- Next message (by thread): [anti-abuse-wg] Introducing the RIPE NCC Report Form
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]