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/[email protected]/

[db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01

Previous message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Next message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Randy Bush randy at psg.com
Mon Mar 7 21:01:37 CET 2016

> It has been implemented for the whole of the address space allocated
> or assigned by the RIPE NCC. We spent 6 months 'encouraging' members
> to deploy it, then another year 'encouraging' PI holders to deploy
> it. ...

and 42% of those addresses black-hole or bounce.  and we keep tilting
at this windmill.

> The legacy resources are the only resources in the RIPE Database that 
> currently do not all have an abuse-c. If you use the tools provided by 
> the NCC you should not need to do any manual lookups or read comments.

and the black-hole and bounce fraction will be higher.

wake up and smell the coffee.

randy

Previous message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Next message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]