Maybe the BGP implemntations should be re-written to be more effective. BGP in Cisco must have parts that are quite old and can be done more effectively today. Just take a look at OpenBGPD which is an example that a BGP implementation can save more memory.
Latest LAN/WAN headlines from Network World:
Porn producer sentenced to prison for online distribution
EBay buys payment firm for almost $1B, lays off over 1,000
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
RE: 'Radical rethinking' of Internet routing under way
I believe the whole point of the article is to find a successor to BGP. BGP has been around a while now and has scaled to this point. However moving forward I don't believe BGP is the way to go. I don't think BGP can scale to the degree the IRTF needs for developing countries. With most large organizations doing multi-homing with different service providers scalability is not the only issue. There is currently no way to load balance across different service providers without using an additional appliance. If the IRTF could develop a protocol that will scale, load balance, and converge quickly when a network event occurs they might find the "silver bullet" they are looking for.
BGP Appliance?
BGP was never intended to truly load balance, not evenly, or in a fine-grained manner anyhow. Router implementations work fine for finding a viable path in multi-homed organizations, even with multiple upstreams, and peering relationships.