This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
NRTM proposal
- Previous message (by thread): NRTM proposal
- Next message (by thread): NRTM proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arnd Vehling
av at nethead.de
Tue Mar 12 16:35:14 CET 2002
"Lu, Ping" wrote: > me wrote.. > > To be more precise. The data is up to date if the highest > > serial number > > on the mirror server matches the highest serial number on the client. > > > Exactly. That's why the client can't just ignore any private object. It will > need to do a dummy update to advance the serial numbers. Nope. The only thing which the client really needs to know is the highest serial number _he_, the client, did process. If the highest serial number internal to the datastructure of the client matches the one of the mirror source is of no concern. Please keep in mind that i can write a mirror client which doesnt needs to have the same structure as the ripe-db and therefore may very well miss a "serial" number like the ripe-server has. 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
- Previous message (by thread): NRTM proposal
- Next message (by thread): NRTM proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]