Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging
RFC 7572

Document Type RFC - Proposed Standard (June 2015; No errata)
Last updated 2015-10-14
Replaces draft-saintandre-sip-xmpp-im
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yana Stamcheva
Shepherd write-up Show (last changed 2015-01-26)
IESG IESG state RFC 7572 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                    P. Saint-Andre
Request for Comments: 7572                                          &yet
Category: Standards Track                                       A. Houri
ISSN: 2070-1721                                                      IBM
                                                           J. Hildebrand
                                                     Cisco Systems, Inc.
                                                               June 2015

   Interworking between the Session Initiation Protocol (SIP) and the
  Extensible Messaging and Presence Protocol (XMPP): Instant Messaging

Abstract

   This document defines a bidirectional protocol mapping for the
   exchange of single instant messages between the Session Initiation
   Protocol (SIP) and the Extensible Messaging and Presence Protocol
   (XMPP).

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on
   Internet Standards is available in 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
   http://www.rfc-editor.org/info/rfc7572.

Copyright Notice

   Copyright (c) 2015 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.

Saint-Andre, et al.          Standards Track                    [Page 1]
RFC 7572                SIP-XMPP Interworking: IM              June 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Intended Audience . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  XMPP to SIP . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  SIP to XMPP . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Message Size  . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Content Types . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Internationalization Considerations . . . . . . . . . . . . .   9
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   In order to help ensure interworking between instant messaging (IM)
   systems that conform to the instant messaging / presence requirements
   [RFC2779], it is important to clearly define protocol mappings
   between such systems.  Within the IETF, work has proceeded on two
   instant messaging technologies:

   o  Various extensions to the Session Initiation Protocol ([RFC3261])
      for instant messaging, in particular the MESSAGE method extension
      [RFC3428]; collectively the capabilities of SIP with these
      extensions are commonly called SIP for Instant Messaging and
      Presence Leveraging Extensions (SIMPLE).

   o  The Extensible Messaging and Presence Protocol (XMPP), which
      consists of a formalization of the core XML streaming protocols
      developed originally by the Jabber open-source community; the
      relevant specifications are [RFC6120] for the XML streaming layer
      and [RFC6121] for basic presence and instant messaging extensions.

   One approach to helping ensure interworking between these protocols
   is to map each protocol to the abstract semantics described in
   [RFC3860]; that is the approach taken by [SIMPLE-CPIM] and [RFC3922].
   In contrast, the approach taken in this document is to directly map
   semantics from one protocol to another (i.e., from SIP / SIMPLE to
   XMPP and vice versa), since that is how existing systems solve the
   interworking problem.

   Both XMPP systems and IM-capable SIP systems enable entities to
Show full document text