Special ftp access for IRR?

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

Mostly, except for the last two items... :)

> 
> Design bugs?
> 
Scaleability?  Human intervention?  Except for the last two, this sounds alot
like the DNS update sequence.  The ability to "notify" those who might run 
a backup service for you and to automatically send the updates would rest 
my worried mind.  Not that what I care about matters of course.

--bill



-------- Logged at  Tue Feb 28 17:13:40 MET 1995  ---------