<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <tt>Hi William</tt> <tt>If we are going to follow the NWI then lets define the problem and then look at available options to fix it. There are other ways to fix it and each option has pros and cons. </tt> <tt>cheers</tt> <tt>denis </tt> <tt> </tt> <div class="moz-cite-prefix">On 02/11/2016 23:50, William Sylvester wrote: </div> <blockquote cite="mid:806F92F8-23DD-4732-90A6-FD351912B88B@addrex.net" type="cite"> <pre wrap="">I support this. William </pre> <blockquote type="cite"> <pre wrap="">On Nov 2, 2016, at 5:53 AM, Sebastian Wiesinger <a class="moz-txt-link-rfc2396E" href="mailto:sebastian@karotte.org"><sebastian@karotte.org></a> wrote: I'm currently struggling with abuse-c management for a big organisation which wants multiple abuse contacts for different parts of the organisation. The org is using a lot of PI resources, some of them legacy. Currently they all use the same org object which is inextricably linked to the same abuse-c mailbox. They have a new field of business which is mostly decoupled from the rest (own AS, own routers, PI space, etc.) but still uses the same org object. As cumbersome as having to create a new org object would be, I would've gone this road but as all of them are PI I can't change the org object! It is managed by the RIPE NCC. So the only solution right now would be to ask the RIPE NCC to change the org for all objects to a new one just to change the abuse-c for the resources. I would not be surprised if this turns out to be more complicated because of the end-user contract stuff but I'll need input from the NCC how they handle such cases. Also having multiple org objects that have the same data (company name, address, phone,...) just to have a different abuse-c is something that irks me to no end. Now I have to update X orgs when the phone number or address changes. Also: redundant data in the database! I tried to follow past discussions regarding this but it seems they all kind of fizzed out without any conclusion? I would propose to fix this and add an abuse-c to resource objects that would be "more specific" than the org abuse-c and overrides it. If there are other ideas please don't hesitate to state them but to me it seems like a low-cost solution to this mess. Best Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant </pre> </blockquote> <pre wrap=""> </pre> </blockquote> </body> </html>