• 03/01/2006
    11:57 AM
  • Rating: 
    0 votes
    Vote up!
    Vote down!

Why I Hate Open Source Routing

Why is it that perfectly sane, intelligent, and bright journalists get boinked when it comes to open source technology? Mention Firefox and they interpret 10 percent marketshare as market dominance. They sing the praises of Asterisk not stopping to think...

Vyetta/XORP though won't be able to work in the language of routing that's spoken in today's enterprises, Cisco's IGRP. Without supporting the Cisco routing protocol, replacing Cisco isn't going to be happen any time soon. That's a big difference from LINUX, Firefox or other wunderkids of open source, where playing in the existing environment doesn't present nearly the same kinds of problems. And don't expect to argue that you'll just replace a Cisco core router with a XORP-equivalent. Besides IT's investment in the existing hardware, XORP's performance remains slower than Cisco routers because the forwarding plane is implemented in software. Routing code also has little do with the needs of the remote office, which today is looking for an office-in-a-box -- a router that provides all connectivity requirements. Cisco's Integrated Service Routers (ISRs) is a perfect example. It can be equipped with an IP PBX, firewall, a switch, wireless access point and an IDS/IPS. So far Cisco has shipped 750,000 ISRs.

Cisco isn't alone in that regard. Whether it's Juniper's J-Series or Adtran's NetVanta line, the message is one-stop delivery of the critical network applications needed in the branch office is what today's routing is all about.

The small business is another matter and I think here is where Vyatta/XORP's impact could really be felt. All sorts of small office, multifunctional gear will become more popular today because vendors can focus on the applications that really matter and less on the routing code. Alec Saunders makes this point when recounting a dinner conversation he had with a CTO of a very large PBX manufacturer. The CTO, blogs Alec, defined call control as a commodity and if he can outsource it to an open source project, it lets him assign resources to the far more lucrative applications market.

The other impact could well be in commoditizing Session Border Controller (SBC), notes Aswath Rao in his blog. He should know. He suggested the Inter Connect Function in the TIPHON Architecture that became known as the SBC. Rao writes that "in its core SBC is a 'twice NAT'. So it is very likely the open source router software used by Vyatta could be used to build SBC as well." Open source routing has its role to play in this market, but don't expect that to be in the enterprise any time soon.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.

Log in or Register to post comments