Re: [sipcore] Bypassing out-of-service intermediate Proxy

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 29 November 2010 06:45 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FC343A6BF9 for <sipcore@core3.amsl.com>; Sun, 28 Nov 2010 22:45:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level:
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhvARSgZmse2 for <sipcore@core3.amsl.com>; Sun, 28 Nov 2010 22:45:08 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 45BA03A6BFC for <sipcore@ietf.org>; Sun, 28 Nov 2010 22:45:07 -0800 (PST)
X-AuditID: c1b4fb3d-b7b8cae0000016b1-95-4cf34c37b1a8
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 17.4E.05809.73C43FC4; Mon, 29 Nov 2010 07:46:15 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Mon, 29 Nov 2010 07:46:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Mon, 29 Nov 2010 07:42:54 +0100
Thread-Topic: [sipcore] Bypassing out-of-service intermediate Proxy
Thread-Index: AcuPcQ2LO/H5UYixQPOKlQtg+raSVgAH5kno
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058502C7189A@ESESSCMS0356.eemea.ericsson.se>
References: <9ECCF01B52E7AB408A7EB8535264214101CD7EE2@ftrdmel0.rd.francetelecom.fr><4C7FDBEE.6080305@nostrum.com>, <9ECCF01B52E7AB408A7EB85352642141020FD443@ftrdmel0.rd.francetelecom.fr> <CD5674C3CD99574EBA7432465FC13C1B22022889B6@DC-US1MBEX4.global.avaya.com><9ECCF01B52E7AB408A7EB8535264214102155080@ftrdmel0.rd.francetelecom.fr> <4CD16A52.7090006@cisco.com> <9ECCF01B52E7AB408A7EB853526421410221B4E3@ftrdmel0.rd.francetelecom.fr> <4CD53DFC.8020401@cisco.com> <9ECCF01B52E7AB408A7EB85352642141022A9552@ftrdmel0.rd.francetelecom.fr>, <4CE476E2.70801@cisco.com> <7F2072F1E0DE894DA4B517B93C6A058502C71893@ESESSCMS0356.eemea.ericsson.se>, <4CF31667.60601@cisco.com>
In-Reply-To: <4CF31667.60601@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "sipcore@ietf.org" <sipcore@ietf.org>, "youssef.chadli@orange-ftgroup.com" <youssef.chadli@orange-ftgroup.com>
Subject: Re: [sipcore] Bypassing out-of-service intermediate Proxy
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2010 06:45:24 -0000

Hi,

>>Not exactly the same case that Youssef is talking about, but every now and then I have had discussions that 
>>it would be useful to be able to re-negotiate the route set (not only the local/remote targets, but also the 
>>record-routes) during a dialog. E.g. in Outbound cases it could be used to move ongoing dialogs from a 
>>failed flow to another (it is not always possible to achieve it by using domain names and DNS).
>>
>>A problem is of course backward compability, becuase you would need to ensure that every intermediary 
>>that wants to remain in the route set inserts Record-Route in every re-INVITE/UPDATE (or whatever 
>>request is used to re-negotiate the route set).
>>
>>No, I did not suggest that we start work on such functionality :)
>
>We already have a way to do that: INVITE with Replaces.

Sure, but that requires the establishment of a new session. 

Because I don't think it's allowd to send a re-INVITE, in order for a session to replace "itself", is it?

Regards,

Christer