NRTM proposal

I believed we are talking about two different things:

In your scenario: Your client has a different serial number than RIPE's one.
let's say it goes like this,
RIPE:123 YOURS:111
RIPE:124 YOURS:111 (filter out)
RIPE:125 YOURS:112 
RIPE:126 YOURS:112 (filter out)
RIPE:127 YOURS:112 (filter out)
RIPE:128 YOURS:113
RIPE:129(for some reason it is lost) YOURS:113
RIPE:130 YOURS:113 (filter out)
RIPE:131 YOURS:114

How can you tell there is something missing ? Also next time the client
restart which serial number is it going to use ?

Our scenario: The client maintain the same serial number as RIPE's.
RIPE:123 OURS:123
RIPE:124 OURS:124 (dummy update)
RIPE:125 OURS:125 
RIPE:126 OURS:126 (dummy update)
RIPE:127 OURS:127 (dummy update)
RIPE:128 OURS:128
RIPE:129(for some reason it is lost) OURS:128 (client detect mismatch stop
here)


I want to stop discussion about different scenarios and just limit this to
the current
NRTM practice: NRTM server and client maintain the same serial numbers.

Best Regards.

Ping Lu
Cable & Wireless USA
Network Tools and Analysis Group
W: +1-703-292-2359
E: plu at cw.net


> -----Original Message-----
> From: Arnd Vehling [mailto:av at nethead.de]
> Sent: Tuesday, March 12, 2002 10:35 AM
> To: Lu, Ping
> Cc: 'Andrei Robachevsky'; Bjorn Danielsson; db-beta at ripe.net;
> 'db-wg at ripe.net'; Dieken, Chris; Beaumont, Dave; Resh, Stephanie; Phil
> Syskes
> Subject: Re: NRTM proposal
> 
> 
> "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
>