comments followed.
-----Original Message----- From: Arnd Vehling [mailto:av@nethead.de] Sent: Monday, March 11, 2002 4:01 AM To: Lu, Ping Cc: 'Andrei Robachevsky'; Bjorn Danielsson; db-beta@ripe.net; 'db-wg@ripe.net'; Dieken, Chris; Beaumont, Dave; Resh, Stephanie; phil@nethead.de Subject: Re: NRTM proposal
[snip]
If receiving a stream with objects considered "non-standard", or private, all the nrtm client (or the server) has to do is to filter out objects (and maybe attributes) which are considered of private nature. The client doesnt need to know anything about which serial number relates to which object. (i.e. The serial-numbers must not be in sync between a source server and the mirror)
If you don't care whether the serial-numbers match or not then how can you tell the mirrored data is up-to-date ?
This can easily be accomplished by creating a perl script which filters the NRTM ascii stream.
Actually we are using such a script for synchronizing our local ip-management ripe-database with the RIPE amsterdam.
Could you therefore please elaborate on where you are seeing a problem with the serial-numbers while mirroring?
As I said before if the client can do whatever they want without maintaining the correct serial-numbers then how can you tell the data is up-to-date ? Best Regards. Ping Lu Cable & Wireless USA Network Tools and Analysis Group W: +1-703-292-2359 E: plu@cw.net