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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd 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                                E. Marocco
Expires: April 25, 2013                                   Telecom Italia
                                                          P. Saint-Andre
                                                     Cisco Systems, Inc.
                                                        October 22, 2012

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

Abstract

   This document describes current 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 like 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 April 25, 2013.

Ivov, et al.             Expires April 25, 2013                 [Page 1]
Internet-Draft        Combined Use of SIP and XMPP          October 2012

Copyright Notice

   Copyright (c) 2012 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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Client Bootstrap  . . . . . . . . . . . . . . . . . . . . . . . 4
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   4.  Federation  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   7.  Informative References  . . . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Ivov, et al.             Expires April 25, 2013                 [Page 2]
Internet-Draft        Combined Use of SIP and XMPP          October 2012

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