[anti-abuse-wg] Abuse-c documentation

/faqs-for-abuse-c Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

[anti-abuse-wg] Cleanup work for "abuse-mailbox:" in certain ORGANISATION objects, following policy 2011-06

ns with interest and we believe that this part of the originally proposed cleanup should be put on hold until we have a more clear direction from those discussions. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

Re: [anti-abuse-wg] RIPE NCC to set abuse-c for remaining organisation with ASNs or other resources allocated or assigned by the RIPE NCC

e contact to something else before we create it. However no action is necessary in case they are happy with the email address we will use in the object, and they can of course also modify the abuse-mailbox later. Regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC >

Re: [anti-abuse-wg] [db-wg] RIPE NCC to set abuse-c for remaining organisation with ASNs or other resources allocated or assigned by the RIPE NCC

Hi all, To clarify, we do not create duplicates or overrides. > On 16 Dec 2015, at 16:54, denis wrote: > > Hi Tim > > On 16/12/2015 15:58, Tim Bruijnzeels wrote: >> Hi, >> >>>>> >>>>> To expedite the creation of abuse contacts we&#

Re: [anti-abuse-wg] [db-wg] RIPE NCC to set abuse-c for remaining organisation with ASNs or other resources allocated or assigned by the RIPE NCC

Hi, > On 16 Dec 2015, at 15:48, Piotr Strzyzewski > wrote: > > On Wed, Dec 16, 2015 at 03:34:26PM +0100, denis wrote: > > Dear Denis, > >> On 16/12/2015 11:32, Alex Band wrote: >>> Hi Michele, >>> On 15 Dec 2015, at 21:28, Michele Neylon - Blacknight wrote: Tim >>

[anti-abuse-wg] RIPE NCC to set abuse-c for remaining organisation with ASNs or other resources allocated or assigned by the RIPE NCC

avoid doing this at the same time as the start of the year invoicing. Please let us know what you think. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

Re: [anti-abuse-wg] [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

ieve it's best to discuss this in more detail then. But to be absolutely clear: we would only implement after working group discussion and consensus called by the chairs. The same applies obviously for other proposals and suggestions mentioned in this thread. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

Re: [anti-abuse-wg] WHOIS (AS204224)

are happy to provide rough estimates when asked to do so, and we can make more refined estimates and implementation plans once consensus is clear. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

Re: [anti-abuse-wg] [routing-wg] [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

nd when we have a clear consensus on a go-ahead. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

Re: [anti-abuse-wg] abuse-c cleanup

ether abuse-c has been set, because it's not mandatory and we often find that this makes dealing with requests longer. But that said, the above is only a partial picture of this, and this should in our view be discussed in the database working group. We can implement after consensus is called. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC