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

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 02 December 2010 17:19 UTC

Return-Path: <dworley@avaya.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 27D7528C1BC for <sipcore@core3.amsl.com>; Thu, 2 Dec 2010 09:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level:
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, 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 vflAgg0WG5fS for <sipcore@core3.amsl.com>; Thu, 2 Dec 2010 09:19:20 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 7715A28C1C7 for <sipcore@ietf.org>; Thu, 2 Dec 2010 09:19:20 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEpk90yHCzI1/2dsb2JhbACjInGpdAKZD4VHBIReiTM
X-IronPort-AV: E=Sophos;i="4.59,289,1288584000"; d="scan'208";a="252935122"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Dec 2010 12:20:35 -0500
X-IronPort-AV: E=Sophos;i="4.59,289,1288584000"; d="scan'208";a="549036432"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 02 Dec 2010 12:20:35 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 2 Dec 2010 12:20:35 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@cisco.com>, "youssef.chadli@orange-ftgroup.com" <youssef.chadli@orange-ftgroup.com>
Date: Thu, 2 Dec 2010 12:19:46 -0500
Thread-Topic: [sipcore] Bypassing out-of-service intermediate Proxy
Thread-Index: AcuGucJgDasXXQisTj27OAMu8zhX2wHA82BUASHjmBs=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288A74@DC-US1MBEX4.global.avaya.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>
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
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
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: Thu, 02 Dec 2010 17:19:24 -0000

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Christer Holmberg [christer.holmberg@ericsson.com]

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

No, I did not suggest that we start work on such functionality :)
_______________________________________________

You mean that the renegotiation would be initiated by an *intermediate* proxy.  That is extremely ugly!

Dale