Market mass or open standards?

At Interop this month, we heard keynotes from two network vendors who are not only archrivals in a business sense but also in their approach to the market. Cisco represents market power, account control. Juniper represents open standards. Who will win, and will the market win with them?

According to Cisco CEO John Chambers, the network is a repository for intelligence, a place to which all kinds of application features will migrate. Cisco's Service Oriented Network Architecture (SONA), criticized for its seeming lack of service-oriented architecture features despite its name, is emerging as a kind of network feature reservoir where Cisco hopes to store traditional features, such as virtualization and load balancing, and future ones, such as collaboration and message mediation. Buyers would likely have to adopt SONA end to end, meaning a SONA network is a Cisco network.

Juniper CEO Scott Kriens sees the enterprise at the center of a "perfect storm" of pressure, and sees the concept of open standards and guaranteed interoperability among vendors as the key to relieving that pressure. Intelligence should migrate into any network regardless of vendor, and any intelligence that's suitable from the user's perspective has to be able to make the trip into network hosting through standards accepted by all.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

At Interop this month, we heard keynotes from two network vendors who are not only archrivals in a business sense but also in their approach to the market. Cisco represents market power, account control. Juniper represents open standards. Who will win, and will the market win with them?

According to Cisco CEO John Chambers, the network is a repository for intelligence, a place to which all kinds of application features will migrate. Cisco's Service Oriented Network Architecture (SONA), criticized for its seeming lack of service-oriented architecture features despite its name, is emerging as a kind of network feature reservoir where Cisco hopes to store traditional features, such as virtualization and load balancing, and future ones, such as collaboration and message mediation. Buyers would likely have to adopt SONA end to end, meaning a SONA network is a Cisco network.

Juniper CEO Scott Kriens sees the enterprise at the center of a "perfect storm" of pressure, and sees the concept of open standards and guaranteed interoperability among vendors as the key to relieving that pressure. Intelligence should migrate into any network regardless of vendor, and any intelligence that's suitable from the user's perspective has to be able to make the trip into network hosting through standards accepted by all.

At one level, this debate is predictable. The guy with market mass, account control, deep pockets, rising sales, glamour and glory will always be talking about solving problems end to end with proprietary gear and strategies. Those who lack one or more of these heady attributes will pledge allegiance to open standards. Nevertheless, there are some real issues here.

IT is moving to a more open and competitive framework than ever before. The explosion of powerful microprocessors based on the x86 architecture has reshaped the hardware markets, marginalizing proprietary servers and workstations. Silicon Graphics, a high-end workstation vendor, filed for Chapter 11 the week after Chambers and Kriens gave their keynotes. At the same time, open source has revolutionized software, starting with Linux at the operating systems level and moving up to databases, then on to application middleware. IT vendors don't like that but don't have much hope of stemming the tide.

If features migrate down into the network, they migrate out of the space where open source traditionally competes. Could it be that the last bastion of proprietary IT is inside the network? Or is it possible that the open source influence on software will be enough to force network providers to adopt the standards-based approach?

Traditional network standards such as TCP or Session Initiation Protocol won't cut it these days, as far as network openness is concerned. Application middleware is creating a new interface between software and the network, an interface that is less protocol-oriented and therefore less linked to traditional network standards. Whether we're talking standard approaches to communicating applications, such as Asynchronous JavaScript + XML, or proprietary tools, such as Microsoft's forthcoming Indigo communications model, protocols are becoming disconnected from software.