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

Paul Kyzivat <pkyzivat@cisco.com> Mon, 29 November 2010 02:55 UTC

Return-Path: <pkyzivat@cisco.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 F2D713A6BAD for <sipcore@core3.amsl.com>; Sun, 28 Nov 2010 18:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.509
X-Spam-Level:
X-Spam-Status: No, score=-110.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 88DBPR7yVKyX for <sipcore@core3.amsl.com>; Sun, 28 Nov 2010 18:55:32 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 0B4333A6BAB for <sipcore@ietf.org>; Sun, 28 Nov 2010 18:55:31 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAA6l8kxAZnwN/2dsb2JhbACifHGmSpouhUcEhFyGBYMP
X-IronPort-AV: E=Sophos;i="4.59,274,1288569600"; d="scan'208";a="186696714"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 29 Nov 2010 02:56:40 +0000
Received: from [10.86.250.233] (bxb-vpn3-745.cisco.com [10.86.250.233]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id oAT2ue2o015624; Mon, 29 Nov 2010 02:56:40 GMT
Message-ID: <4CF31667.60601@cisco.com>
Date: Sun, 28 Nov 2010 21:56:39 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
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>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058502C71893@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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 02:55:33 -0000

On 11/26/2010 6:08 PM, Christer Holmberg wrote:

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

	Thanks,
	Paul