IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 02 August 2013 10:30 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 D8E0D21E82C7 for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.452
X-Spam-Level:
X-Spam-Status: No, score=-5.452 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 nHsq9lU0WBfB for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:30:54 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 746A021E833F for <stox@ietf.org>; Fri, 2 Aug 2013 03:30:22 -0700 (PDT)
X-AuditID: c1b4fb25-b7f826d000001766-da-51fb8a3db078
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id A1.BA.05990.D3A8BF15; Fri, 2 Aug 2013 12:30:21 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.02.0328.009; Fri, 2 Aug 2013 12:30:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adrian Georgescu <ag@ag-projects.com>
Thread-Topic: [Stox] Media Sessions (draft-ietf-stox-media-01) and forking
Thread-Index: Ac6PaRwphn/mcGjdScuZ2ITH5v377///4akA///dspA=
Date: Fri, 02 Aug 2013 10:30:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C418FAC@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C418E51@ESESSMB209.ericsson.se> <8C703C0F-181C-4E36-8A59-727B45C0A1B5@ag-projects.com>
In-Reply-To: <8C703C0F-181C-4E36-8A59-727B45C0A1B5@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.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C418FACESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvra5t1+9Ag9e3FC223su3+L+jidWB yaOlfxKLx5IlP5kCmKK4bFJSczLLUov07RK4Mi5v7GcuOONZ0X7jHksD43SnLkZODgkBE4mb 696xQthiEhfurWfrYuTiEBI4zCix6tQxVghnMaPE587dTF2MHBxsAhYS3f+0QRpEBDQlWhZN ZgEJMwsoSxyaIgsSFhbwlNi86wM7RImXxLZbD6FsK4neI1vZQGwWARWJg083gNm8Ar4Sq26e h9rbxigxe/UmZpAEp4CzxNyVh8BsRqDjvp9awwRiMwuIS3w4eJ0Z4mgBiSV7zkPZohIvH/+D ekZJonHJE1aI2/Il7q93hNglKHFy5hOWCYyis5BMmoVQNQtJFUSJjsSC3Z/YIGxtiWULXzPD 2GcOPGZCFl/AyL6KkT03MTMnvdxoEyMwmg5u+a26g/HOOZFDjNIcLErivJv1zgQKCaQnlqRm p6YWpBbFF5XmpBYfYmTi4JRqYOR5ZBVSK2/z+ZN746u+Bw9fSh9YW29vNpHXe6bexiRBJdFu 02Wtt35y2HamWhy0rWeVZVozbZJm1O7PzoXn9wiWpv/xv2Ns758v+CzztpT4jtY387RTkr+e WdQRJjUvLETyEjfjzMSc1xGH1gYrHRLa4i+0UivKYjePgaMwL9uM5yXBPyrzlViKMxINtZiL ihMBnpR89HQCAAA=
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:31:00 -0000

Hi Adrian,

>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.

Ok, but how are you going to ensure that such element exists?

Regards,

Christer





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<mailto: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<mailto:stox@ietf.org>
https://www.ietf.org/mailman/listinfo/stox

v2.23.0 | Report a Bug | By Email