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 ]
Brian Nisbet
brian.nisbet at heanet.ie
Wed Apr 11 18:50:13 CEST 2012
"Brian Nisbet" wrote the following on 11/04/2012 13:13: > Chris, > > "Chris" wrote the following on 11/04/2012 11:03: >> On 04/10/2012 05:18 PM, Joe St Sauver wrote: >>> Maintenance of the database documenting who's been allocated/assigned >>> space is *core* to RIPE's mission. >> >> simply wrong. >> ripe's core is allocation. that's what they do. your mission is your >> private error. > > http://www.ripe.net/lir-services/ncc/functions > > Specifically the development and maintenance of the RIPE DB. 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. I do speak for the > NCC, but a substantial amount of the narrative recently has been around > keeping that registry up to date and, indeed, attempting to find new and > interesting ways of making sure the members put the right data in the > right place. As has been correctly pointed out, I managed to leave out a negative above. I do *not* speak for the NCC. Sorry for any confusion that may have caused. Brian.
- 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 ]