Re: [Roll] updating DAO caches - a proposal
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Roll] updating DAO caches - a proposal



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>>>>> "Richard" == Richard Kelsey <richard.kelsey at ember.com> writes:
    Richard> In a network where all nodes cache DAOs, a node that moves
    Richard> sends the contents of its cache to its new parent.  These
    Richard> propagate up the tree, with each node forwarding on only
    Richard> those prefixes which are new to its cache.  The forwarding
    Richard> stops when it reaches the least common ancestor of the
    Richard> node's old and new locations.

Please confirm... at the least common ancestor, the contents of the
cache change, but nothing is new..?

    Richard> In a mixed network, nodes with caches and nodes whose only
    Richard> caching ancestor is the root will have the same behavior
    Richard> as above.  A node without a cache will send its own DAO and
    Richard> set the Destination Advertisement Trigger to cause its

So, in effect, a node that does not cache, has a cache size of 0, so all
DAOs are always "new"

I think this works.

- -- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Finger me for keys

iQEVAwUBSwW5IYCLcPvd0N1lAQJvnQgAr0h5sziEUfQMXMRihoA8P6BQXjHyclvm
mLZ/pWURJu86DebH15uxpmSOJ+QDT/bTX7jAb6u2f1IBKutkH7e43nVXN5WBeLZZ
QwVlFosw5WD+fihEueG9af4Ah19nPPchJSSadnaOjXWE8om0akPEdJ8X84tXHjIQ
dECjapijLFyS/wcXPCkH/5ijijCebW4QjUJG+Ssv3vovcvxUd2C0miBR8vUcInh8
5K0MlDuzptG5mKJXgzNraXMx0xQMnNQQQ7yPXanUqKDHTNrypw/kaLUriMut2VJ/
eW9Zkr1wnX2BmKS/2yykq7lMTYSni70QlsZGWwwzKCNhyNIidGrHBw==
=0DwC
-----END PGP SIGNATURE-----

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.