NRTM proposal

Hi,

"Lu, Ping" wrote:
> 
> I believed we are talking about two different things:

Yupp.

We are not doing direct mirroring at the moment as we are not allowed
to put out CW-Europes allocation into a own registry  and get this
mirrored by RIPE.

> 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 ? 

You can only tell by comparing the objects.

> Also next time the client
> restart which serial number is it going to use ?

The client saves the last _processed_ serial number and goes on from 
there. Thats the way our e-mail synchronisation with the ripe works
at the moment as we are not able to mirror at the moment due to
several reasons.

[..]

One could log the serials of the dropped objects and count them,
for example.

> I want to stop discussion about different scenarios and just limit this to
> the current

ack

> NRTM practice: NRTM server and client maintain the same serial numbers.

No, thats RIPE-Software practice. The client only requests a serial-range
and the server sends this range. Obviously that practice has some constrains
when it comes to privat objetcs. Exchanging privat objects is obviously
out of the scope of this protocol. And object/attribute filtering on client
is IMO bad too. 
 
Due to this reason i opt for the following setup:

[Privat Registry] -> syncs with -> [official mirror server] <-> [mirror
client]

Whereas:

[Privat Registry]        (CWs) internal registry with privat objects
[Official mirror server] (CWs) Server containing only standard RPSL objects
of the registry
[mirror client]          RIPE, RADB etc.

That way all the privat objects stay private. In addition its not possible
to
query them externally, and only standard RPSL objects are exchanged with
external 
mirrors.

Another option is to enhance the NRTM protocol or start developing
distributed
registries.

BTW.: Filtering private attributes and classes (objects) out of an object
stream
      is easy to accomplish.

regards,

  Arnd