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

Paul Kyzivat <pkyzivat@cisco.com> Wed, 03 November 2010 13:57 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 534B63A68D2 for <sipcore@core3.amsl.com>; Wed, 3 Nov 2010 06:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level:
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_29=0.6, J_CHICKENPOX_39=0.6, 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 rCicjUpJjEpO for <sipcore@core3.amsl.com>; Wed, 3 Nov 2010 06:57:35 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 164D23A69B3 for <sipcore@ietf.org>; Wed, 3 Nov 2010 06:57:33 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIIH0UxAZnwN/2dsb2JhbAChZHGiQ5tahUYEilWDCA
X-IronPort-AV: E=Sophos;i="4.58,289,1286150400"; d="scan'208";a="178153144"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 03 Nov 2010 13:57:39 +0000
Received: from [10.86.250.226] (bxb-vpn3-738.cisco.com [10.86.250.226]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id oA3DvdDO008250 for <sipcore@ietf.org>; Wed, 3 Nov 2010 13:57:39 GMT
Message-ID: <4CD16A52.7090006@cisco.com>
Date: Wed, 03 Nov 2010 09:57:38 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: sipcore@ietf.org
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>
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214102155080@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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: Wed, 03 Nov 2010 13:57:40 -0000

This idea seems analogous to the auto assembly line deciding to bypass 
the broken station where the engine is inserted into the car, and just 
send the car on to the next station without its engine. The consumer who 
receives this car may be less than satisfied. :-(

	Thanks,
	Paul

On 11/3/2010 5:55 AM, youssef.chadli@orange-ftgroup.com wrote:
>
> I understand that the usage of DNS to provide alternate server is a way to ensure redundancy. In such solution, to be able to handle SIP requests inside a SIP dialog and for which the proxy need to be "dialog statefull", there is a need to implement a mechanism that would allow the "alternate" server to share the same SIP dialog contexts.
>
> My idea is in case of unavailability of the next hop and in case no alternate server is returned by DNS (or alternate servers are unreachable too), instead of rejecting the request (which would make the call/session fails), the SIP Proxy may send it to the hop after the unreachable one in the Route. This alternative would be authorized only if the Proxy knows that it's better to bypass the unreachable node instead of rejecting the request. The SIP proxy may get this information via a URI parameter in the Route entry of the "unreachable" node for example
>
> Best regards,
>
> Youssef
>
> -----Message d'origine-----
> De : Worley, Dale R (Dale) [mailto:dworley@avaya.com]
> Envoyé : vendredi 29 octobre 2010 20:22
> À : CHADLI Youssef RD-CORE-ISS; adam@nostrum.com
> Cc : sipcore@ietf.org
> Objet : RE: [sipcore] Bypassing out-of-service intermediate Proxy
>
> ________________________________________
> From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of youssef.chadli@orange-ftgroup.com [youssef.chadli@orange-ftgroup.com]
>
> I understand that the intention of this text in RFC 3261 is to fail over to an alternate server that serves the same function. Though, it's not explicitly stated.
>
> However, I did not find any text in RFC 3261 that would make forbidden failing over to a proxy further down the path.  Moreover, I did not see any problem to such behaviour.
> ________________________________
>
> If a particular URI is included in a Route header, then there is some important function the server with that URI is to perform.  If one element ignores this URI and sends the request to the next URI in the Route header, presumably the function of the skipped server will not be performed.
>
> In all cases that I have heard about, the correct way to provide alternate servers for a failed server is to construct a DNS SRV name which maps to the primary and alternate server as is desired.
>
> For instance, if functionA is to be serviced by serverA but in an emergency the request can be routed to serverB, and if functionB is serviced by serverB, then we construct two SRV names:
>
> functionA    SRV   serverA  priority=1
> functionA    SRV   serverB  priority=2
>
> functionB    SRV   serverB priority=1
>
> and use this Route header:
>
> Route:  sip:functionA, sip:functionB
>
> If an element has a request with this Route header, it will send the request to sp:functionA using the RFC 3263 rules, viz., attempt to send to serverA, and if that fails, attempt to send to serverB.
>
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>