Lippis Report 150: What is the Motivation Behind The Unified Communications Interoperability Forum?
In mid May of this year HP, Juniper Networks, Microsoft, Logitech / LifeSize and Polycom established a forum to develop a set of interoperability test methodologies and certification programs along with specifications and guidelines that enable mixed vendor Unified Communications UC solutions to work with each other. In short, the UC Interoperability Forum or UCIF is trying to define what it means for multi-vendor UC implementations to interoperate. Since its establishment, membership has grown by thirteen vendors, but blaringly obvious is the omission of Cisco, Avaya, Mitel, ShoreTel and other major UC providers. This begs the question of motivation. Is the UCIF interested in interoperability or changing the market landscape to gain advantage on the established leaders? In this Lippis Report Research Note we explore this question.
Making Networks More Agile With Force10’s Open Automation
UC interoperability is a very big deal. In fact, back in early April of this year, Zeus Kerravala, SVP of the Yankee Group and I addressed this issue in a Lippis Report podcast titled What is Holding UC Back?. Our answer was lack of interoperability standards and the vendor community’s minimal interest of embracing the ones we have. The UC market has evolved in a peculiar way as it brings together traditional voice communication companies, data networking firms, computing corporations and software concerns. UC is now at the epicenter of video communications, social networking and mobile computing too. UC represents one of the largest cross sections of disparate markets second only to the Internet. It’s here, within this cross section, that UC gains its enormous value.
Siemens Changes UC Market with OpenScape UC Server 2010
UC offers to control real time communications and collaboration. Put another way, all real time business processes will be accessed and control by UC over time. Need to call a colleague? It’s via your UC client. Need to schedule a meeting? It’s via your UC calendar client. Need to video chat with a customer? It’s via your UC video client. Need to bring a group of people together for an emergency meeting? Yes, you guessed it! It is via your UC collaboration client. And common to all those UC clients is presence enabled directory to you, so you can find someone and know if they are available, a communications management system that sets up and tears down connections over intranet, internet and mobile nets. To make UC work ubiquitously, like the public telephone network or the Internet, the vendor community needs a forum or place where it can work out interoperability standards. In addition, for this next evolution in human communications to live up to its promise, it needs motivated vendors to allow their equipment to work together.
What is Holding UC Back?
Yes, UC does have key interoperability standards such as SIP or Session Initiation Protocol that offer both end-point and communications manager interoperability, but many vendors add proprietary extensions to SIP reducing its value in multi-vendor networks. So the UCIF is to be applauded for taking the first step in creating an organization among the vendor community to usher in an era of interoperable UC. But the problem with UCIF is which companies established its formation. Clearly suppliers are businesses looking for sustainable competitive advantage that comes with large market share and innovative, albeit proprietary technologies. It’s no surprise then that when UCIF is established by firms with limited UC market share one’s mind jumps to the obvious assumption that the founding members of the UCIF are perhaps more interested in market share re-distribution than interoperability.
IPv6 First Hop Security: Protecting Your IPv6 Access Network
I’ve observed many industry forums and consortiums in the past that used interoperability as a convenient cause to hide a group’s true intentions. For example, Bay Networks, 3Com and IBM established the Network Interoperability Alliance or NIA in May of 1996 to foster interoperability between Local Area Network (LAN) switch vendors. NIA had limited success in competing with Cisco’s increasing market share gains of the enterprise router and switch market.
A Rational Storage Strategy: To Unify or Not to Unify
UCIF feels a lot like NIA to me. The shear fact that it’s mission statement, board and legal structure was done without any of the UC market leaders input and participation is unfortunate, as it has alienated them. It’s also unfortunate that Polycom and LifeSize are founding UCIF partners, but Cisco/Tandberg is not involved as this has a hint of Polycom/LifeSize fear of Cisco breaking away with the Telepresence market; UCIF seems like a way of mitigating this threat. The timing is very close with Cisco closing the Tandberg acquisition in April and UCIF being launched in May.
SIP-O-Nomics Saving Money and Simplifying Architecture with the Session Initiation Protocol
If UCIF is not able to entice and recruit Cisco, Avaya, Mitel, and ShoreTel et al in a meaningful and authoritative way, then its fate may very well be the same as NIA. What the industry does need is true interoperability standards so that a Cisco, Avaya, Microsoft, Siemens, HP et al UC implementations are able to work with each other in the same way that multi-vendor email systems work with each other. But without full industry participation, it seems that UCIF may be doomed and not able to deliver on its promise of interoperability. For UCIF to be meaningful it needs the UC market leaders full participation as well as Enterprise IT architects and planners plus service providers too, for without them, UCIF is NIA.