IETF Logo Mail Archive

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

Adrian Georgescu <ag@ag-projects.com> Fri, 02 August 2013 10:26 UTC

Return-Path: <ag@ag-projects.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 709B521E8386 for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level:
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, 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 WiXFpIl9l-q9 for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:26:41 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id A080221E8376 for <stox@ietf.org>; Fri, 2 Aug 2013 03:26:25 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 5785FB35DD; Fri, 2 Aug 2013 12:26:24 +0200 (CEST)
Received: from ag-retina15.fritz.box (xs4all.dns-hosting.info [82.161.39.123]) by mail.sipthor.net (Postfix) with ESMTPSA id 2BF9DB017A; Fri, 2 Aug 2013 12:26:11 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3FF650B1-CE03-451A-BD95-F61B9CEB4B22"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Adrian Georgescu <ag@ag-projects.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se>
Date: Fri, 02 Aug 2013 12:26:10 +0200
Message-Id: <8C703C0F-181C-4E36-8A59-727B45C0A1B5@ag-projects.com>
References: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
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: Fri, 02 Aug 2013 10:26:46 -0000

Hi Christer,

I would suggest that best practice is for the SIP traffic to be routed to the SIP Proxy/Registrar/Presence Agent of the given domain behind the gateway. That element has more proper capabilities for handling forking or any other SIP features. 

Otherwise you will move all SIP functionality into the XMPP gateway and must document that whole SIP universe as running inside that gateway, which makes little sense.

Regards, 
Adrian

On Aug 2, 2013, at 12:16 PM, Christer Holmberg <christer.holmberg@ericsson.com> 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.
>  
> Regards,
>  
> Christer
>  
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox

v2.23.0 | Report a Bug | By Email