Invalid data in the RIPE database
- Previous message (by thread): Invalid data in the RIPE database
- Next message (by thread): Invalid data in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Tue Apr 26 09:41:50 CEST 1994
Daniel Karrenberg <Daniel.Karrenberg at ripe.net> writes * * > Laurent Joncheray <lpj at merit.edu> writes: * > Dear database managers, * > i had a look at some entries in the RIPE database and at the * > 'nsf-in' network attribute. For a lot of them the value in the RIPE * > db is inconsistant with the Merit (NSF) database... * * More radical question: Considering that the NSFnet is going away and * the routing registry has routing policy, should these attributes * be deprecated or even removed totally? Jean-Michel writes * 1- obsolete this field. * 2- Implement what Laurent proposes (automatic download from Merit). 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 this information useful currently, wrong information is worse than no information. I'd say obsolete. -Marten
- Previous message (by thread): Invalid data in the RIPE database
- Next message (by thread): Invalid data in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]