Re: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking

Christer Holmberg <christer.holmberg@ericsson.com> Sun, 04 August 2013 16:58 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEAA21F9C0A for <stox@ietfa.amsl.com>; Sun, 4 Aug 2013 09:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.445
X-Spam-Level:
X-Spam-Status: No, score=-3.445 tagged_above=-999 required=5 tests=[AWL=-2.016, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_MLH_Stock1=0.87]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2XhaY1yOBMI for <stox@ietfa.amsl.com>; Sun, 4 Aug 2013 09:57:59 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id AA90921F830F for <stox@ietf.org>; Sun, 4 Aug 2013 09:57:58 -0700 (PDT)
X-AuditID: c1b4fb38-b7f456d000002e83-ea-51fe88143a7f
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 95.9E.11907.4188EF15; Sun, 4 Aug 2013 18:57:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.02.0328.009; Sun, 4 Aug 2013 18:57:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
Thread-Topic: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking
Thread-Index: Ac6PaRwphn/mcGjdScuZ2ITH5v377///5ViA//xQumA=
Date: Sun, 4 Aug 2013 16:57:56 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C41C18F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se> <ABAD55BF-8EDA-45CD-A665-9288D564F67A@ag-projects.com>
In-Reply-To: <ABAD55BF-8EDA-45CD-A665-9288D564F67A@ag-projects.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvra5Ix79Ag9nHbSyW7lvDYvF/RxOr A5NHS/8kFo8lS34yBTBFcdmkpOZklqUW6dslcGUs3pdTcJmtYsGfi6wNjDNYuxg5OSQETCRO XWlihrDFJC7cW8/WxcjFISRwlFHi7IcHYAkhgcWMQBnOLkYODjYBC4nuf9ogpoiAi0T/kgAQ k1lAWeLQFFmQYmEBT4nNuz6wg9giAl4S2249hLKtJN5+u8sCYrMIqEjcP7OBDcTmFfCV2NDX xQaxqI1Romt3LIjNKeAsMeHgF7B6RqDLvp9awwRiMwuIS3w4eB3qYgGJJXvOQ9miEi8f/4P6 Sknix4ZLLBD1ehI3pk5hg7C1JZYtfM0MsVdQ4uTMJywTGMVmIRk7C0nLLCQts5C0LGBkWcXI UZxanJSbbmSwiREYHQe3/LbYwXj5r80hRmkOFiVx3i16ZwKFBNITS1KzU1MLUovii0pzUosP MTJxcEo1MIY8mvypSMJ/m0GrmVrlg3X3ikQWvO95G8/C2r5z1rHZUz2dpi57vk/qafrue6m/ NnwPC/M4k5aR/M1FbpO9IoNCxZoDZdwhK/lm6DGfED3q4NXw+tvdsBPVH2NOb3G+ln6lNevk 2iSdiftnH7n0elfPMiOFqTyPvRgtym8LrHklpeJ8+9H8Jf1KLMUZiYZazEXFiQDf0DzuXAIA AA==
Cc: "stox@ietf.org" <stox@ietf.org>
Subject: Re: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 16:58:05 -0000

Hi,
 
>> As I indicated at the STOX session (and was later repeated by Jonathan Lennox), the draft need to have a story on SIP forking, e.g. if what happens if the INVITE sent from the interworking node gets forked, and multiple early dialogs are created.
>
> I'll propose text but in general terms, since forking doesn't exist in XMPP, the gateway will need to make sure only one reply is relayed to the XMPP side. Also, there dis very little text about early media in XEP-166, I'll look more into that.

Unfortunately my XMPP knowledge is more or less zero, so at this point I can't really suggest any solution. However, if early media does not exist in XMPP, and the gateway only needs to care about (at least from a media perspective) the 200 OK, there probably is no problem :)

Regards,

Christer