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

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 06 August 2013 16:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 173D221F9F74 for <stox@ietfa.amsl.com>; Tue, 6 Aug 2013 09:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.106
X-Spam-Level:
X-Spam-Status: No, score=0.106 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, 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 Bf2I3tbhU+p2 for <stox@ietfa.amsl.com>; Tue, 6 Aug 2013 09:17:50 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC0721F9F62 for <stox@ietf.org>; Tue, 6 Aug 2013 09:17:50 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta15.westchester.pa.mail.comcast.net with comcast id 9Ph41m0041c6gX85FUHpun; Tue, 06 Aug 2013 16:17:49 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id 9UHp1m00Q3ZTu2S3jUHpk0; Tue, 06 Aug 2013 16:17:49 +0000
Message-ID: <520121AC.5030301@alum.mit.edu>
Date: Tue, 06 Aug 2013 18:17:48 +0200
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: stox@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se> <ABAD55BF-8EDA-45CD-A665-9288D564F67A@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C41C18F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C41C18F@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1375805869; bh=CAQBmwEQANKeyYwYyuTC4j625qNradKTv9rv+E7LmjM=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=LZGRQBbxtp2B23C0keYx7GPFR44Cmpr/L5fvwtWReqy8CHsnUKDVJQU+RweoGRnEe UnW3oeoZmv0If5JrZybo1D1TOhXL+LJmlSBNMMvlQk3HwAJf7Fu6AASR79p3FePkBu GzTqBjhVmU7H81BwU2a4DVYcckrXebWMlP06dzXOP2rCsrnQkqTk8h6HD0KeBzGt2I CcQ4yLwWH5tldy/IB3csvs90TfBQzLQ3ULZJHDyTDc9sWFgcpRYLl4kMrkALkcsRL1 awqTnVPgKbsrWwgQWrvKLOrzCHmQvLX21HwyxghJ/FjAurpoheKoPUQwqK6rWCju5S d7WFkK2nx38XA==
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: Tue, 06 Aug 2013 16:17:55 -0000

On 8/4/13 6:57 PM, Christer Holmberg wrote:
> 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.

Me too.

> 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 :)

I'm not sure what it means for early media to not exist in XMPP, or the 
implications of that on an XMPP-SIP GW. If the session is being 
originated from XMPP, and media addresses are provided before the call 
is answered, then early media is possible, even if it will be ignored.

The only way I can see to avoid this entirely is for the GW to initiate 
the initial INVITE without an offer, and *not* support 100rel, so that 
the answer won't be sent until the ACK.

	Thanks,
	Paul

> Regards,
>
> Christer
>
>
>
>
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox
>