[anti-abuse-wg] [db-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database
- Previous message (by thread): [anti-abuse-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database
- Next message (by thread): [anti-abuse-wg] [db-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco d'Itri
md at Linux.IT
Fri Nov 16 17:03:07 CET 2012
On Nov 15, Kaveh Ranjbar <kranjbar at ripe.net> wrote: > The RIPE NCC's proposed implementation plan of RIPE policy 563 (policy proposal 2011-06) titled "Abuse Contact Management in the RIPE Database" is as follows: Requiring that LIRs maintain a new and otherwise totally useless organization object for every customer who need a delegated abuse-c attribute is very inconvenient. At least unless that object can be simplified to contain only the abuse-c attribute and no other data. I believe that the original proposal (abuse-c attributes on hierarchical resources) would be much easier to deploy, even if it initially requires adding the abuse-c attribute to a (usually) small number of top-level inetnum objects. If LIRs with hundreds of directly-assigned resources are concerned about modifying them (are they?), then why not support both schemes? -- ciao, Marco -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20121116/f917b53c/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database
- Next message (by thread): [anti-abuse-wg] [db-wg] RIPE NCC's proposed implementation of Abuse Contact Management in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]