Special ftp access for IRR?

  > bmanning at ISI.EDU writes:
  > > 
  > > 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?  

10s of mirror sites
order of 10,000 atomic operations/day

  > Human intervention?  

Not necessary.


  > Except for the last two, this sounds a lot like the DNS update sequence.  

Yes you can keep the current serial number available by -say- whois ;-)

  > The ability to "notify" those who might run 
  > a backup service for you and to automatically send the updates would rest 
  > my worried mind.  

The idea is to send them automatically by whatever means and have the
FTPable trails there for recovery if needed. 

  > Not that what I care about matters of course.

????



-------- Logged at  Tue Feb 28 19:24:43 MET 1995  ---------