IM Federation Is Still a Mess

執筆者
Michael Caton
Michael Caton
Published: Oct 7, 2005
Updated: Feb 2, 2021
2 minute read
eWeek のコンテンツおよび製品のおすすめは、編集上の独立性を保っています。パートナーへのリンクをクリックすると、当社が報酬を得る場合があります。 詳細を見る

During the past few weeks, I have been working with a few enterprise instant messaging platforms to test their interoperability in the context of federation, or connecting separate IM networks.

What a mess.

A couple of the products seemingly work well, but so much work needs to be done, and the framework just doesnt scale the way it needs to.

In the testing, I looked to connect Antepo OPN XT, IBM Lotus Sametime and Microsoft Live Communication Server 2005, as well as connect to public networks.

Per my Tech Analysis, the overhead for doing this can be high because of certificate management and administration of white lists for every network a company wants to connect with.

If you have a couple of key partners, thats not bad, but some organizations deal with a range of partners and customers, and for these companies, the administrative overhead involved would be too high.

/zimages/2/28571.gifHackers step up attacks on IM networks.Click hereto read more.

Part of the problem right now is that the tools dont exist for creating a bulk white list. Administrators have to manually create and manage connections to each partner domain.

Bringing automation to the process and giving users some control over creating the white list, albeit with IT having final approval, would be welcome and valuable improvements.

Certificate management is another headache as well, but one that requires infrequent administration.

One of the most frustrating aspects of my testing was dealing with Microsofts LCS 2005 Enterprise Edition.

I still cannot fathom why the product is so poorly architected that it requires setting up three LCS servers to connect to an external domain. LCS needs a core IM server, a director server and the proxy server. For the IM servers from Antepo, Jabber and IBM, on the other hand, a core IM server and gateway server suffice.

Companies that want to give remote users access to IM without a VPN connection have to set up LCS in the same way. Theoretically, the ability to allow remote access without VPN would be a significant cost savings, if Microsoft hadnt made running another server and using certificates for authentication a requirement.

Advertisement

I made one very pleasant discovery while doing the testing: Finally, a company understands that users may want a high degree of control over their presence information. Antepos OPN Client allowed me to more finely tune who could see that I was online.

/zimages/2/28571.gifRead another opinionhereabout the challenges of “presence.”

Thats a requirement for federation to succeed. The nature of my job entails a high degree of external communications, but Im loath to make my online availability known because of the prospect of more IM than I can handle. The ability to more tightly manage presence information by individuals and groups makes it much easier to be get person-to-person work done on a project basis.

eWEEK Labs Technical Analyst Michael Caton can be reached at michael_caton@ziffdavis.com.

/zimages/2/28571.gifCheck out eWEEK.coms for more on IM and other collaboration technologies.

Michael Caton

Michael Caton

Content Writer
eWeek Logo

eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site's focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

TechnologyAdvice が所有・運営しています。 © 2026 TechnologyAdvice. 無断転載を禁じます

広告主に関する開示:このサイトに掲載されている製品の一部は、TechnologyAdvice が報酬を受け取っている企業のものです。この報酬は、製品がこのサイトのどこにどのように表示されるか(表示される順序など)に影響する場合があります。TechnologyAdvice は、市場で入手可能なすべての企業やすべての種類の製品を掲載しているわけではありません。