Dear WG, Denis, Thank you. Then we will proceed as proposed and do the clean-ups and notifications in one go on Monday 30 October. In the meantime, if you still have an opportunity to look at the 1.90 release in the RC environment, please do - and let us know if you find any issues. We plan to deploy this version to production on Monday 16 October. Thanks Tim
On 29 Sep 2017, at 15:39, denis walker <ripedenis@yahoo.co.uk> wrote:
Hi Tim, colleagues
No one has expressed any serious concerns over this small change. I think we can safely go ahead and only send the one email notification in these cases when you change the objects.
cheers denis co-chair DB-WG
----- Forwarded Message ----- From: denis walker via db-wg <db-wg@ripe.net> To: Database WG <db-wg@ripe.net> Sent: Wednesday, 27 September 2017, 11:55 Subject: [db-wg] Fw: NWI-7: abuse-c implementation plan modification
Colleagues
I think the suggestion below from Tim is OK. There seems little point sending notifications to users about changes they don't need to take action on of data that is redundant. So if anyone has any strong objections please let us know by the end of this week. Otherwise we can give Tim the go ahead to this modification to the implementation plan.
cheers denis co-chair DB-WG
From: Tim Bruijnzeels via db-wg <db-wg@ripe.net> To: "db-wg@ripe.net" <db-wg@ripe.net> Sent: Wednesday, 30 August 2017, 21:32 Subject: Re: [db-wg] NWI-7: abuse-c implementation plan
Dear working group,
We have a proposed timeline for the implementation. Let me quote the proposal sent out on 28 June here, and comment in-line:
3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases)
In these cases we propose to send a warning email to the holders of these objects with the following main message:
“The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects."
And then 4 weeks later we will preform the clean-up and refer back to this communication.
On further reflection we would prefer to alter the plan, and just a single clean-up of these objects on Monday 30 October as well. This way the clean-up process will be consistent across all object types. Furthermore, there is no action to be taken on these objects and “abuse-mailbox:” on these objects is ignored in the Abuse Finder. In short there does not seem to be a strong motivation for bothering the holders of these objects twice.