[Dundi] Caching

[Mark Spencer]

> 	I would rather see a mechanism for Announcers to push changes into
> the peer group. Changes delays then become a function of convergence time
> rather than TTL.

This becomes totally unmanagable with a large system because essentially 
every node must know the routes for all numbers as they come and go. 
Definitely a bad idea.  However, we recently added a "PRECACHE" function 
to DUNDI so that, for example, smaller nodes could "PRECACHE" answers up 
to a more master node.

If this works, then we could setup a "best practices" policy that 
nodes with less than a thousand (or whatever the magic number is) 
routes would simply "PRECACHE" their answers up to one or two other nodes, 
rather than actually be queried the whole time.

What do people think about this?

> 	With the implementation of cascading changes, DUNDi will start to
> look more like BGP (which is where I think it needs to head anyway).

If that's what you think, you need to look at TRIP.  DUNDi is not, nor 
should it be, what TRIP is.  This is about "asking" not about advertising.

Mark