Invalid data in the RIPE database

Laurent Joncheray <lpj at merit.edu> writes
 * 	Why not deciding this by mail and doing it *now*? (since everybody
 * 	seems to agree)
 * 
 * 10 min to remove those lines from the DB file (grep -v is fine)
 * 10 min to disable the nsf-in attribute in the conf file (or dbupdate.pl)
 * 1h ? to rebuilt the index file.
 * 	No big deal...

Actually, just removing from the config and reindexing is enough, it
will dissapear automagically ...

 * > =I feel for Daniels and Jean-Michel's first option. They should
 * > =definately be deprecated (although I have always viewed them as info
 * > =only attibutes) and preferably removed. Although some people may find
 * > 
 * >   I agree with this point of view. 
 * > 
 * >   I'm going to put it on the agenda for the DB-WG at the Amsterdam
 * >   RIPE-Meeting. We should have a *short* review and then agree on a
 * >   proposal and a *timeschedule* to remove this information from the
 * >   database.

Since it is on the agenda, and needs to be discussed/approved, no
action will be taken here before the RIPE meeting. After that, it can
be implemented in the time frames Laurent put up.

-MT

PS I assume the same applies to nsf-out?