CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)
draft-ivov-xmpp-cusax-07

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-09-12 (latest revision 2013-08-26)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd Mary Barnes
Shepherd write-up Show (last changed 2013-06-18)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES.
Responsible AD Gonzalo Camarillo
Send notices to emcho@jitsi.org, enrico.marocco@telecomitalia.it, psaintan@cisco.com, draft-ivov-xmpp-cusax@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                            E. Ivov
Internet-Draft                                                     Jitsi
Intended status: Informational                            P. Saint-Andre
Expires: February 28, 2014                           Cisco Systems, Inc.
                                                              E. Marocco
                                                          Telecom Italia
                                                         August 27, 2013

  CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the
           Extensible Messaging and Presence Protocol (XMPP)
                        draft-ivov-xmpp-cusax-07

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 the practices outlined in this document 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 February 28, 2014.

Ivov, et al.            Expires February 28, 2014               [Page 1]
Internet-Draft        Combined Use of SIP and XMPP           August 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  . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Server-Side Setup . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Service Management  . . . . . . . . . . . . . . . . . . .   8
     3.3.  Client-Side Discovery and Usability . . . . . . . . . . .   8
     3.4.  Indicating a Relation Between SIP and XMPP Accounts . . .   9
     3.5.  Matching Incoming SIP Calls to XMPP JIDs  . . . . . . . .  10
   4.  Multi-Party Interactions  . . . . . . . . . . . . . . . . . .  11
   5.  Federation  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Summary of Suggested Practices  . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  15
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

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
Show full document text