[dispatch] Charter Proposal: SIP-XMPP Mapping

Peter Saint-Andre <stpeter@stpeter.im> Fri, 15 February 2013 22:37 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E44C221F85C6 for <dispatch@ietfa.amsl.com>; Fri, 15 Feb 2013 14:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level:
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yq7itOfW3wPX for <dispatch@ietfa.amsl.com>; Fri, 15 Feb 2013 14:37:32 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1094C21F85BC for <dispatch@ietf.org>; Fri, 15 Feb 2013 14:37:32 -0800 (PST)
Received: from [192.168.1.7] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1A03A406A8 for <dispatch@ietf.org>; Fri, 15 Feb 2013 15:44:44 -0700 (MST)
Message-ID: <511EB8B0.8090104@stpeter.im>
Date: Fri, 15 Feb 2013 15:37:36 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: DISPATCH <dispatch@ietf.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [dispatch] Charter Proposal: SIP-XMPP Mapping
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 22:37:33 -0000

Charter Proposal: SIP-XMPP Mapping
DISPATCH WG
IETF 86, Orlando

Problem Statement

The IETF has defined two signalling technologies that can be used
for multimedia session negotiation, instant messaging, presence,
file transfer, capabilities discovery, notifications, and other types of
real-time functionality:

o  The Session Initiation Protocol (SIP), along with various SIP
   extensions developed within the SIP for Instant Messaging and
   Presence Leveraging Extensions (SIMPLE) Working Group.

o  The Extensible Messaging and Presence Protocol (XMPP), along
   with various XMPP extensions developed by the IETF as well as by
   the XMPP Standards Foundation.

SIP has been focused primarily on media session negotiation (e.g. audio
and video), whereas XMPP has been focused primarily on messaging and
presence.  As a result, the technologies are mostly complementary.
However, there is also some overlap between SIP and XMPP, since there
are SIP extensions for messaging, presence, groupchat, file transfer
(etc.) and there are XMPP extensions for multimedia session negotiation.
This overlap has practical implications, since some deployed services
use SIP for both media and (broadly) messaging, whereas other deployed
services use XMPP for both messaging and media.  When such services wish
to exchange information, they often need to translate their native
protocol (either SIP or XMPP) to the other protocol (either XMPP or
SIP).

Implementers needing to perform such protocol mappings have often worked
out their own heuristics for doing so.  Unfortunately, these heuristics
are not always consistent, which can lead to interoperability problems.

Objectives

To make it easier for implementers to enable interworking between
SIP-based systems and XMPP-based systems, several Internet-Drafts have
defined guidelines for protocol mapping between SIP and XMPP, starting
with draft-saintandre-xmpp-simple-00 in early 2004.  The current
documents are:

draft-saintandre-sip-xmpp-core
draft-saintandre-sip-xmpp-presence
draft-saintandre-sip-xmpp-im
draft-saintandre-sip-xmpp-chat
draft-saintandre-sip-xmpp-groupchat

These documents are quite stable and the authors have received feedback
from a number of implementers over the years.  However, implementers do
not always know about these documents because they are Internet-Drafts
and sometimes have expired.  Thus it would be helpful to polish them off
and publish them as RFCs (and perhaps other documents in the same series,
covering topics like media signalling, capabilities discovery, and file
transfer).

Deliverables

1. Address mapping and error handling
2. Presence mapping
3. Mapping for single instant messages
4. Mapping for one-to-one text chat sessions
5. Mapping for multi-user text chat sessions

Any additional work would require a recharter.

Milestones

To be determined.

###