Re: [sip-overload] draft-ietf-soc-overload-control-01 submitted
Volker Hilt <volker.hilt@alcatel-lucent.com> Tue, 08 February 2011 22:24 UTC
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id A7A803A6855 for <sip-overload@core3.amsl.com>;
Tue, 8 Feb 2011 14:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[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 OiIZpC9NkoHz for
<sip-overload@core3.amsl.com>; Tue, 8 Feb 2011 14:24:19 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by
core3.amsl.com (Postfix) with ESMTP id B4BB33A6835 for
<sip-overload@ietf.org>; Tue, 8 Feb 2011 14:24:19 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com
(usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com
(8.13.8/IER-o) with ESMTP id p18MOQP2021913 (version=TLSv1/SSLv3
cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sip-overload@ietf.org>;
Tue, 8 Feb 2011 16:24:26 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com
(usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by
usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id
p18MOQeS002752 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for
<sip-overload@ietf.org>; Tue, 8 Feb 2011 16:24:26 -0600
Received: from [135.112.131.41] (135.3.63.242) by
USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP
Server (TLS) id 8.3.106.1; Tue, 8 Feb 2011 16:24:26 -0600
Message-ID: <4D51C2BD.1090206@alcatel-lucent.com>
Date: Tue, 8 Feb 2011 17:25:01 -0500
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: <sip-overload@ietf.org>
References: <4D3876BF.9050009@bell-labs.com> <9ECCF01B52E7AB408A7EB85352642141027CFAFE@ftrdmel0.rd.francetelecom.fr> <4D503A57.6070206@bell-labs.com> <9ECCF01B52E7AB408A7EB8535264214102810BAC@ftrdmel0.rd.francetelecom.fr> <4D514B5B.6030503@bell-labs.com>
<9ECCF01B52E7AB408A7EB8535264214102810E50@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214102810E50@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [sip-overload] draft-ietf-soc-overload-control-01 submitted
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 22:24:20 -0000
On 2/8/2011 11:37 AM, bruno.chatras@orange-ftgroup.com wrote: >> -----Message d'origine----- >> De : Vijay K. Gurbani [mailto:vkg@bell-labs.com] >> Envoyé : mardi 8 février 2011 14:56 >> À : CHATRAS Bruno RD-CORE-ISS >> Cc : sip-overload@ietf.org >> Objet : Re: [sip-overload] draft-ietf-soc-overload-control-01 submitted >> >> On 02/08/2011 07:55 AM, bruno.chatras@orange-ftgroup.com wrote: >>> [BC] I was trying to find a solution for the case where the proxy has >>> been upgraded to support filtering of messages but not AS-A. I >>> believe this will frequently happen in real networks (e.g. AS-A is an >>> old system hosting basic telephony applications for user A while AS-B >>> is a new system hosting a new overload control sensitive application, >>> the core network proxies are upgraded). >> >> Bruno: I see. The thing that bothers me about this approach --- and I >> readily subscribe to your assertion that this may happen in real >> networks --- is that (a) we are essentially performing overload control >> for AS-B two hops away, and (b) we are attempting to codify B2BUA >> behaviour in the context of overload. >> >> Even then, the proxy must have a filter so only those messages that >> AS-A will send to AS-B will be quenched. What is the nature of this >> filter? Is it prescribed anywhere? Is loading this filter an >> administrative task or will AS-A automatically send it to the proxy? >> And if so, how? These are all questions that arise in the context of >> your scenario. To what extent do we need to flesh these out if we go >> this route? > > [BC] That's a bit tricky indeed. I think I understand you point as well. May be we should just add a warning that filtering must be performed by the adjacent nodes or is this stated somewhere already? > This is essentially going down the path of end-to-end overload control, which is discussed in the design considerations draft. If AS-A is not updated to support overload control, it will drop the feedback from AS-B, which is exactly what it needs to do. If AS-A would blindly copy the feedback from AS-B to the proxy, it will throttle all traffic to AS-A even if that would not hit AS-B at all. The proxy would have to be specifically updated to copy the oc parameter, which would be unwise to do. If an update is performed, it should be updated to support regular overload control. Volker (as individual)
- [sip-overload] draft-ietf-soc-overload-control-01… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… Antoine Roly
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… bruno.chatras
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… bruno.chatras
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… bruno.chatras
- Re: [sip-overload] draft-ietf-soc-overload-contro… Volker Hilt
- Re: [sip-overload] draft-ietf-soc-overload-contro… Volker Hilt
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- [sip-overload] Comments on draft-ietf-soc-overloa… Janet P Gunn
- Re: [sip-overload] Comments on draft-ietf-soc-ove… Volker Hilt