Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs

["Sriram, Kotikalapudi" <[e-mail]>]

>
> ooc, in regards to the above: is there any detailed analysis of how much extra overhead we can expect from these beacons if BGPSec were deployed universally today?  Specifically, the comment above, "an AS could cause the same impact on the routing system by changing other route parameters at the same frequency" seems to miss the point I think I see in the objection: what if _every_ AS must do this all the time (not just a rogue, or select few).  How much extra overhead would ensue if (say) someone took the current set of all ASes and prefixes and simulated the extra update traffic needed in (say) a day?  Maybe if we saw some numbers that told us how many additional updates and how much additional bandwidth this approach would require in a routing system like today's we could understand another aspect of much of a shift we are talking about?
>

Eric,

According to 
http://bgpupdates.potaroo.net/instability/bgpupd.html 
the current global BGP system produces
Average Prefixes per BGP Update: 	2.24
Average BGP Update Messages per second: 	1.13 	
Average Prefix Updates per second: 	2.53
>From this we can compute:
Average Prefix Updates per day = 	218696

Now if we consider a BGPSEC island of 100,000 participating prefixes
(multiple ISPs form a BGPSEC island and there is BGPSEC between
them and also in each ISP's entire customer cone):
With 24 hour beaconing interval, we would have:
Prefix Updates per Day = 100,000 (seen at each BGPSEC router)
BGPSEC Update Size = 420B (for ECDSA-256)
Average Bandwidth Required = 3.89 kbps (averaged over a day) 

Does this answer what you were asking for?

Sriram 
 


_______________________________________________