Dear Job This was only a short term action and the persistence of this remarks attribute will be dropped in the next release 1.74. We wanted to persist it for a short while otherwise the first auto-generated update would have removed it with little chance of it being noticed. Regards Denis Walker Business Analyst RIPE NCC Database Team

On 13/06/2014 11:50, Job Snijders wrote:

On Tue, May 27, 2014 at 04:24:45PM +0200, Denis Walker wrote:

RIPE Database software release 1.73.1 has now been deployed into production.

The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:"
attribute. We have also modified all legacy INETNUM objects and set the
"status:" to 'LEGACY'.

Is it possible to stop forcefully inserting this line:

    remarks: For information on "status:" attribute read <snip>

in one of the next releases? To be more specific: disable 
enforceRemarksRightBeforeStatus() for remarks about the 'status'
attribute.

As a method to inform resource-holders that something has changed I
think that one-shot inserting of remarks is a good method (next to
informing mailing-lists, twitter, etc), but these messages should not be
enforced too long. I'm fine with leaving the existing remarks in the DB,
just don't enforce on new updates after four weeks or so.

Kind regards,

Job