On 2016 May 11 (Wed) at 17:26:24 +0200 (+0200), Tim Bruijnzeels wrote: :Dear working group, : :In answer to your question, let me ask the working group in return to take a decision by the end of the week. : :> As a follow up: Is "last-modified:" going to be updated? : :If the working group prefers, we will update "last-modified:". : :We did not intend to do so because this is a bulk change and not a *user* initiated change. This was always about : I have an extremely strong preference for last-modified to be updated. This *is* a modification. :> Will the "your objects got changed" mail be generated? : :Initially the intention was that we wouldn't because the clean-up affects 93k objects, out of which 49k have a 'notify'. This can result in too many support questions, especially in this busy time just before the RIPE Meeting. : :That said, we re-evaluated and we can send notifications, if we postpone the clean-up to a more quiet time. This implies that "descr:" remains maintained by RIPE NCC until then. : I have a preference (but not as strong) that the notification mail is generated. To me, that's the entire point of the notify field. Is it possible that the reason for this change be included in the notification mail? That may help reduce the number of support requests generated. :So, working group, please decide between the following: :a) Clean-up this Tuesday 17 May, with general announcement only :b) Clean-up on Thursday 2 June, with notifications, RS keeps enforcing "descr:" until then. : My preference is with notification, so #b. :If option a is preferred we need to know this by Friday afternoon latest, so that we can prepare. : :Kind regards, : :Tim Bruijnzeels :Assistant Manager Software Engineering :RIPE NCC -- "Under capitalism, man exploits man. Under Communism, it's just the opposite." -- John Kenneth Galbraith