Browse Prior Art Database

CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) (RFC7081) Disclosure Number: IPCOM000233175D
Original Publication Date: 2013-Nov-01
Included in the Prior Art Database: 2013-Nov-28
Document File: 38 page(s) / 47K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Ivov: AUTHOR [+2]


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". On the other hand, XMPP has, from its Jabber days, been mostly used for instant messaging, presence [RFC6121], and related services such as groupchat rooms [XEP-0045].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                           E. Ivov Request for Comments: 7081                                         Jitsi Category: Informational                                   P. Saint-Andre ISSN: 2070-1721                                      Cisco Systems, Inc.                                                               E. Marocco                                                           Telecom Italia                                                            November 2013

       CUSAX: Combined Use of the Session Initiation Protocol (SIP)        and the Extensible Messaging and Presence Protocol (XMPP)


   This document suggests some strategies for the combined use of the    Session Initiation Protocol (SIP) and the Extensible Messaging and    Presence Protocol (XMPP) both in user-oriented clients and in    deployed servers.  Such strategies, which mainly consist of    configuration changes and minimal software modifications to existing    clients and servers, aim to provide a single, full-featured, real-    time communication service by using complementary subsets of features    from SIP and from XMPP.  Typically, such subsets consist of telephony    capabilities from SIP and instant messaging and presence capabilities    from XMPP.  This document does not define any new protocols or syntax    for either SIP or XMPP and, by intent, does not attempt to    standardize "best current practices".  Instead, it merely aims to    provide practical guidance to those who are interested in the    combined use of SIP and XMPP for real-time communication.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Ivov, et al.                  Informational                     [Page 1]
 RFC 7081              Combined Use of SIP and XMPP         November 2013

 Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as t...