Re: [sip-overload] draft-ietf-soc-overload-control-01 submitted

<bruno.chatras@orange-ftgroup.com> Tue, 08 February 2011 16:37 UTC

Return-Path: <bruno.chatras@orange-ftgroup.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 094223A680A for <sip-overload@core3.amsl.com>; Tue, 8 Feb 2011 08:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 cY1R4cx39NW2 for <sip-overload@core3.amsl.com>; Tue, 8 Feb 2011 08:37:42 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id A163B3A67E3 for <sip-overload@ietf.org>; Tue, 8 Feb 2011 08:37:35 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 145C6760004; Tue, 8 Feb 2011 17:42:49 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 0CFE9760003; Tue, 8 Feb 2011 17:42:49 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Feb 2011 17:37:42 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Feb 2011 17:37:40 +0100
Message-ID: <9ECCF01B52E7AB408A7EB8535264214102810E50@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <4D514B5B.6030503@bell-labs.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-overload] draft-ietf-soc-overload-control-01 submitted
Thread-Index: AcvHn/ZyKKkq3MnqRMu+WxF4PrqVFAADgI+Q
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>
From: <bruno.chatras@orange-ftgroup.com>
To: <vkg@bell-labs.com>
X-OriginalArrivalTime: 08 Feb 2011 16:37:42.0604 (UTC) FILETIME=[81CBB8C0:01CBC7AE]
Cc: sip-overload@ietf.org
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 16:37:44 -0000

> -----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?
> 
> > [BC] I agree under certain assumptions REQ-23 can be met. That's why
> > I think that "partial" is more suitable than "Yes". "Yes under
> > certain assumptions" would be fine as well.
> 
> I agree; that is probably the best we can do.  Unless someone else has
> any objections, I will update REQ-23 to read "Partial".
> 
> Thank you,
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/