Sorry to jump in here, but I think that there is a drifting into conjecture...
It would be best to stay within the realm of facts. > Great, so you don't disagree that beacons mostly cause no change. > That should cover the bulk of BGPSEC updates. > > That brings us a long way down from 2X. There is no empirical basis for 2X, either in the general case or the specific case. If I understand the "beacon" concept correctly, this is the re-announcement from the origin, based on the expiry time? Is this correct? Then the impact to the listener will be: The sum of (per-prefix frequency x number of in-RIBs that prefix is heard over) [i=1..N, N = number of prefixes]. If someone has a router with 10 copies of the full routing table, and the median rate is 1/day, then this will be approximately 10 x (routing table size) per day. The routing table in the DFZ is about what, 350-400k? That would be roughly 4M/day, or 50/sec. Even modest border routers, for multi-homed networks (two upstreams and significant local peering), that could easily be 1M+/day or 12+/sec. On top of everything else generated by churn, which in the case of a leaf router is 2-3/sec. The basic principal is, unlike churn, where the peak amplitude is an issue, this is pervasive, affecting every received prefix over every link on which it is received, even when routing is stable. Brian _______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
