CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)
draft-ivov-xmpp-cusax-04
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2013-04-04
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group E. Ivov
Internet-Draft Jitsi
Intended status: Informational P. Saint-Andre
Expires: October 06, 2013 Cisco Systems, Inc.
E. Marocco
Telecom Italia
April 04, 2013
CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the
Extensible Messaging and Presence Protocol (XMPP)
draft-ivov-xmpp-cusax-04
Abstract
This document describes suggested practices for combined use of the
Session Initiation Protocol (SIP) and the Extensible Messaging and
Presence Protocol (XMPP). Such practices aim to provide a single
fully featured real-time communication service by using complementary
subsets of features from each of the protocols. Typically such
subsets would include telephony capabilities from SIP and instant
messaging and presence capabilities from XMPP. This specification
does not define any new protocols or syntax for either SIP or XMPP.
However, implementing it may require modifying or at least
reconfiguring existing client and server-side software. Also, it is
not the purpose of this document to make recommendations as to
whether or not such combined use should be preferred to the
mechanisms provided natively by each protocol (for example, SIP's
SIMPLE or XMPP's Jingle). It merely aims to provide guidance to
those who are interested in such a combined use.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 06, 2013.
Ivov, et al. Expires October 06, 2013 [Page 1]
Internet-Draft Combined Use of SIP and XMPP April 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Client Bootstrap . . . . . . . . . . . . . . . . . . . . . . 4
3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Multi-Party Interactions . . . . . . . . . . . . . . . . . . 8
5. Federation . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Informative References . . . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
Historically SIP [RFC3261] and XMPP [RFC6120] have often been
implemented and deployed with different purposes: from its very start
SIP's primary goal has been to provide a means of conducting
"Internet telephone calls". XMPP on the other hand, has, from its
Jabber days, been mostly used for instant messaging and presence
[RFC6121], as well as related services such as groupchat rooms
[XEP-0045].
For various reasons, these trends have continued through the years
even after each of the protocols had been equipped to provide the
features it was initially lacking:
o Today, in the context of the SIMPLE working group, the IETF has
defined a number of protocols and protocol extensions that not
Show full document text