Special ftp access for IRR?

Daniel Karrenberg (Daniel.Karrenberg at ripe.net) on February 28:
> 
> 
> The medium term soloution as discussed in San Jose:
> 
> Update arrives. 
> 
> If not the proper server, forward it there.
> 
> Check local authorisation syntax etc.
> 
> If OK: 
> 
> Process locally.
> 
> Make local notifications.
> 
> Make a record of the following atomic operations.
> 
> 	append object
> 	replace object (same as append)
> 	delete object 
> 
> Add serial number.
> 
> Store in file.
> 
> File are closed at specific intervals and named 
> to something reflecting the serials or time contained.
> 
> Files will be available by FTP.
> 
> Files can be sent by other means (mail etc) at specific
> intervals on request.
> 
> 
> This is easy to implement?
> 
> Design bugs?

I like it. Hence people can only ftp the changes (i.e. diffs) as
opposed to whole database. This saves them a lot in re-indexing.

We also aggreed to keep a file which includes the diffs up to the
current time. So if one wants a copy of the ripe database as current
as possible, he would get this diff.

Cengiz

-- 
Cengiz Alaettinoglu       Information Sciences Institute
(310) 822-1511            University of Southern California



-------- Logged at  Tue Feb 28 20:07:27 MET 1995  ---------