question about bgp incremental updates


I can think of two reasons for such behavior:

- one of the attributes of these routes changed suddenly, so they have been reannounced by your peer,
- you sent a 'route refresh' request to this peer, asking him to reannounce all his table.

Other than that, I don't see why a peer would resend lots of already-announced prefixes..