Securing IM and P2P Applications for the Enterprise

Microsoft s MSN Messenger, much like Yahoo!Messenger, started out as a multi-protocol client with the capability to connect to AOL s AIM (AOLInstant Messenger) service. As a new instant messaging service, MSN did not have a large user baseand used interoperability with AIM as a way to co-opt that user community while building out itsown service. Microsoft released Windows Messenger in 1999, and included the ability to connect toAIM. Just as with Yahoo! Messenger, AIM quickly changed its protocol to prevent access from thisclient.
AOL changed its protocol, which was answered with Microsoft changing its client to regainconnectivity to the service. This is one of the reasons Microsoft released 21 versions of itsinstant messaging client in 1999 (see http://meetingbywire.com/OldVersions.htm for more details). Microsoft finallyabandoned its goal of interoperability at the end of 1999 with version 2.0 and concentrated onbuilding out its own service.
This client for Microsoft s service has had several names including Windows Messenger (theoriginal name and also the version shipped with the Windows operating system), .net Messenger, andMSN Messenger, the current version available for download. The latest client has changedconsiderably from its early versions, tying many of its features to the MSN portal, including theHotmail e-mail service and other MSN properties and services. Today s client bears littleresemblance to the previous versions, and contains new features such as Webcam communication, audiochat, photo and calendar sharing, and includes the ability to provide or request a remoteconnection with another workstation. Many of MSN Messenger s features tie back to MSN Webproperties, and include...