FYI...
/psa
- -------- Original Message --------
Subject: [dispatch] Charter proposal on combining SIP voice with XMPP
IM and presence
Date: Mon, 21 Sep 2009 14:28:43 +0200
From: Peter Saint-Andre
To:
Hello,
Below is the draft charter text for our proposal on combining SIP voice
with XMPP IM and presence.
Comments are very welcome!
Regards,
Simo
- -----------------
Combining SIP VoIP and XMPP IM/Presence
===================
Currently most standards-based Voice over IP (VoIP) deployments use the
Session Initiation Protocol (SIP). In addition to providing basic voice
service SIP has an extensive support for more advanced telephony
features including interworking with the traditional Public Switched
Telephone Network (PSTN). SIP is also gaining popularity in the field
of video communication. At the same time, the Extensible Messaging and
Presence Protocol (XMPP) is enjoying widespread usage in instant
messaging and presence services.
Both SIP and XMPP offer extensions for voice as well as IM and presence
(XMPP voice via the Jingle extension, and SIP IM/presence via SIMPLE
protocols). However, widespread deployment of these extensions has not
so far taken place. In order to speed up deployment of integrated VoIP
and IM systems, SIP based voice and XMPP based IM/Presence could be
combined in endpoints to offer a voice, IM and presence service without
any changes to existing SIP and XMPP service infrastrucure.
The objective of this Working Group is to develop solutions for
combining SIP based voice with XMPP based IM and Presence such that a
unified user experience can be offered to end user. Specifically,
solutions are needed on
- - addressing; end users should be able to initiate sessions to a user
identity in either SIP or XMPP domain. The corresponding user identity
in the other protocol domain needs to be learned automatically.
- - session correlation; endpoints need to be able to correlate voice
sessions with IM/Presence such that they can be presented to the end
user in a seamless fashion
- - presence; it should be possible to change the XMPP presence status
based on the user's activity in the SIP domain.
The goal is to rely on existing service infrastructre, and new
requirements should be imposed only to the endpoint.
Protocol interworking, that is, translation from one protocol to
another, is out of scope of this WG.
Milestones
Feb 2010 Problem statement and use cases submitted to IESG as Informational
Dec 2010 Specification on combining SIP based voice and XMPP based
IM/Presence in a seamless manner submitted to IESG as Proposed Standard.
- -----------------