Re: [dispatch] Charter Proposal: SIP-XMPP Mapping
Michael Lundberg <michaellundberg.ietf@gmail.com> Wed, 20 February 2013 20:55 UTC
Return-Path: <michaellundberg.ietf@gmail.com>
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 C7F2021F865D for <dispatch@ietfa.amsl.com>; Wed, 20 Feb 2013 12:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 jLj8T1r0pxct for <dispatch@ietfa.amsl.com>; Wed, 20 Feb 2013 12:55:25 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 243E521F85F5 for <dispatch@ietf.org>; Wed, 20 Feb 2013 12:55:23 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hi8so6784454wib.1 for <dispatch@ietf.org>; Wed, 20 Feb 2013 12:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=it4X2eI++maSSt29uV3vUCMpGC/qNUqEb5AgAe3Rfws=; b=AbmFK+GOcP82TfOiV9Pus+5oFtnHfp3do9McyhMeO6rjnsWolYrtgezT4e0PQSaDr/ LplNuzf15dsQf++on8Ny0HktjNAkRraDddPv81Dse6qxNOEzjg1VD1zAeiVbHUzxespk c4/V2c28jF/xXrPWgn4QSvcBlYODz9Q4jAv7N503NsbpsMcuUQCHGE1Vrm7BNsj6VXIp +XTSkmnNWmDzBmuEnMpA6B2+J9pUv05SfoWsg8rGihD/sxffmmW96FMvMZhqG/5JXZ0r /E1HZd1+tuYEN/qVMTgaJ3dZBmnoMjcBEdZVuOOkCRYp1dUbb5dhdtrPDhH0omu6UpnY 1dZA==
MIME-Version: 1.0
X-Received: by 10.180.104.10 with SMTP id ga10mr35483119wib.23.1361393723255; Wed, 20 Feb 2013 12:55:23 -0800 (PST)
Received: by 10.216.231.217 with HTTP; Wed, 20 Feb 2013 12:55:23 -0800 (PST)
In-Reply-To: <51253544.3020901@ericsson.com>
References: <511EB8B0.8090104@stpeter.im> <51253544.3020901@ericsson.com>
Date: Wed, 20 Feb 2013 15:55:23 -0500
Message-ID: <CANVDpGFPfgeo5_zu0S1cf1foHMwax0MohdY-MfaVjySC7634LQ@mail.gmail.com>
From: Michael Lundberg <michaellundberg.ietf@gmail.com>
To: dispatch@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [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: Wed, 20 Feb 2013 20:55:26 -0000
I strongly support this proposal! Michael On Wed, Feb 20, 2013 at 3:42 PM, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote: > I do support this proposal > > > /Sal > > On 2/16/13 12:37 AM, Peter Saint-Andre wrote: >> >> 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. >> >> ### >> >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch > > > > -- > Salvatore Loreto, PhD > www.sloreto.com > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch
- [dispatch] Charter Proposal: SIP-XMPP Mapping Peter Saint-Andre
- Re: [dispatch] [External] Charter Proposal: SIP-X… Christou, Christos [USA]
- Re: [dispatch] [External] Charter Proposal: SIP-X… Ben Campbell
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Simon Pietro Romano
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Lorenzo Miniero
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Salvatore Loreto
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Emil Ivov
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Michael Lundberg
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Saúl Ibarra Corretgé
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Ross, Christopher [USA]
- Re: [dispatch] Charter Proposal: SIP-XMPP Mapping Peter Saint-Andre