[sipcore] Bypassing out-of-service intermediate Proxy

<youssef.chadli@orange-ftgroup.com> Thu, 02 September 2010 16:56 UTC

Return-Path: <youssef.chadli@orange-ftgroup.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id DAAF53A69A4 for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 09:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.759
X-Spam-Status: No, score=-0.759 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id RepKvjtXiHsc for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 09:56:52 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com []) by core3.amsl.com (Postfix) with ESMTP id A344B3A6A9F for <sipcore@ietf.org>; Thu, 2 Sep 2010 09:56:13 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain []) by localhost (Postfix) with SMTP id 93C41FC4012 for <sipcore@ietf.org>; Thu, 2 Sep 2010 18:56:42 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown []) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 89A82FC400D for <sipcore@ietf.org>; Thu, 2 Sep 2010 18:56:42 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Thu, 2 Sep 2010 18:56:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4ABF.D14EC160"
Date: Thu, 2 Sep 2010 18:56:21 +0200
Message-ID: <9ECCF01B52E7AB408A7EB8535264214101CD7EE2@ftrdmel0.rd.francetelecom.fr>
Thread-Topic: Bypassing out-of-service intermediate Proxy
Thread-Index: ActKv8TggzTYUuFvQcWqPQhNQ1ErbQ==
From: <youssef.chadli@orange-ftgroup.com>
To: <sipcore@ietf.org>
X-OriginalArrivalTime: 02 Sep 2010 16:56:42.0818 (UTC) FILETIME=[D1BC5220:01CB4ABF]
Subject: [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 Sep 2010 16:56:53 -0000

Hi all,

I have a question regarding routeing of SIP requests and usage of ROUTE.

When a proxy or UA fails to send a SIP request to the next hop (because
this latter is not reachable) is it allowed to bypass this hop and send
the request to the hop whose URI is next in ROUTE header.

According to section 21.5.4 of RFC 3261, this proxy behaviour seems
allowed. See text in bold below:

Any opinions on this?

21.5.4 503 Service Unavailable

The server is temporarily unable to process the request due to a
temporary overloading or maintenance of the server.  The server MAY
indicate when the client should retry the request in a Retry-After
header field.  If no Retry-After is given, the client MUST act as if it
had received a 500 (Server Internal Error) response.

A client (proxy or UAC) receiving a 503 (Service Unavailable) SHOULD
attempt to forward the request to an alternate server.  It SHOULD NOT
forward any other requests to that server for the duration specified in
the Retry-After header field, if present.

Servers MAY refuse the connection or drop the request instead of
responding with 503 (Service Unavailable).

Youssef CHADLI
Orange Labs