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]/
[anti-abuse-wg] [db-wg] objection to RIPE policy proposal 2016-01
- Previous message (by thread): [anti-abuse-wg] [db-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] [db-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
dbwg at c4inet.net
Sat Mar 5 12:50:06 CET 2016
On Fri, Mar 04, 2016 at 09:00:27AM +0100, Gert Doering wrote: >The relevant question for the PDP is "does 2016-01 help achieve >the goal of better combatting Internet abuse"? In its current implementation, abuse-c: is not only useless, it's potentially harmful. -Either abuse-c: is nothing but a convenience for ops, in which case it shouldn't be mandatory or -abuse-c: is an important part of registry documentation in which case the NCC should ensure that whatever information in there points to someone who *handles abuse* The latter would actually amount to NCC telling registries how to manage their network - they MUST have abuse-handlers and they MUST publish their contact data. Where does it say that in the contract and how would it be enforced towards ERX holders who don't *have* a contract? In either case, "We will put in any old email address we have in our records for your org unless you fill it in yourself" is not good enough. rgds, Sascha Luck
- Previous message (by thread): [anti-abuse-wg] [db-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] [db-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]