On Mon, Nov 23, 2015 at 8:35 AM, Paul Jakma <[email protected]> wrote: > On Mon, 23 Nov 2015, Daniel Walton wrote: > > How the table_version in maintained for the peer structure looks a little >> odd. Typically if a peer's tblver is 57 you know that you have converged >> that peer for all prefixes whose tblver is <= 57. What you have above is >> just a counter for how many times something has been added/removed from the >> peer's adj_out. >> > > You could instead set the peer's tblver based on the max between the peer's >> current tblver and the tblver of the prefix being advertised. >> > > Add it as an attribute, or perhaps even a short message that can be > prepended to any and (almost) every other BGP message, and you can have a > Lamport logical clock over your iBGP domain. > > If it were an attribute though that would be bad for update packing because the timestamp would end up being unique for most prefixes.
BMP has timestamps though...we just need someone to implement it in quagga :) Daniel
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
