Presence and IntComm WG

[Candace Holman <>]

The article talks about partnerships and interoperability - as far as 
I'm concerned it's new territory for MS and a step in the right 
direction.  Hopefully this (March 06) article is reporting news after 
the "balkanization" Rodger speaks of.  At worst, at least in this news 
there's greater industry support for SIMPLE, when the recent debate 
within this working group has been increasingly anti-SIMPLE due to lack 
of industry support and deployment.

http://www.networkworld.com/news/2006/030606-microsoft-telecoms-voip.html?page=2 


Candace


Will, Rodger (R.) wrote:
> In addition, MS has taken great steps to "balkanize" SIP/SIMPLE by 
> requiring additional "Access Proxies" to communicate with other 
> SIP/SIMPLE implementations.  The only permitted integraton 
> opportunities requires .NET API level programming.
>
> What MS is doing here is trying to com off as - Hey we are great 
> folks...  We are open!  Look SIP/SIMPLE inside! 
>
> However, what they have really created is another Office Suite-centric 
> Closed Enterprise IM Implementation.
>
>
> -----Original Message-----
> From:   Peter Parnes 
> [mailto:]
> Sent:   Sat 3/25/2006 1:55 PM
> To:     
>
> Cc:     
>
> Subject:        Re: [wg-pic] Microsoft chooses SIP/SIMPLE
>
> Evening,
>
> MS has been on the SIP bandwagon for several years (since about 2001)
> with both its RTC library (standard part of Windows XP) and MS Messenger
> that has been using SIP/SIMPLE since version 4.7.x. Earlier versions of
> MS Messenger even allowed you to use your own SIP server (something they
> later on removed).
>
> MS Messenger = Windows Messenger
> not to be confused with MSN Messenger that it something else.
> MSN Messenger is currently changing name to Windows Live Messenger as of
> version 8 (currently in beta).
>
> Have a nice weekend.
>
> -Peter Parnes, PhD
> Associate Professor
> Media Technology
> Luleå University of Technology
>
> Chief Scientist Marratech