Re: Should SIMPLE be rechartered, replaced, closed, or what?

Avshalom:

Yes, this may be another approach to use XMMP IM/Chat as another data
application as a part of SIP call (as SIMPLE IM/Chat does).

Then the question comes is this: Whether will XMPP have all the hooks for
SIP as SIMPLE does? If not, is it worthwhile to do so?

One of the key weaknesses of XMPP is the integration of XMPP with audio
and/or video. SIP is well established for integration of data applications
like IM/Chat (e.g. SIMPLE) as another applications with audio and/or video,
but XMPP is not.

At the end of the day, it appears that XMPP and SIMPLE/SIP are two competing
protocols. So, it may be such that XMPP will be used as the stand-alone data
applications for IM/Chat while SIMPLE/SIP is the one that will be used for
integration with audio/video using SIP.

So, there will be two niece markets evolving side-by-side. Of course,
SIMPLE/SIP as a stand-alone IM/Chat application will also be competing with
XMPP, but XMPP has much more market share in this segment.

BR/Radhika

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Avshalom Houri
Sent: Thursday, October 18, 2012 7:51 AM
To: Iñaki Baz Castillo
Cc: Mary Barnes; Simple WG; Paul Kyzivat
Subject: Re: [Simple] Should SIMPLE be rechartered, replaced, closed, or
what?



A different effort may be considered which is what will make XMPP acceptable
as an extension to SIP based systems. 

This means not modifying SIMPLE but using XMPP as the presence/IM protocol
for SIP. 

Usage of SIP AOR was mentioned before as an example. 

thanks
avshalom

_______________________________________________
Simple mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/simple