[db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Previous message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Next message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed May 11 17:31:46 CEST 2016
Dear Tim, On Wed, May 11, 2016 at 05:26:24PM +0200, Tim Bruijnzeels wrote: > 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 > > > 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. > > 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. > > If option a is preferred we need to know this by Friday afternoon > latest, so that we can prepare. Good write up Tim, thanks. I prefer option b and an update to "last-modified:". Kind regards, Job
- Previous message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
- Next message (by thread): [db-wg] RIPE Database: Cleaning-up Organisation Names in "descr:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]