NRTM proposal

Hello,

about the NRTM problem.

NRTM works by requesting objects by specifying a range of serials
numbers. The NRTM client usually requests from the last processed
serial number upwards until he reaches the maximum serial number
available in the source server. (See the RIPE-DB doc for explanation)

But all the NRTM client gets (and the server sends) is a 
(ASCII) stream of objects with the appropriate action to 
take (add / delete). 

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)

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?

best regards,

  Arnd

-- 
NetHead                         Network Design and Security
Arnd Vehling                    av at nethead.De
Gummersbacherstr. 27            Phone: +49 221 8809210
50679 Cologne, Germany          Fax  : +49 221 8809212