[sip-overload] Issue: Multiple algorithms -> Single algorithm for overload control
"Vijay K. Gurbani" <vkg@bell-labs.com> Fri, 10 June 2011 21:34 UTC
Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B00F11E8159 for <sip-overload@ietfa.amsl.com>; Fri, 10 Jun 2011 14:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1J0MTsULt1K for <sip-overload@ietfa.amsl.com>; Fri, 10 Jun 2011 14:34:02 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id ABFA411E80EC for <sip-overload@ietf.org>; Fri, 10 Jun 2011 14:34:02 -0700 (PDT)
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 p5ALY1o0017817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sip-overload@ietf.org>; Fri, 10 Jun 2011 16:34:01 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5ALY1lA023344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sip-overload@ietf.org>; Fri, 10 Jun 2011 16:34:01 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p5ALY1Up029566 for <sip-overload@ietf.org>; Fri, 10 Jun 2011 16:34:01 -0500 (CDT)
Message-ID: <4DF28DE3.6080804@bell-labs.com>
Date: Fri, 10 Jun 2011 16:34:27 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: [sip-overload] Issue: Multiple algorithms -> Single algorithm for overload control
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 10 Jun 2011 21:34:04 -0000
Folks: During the Prague IETF, Mr. Kaplan reopened the case for supporting multiple overload control algorithms [1]. Summarizing, the basic problems with multiple algorithms are: 1) Interoperability suffers as protocol gets complex. 2) Get out one algorithm now (loss), and later if there is a need to standardize more add the oc-algo parameter in a backwards compatible manner. 3) Re-negotiating the chosen algorithm is not trivial. 4) Servers will have to maintain negotiated algorithms as pieces of state for a potentially large set of upstream clients. I cannot say that I am unsympathetic to the above list. If we can simplify processing, then we should do so. The main reason to support multiple algorithms appear to have been the need to not preclude rate-based algorithms [2,3]. However subsequent discussions in the thread started off by [3] have resulted in the understanding that rate-based algorithms may have a slight advantage if the offered load at the client significantly surges over a period of time << then the overload server's feedback period. Since the overload server's feedback period is already short (500ms by default), the advantage possessed by rate-based algorithms may be moot [5]. Further, minimizing state in the server is an argument to pick loss-based as the default algorithm instead of rate-based. The latter requires the server to assign --- and keep track --- of a share of its overall capacity with each upstream client. So ... given all this, it may be a good idea to go with one algorithm, and make that the loss based algorithm. I will like have discussion so we can reach consensus on this issue and close it for good. [1] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00564.html [2] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00565.html [3] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00600.html [4] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00606.html [5] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00606.html Thanks, - 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/
- [sip-overload] Issue: Multiple algorithms -> Sing… Vijay K. Gurbani
- Re: [sip-overload] Issue: Multiple algorithms -> … Janet P Gunn
- Re: [sip-overload] Issue: Multiple algorithms -> … Bharrat, Shaun
- Re: [sip-overload] Issue: Multiple algorithms -> … Vijay K. Gurbani
- Re: [sip-overload] Issue: Multiple algorithms -> … Janet P Gunn
- Re: [sip-overload] Issue: Multiple algorithms -> … phil.m.williams
- Re: [sip-overload] Issue: Multiple algorithms -> … NOEL, ERIC C (ERIC C)
- Re: [sip-overload] Issue: Multiple algorithms -> … Janet P Gunn
- Re: [sip-overload] Issue: Multiple algorithms -> … phil.m.williams
- Re: [sip-overload] Issue: Multiple algorithms -> … phil.m.williams
- Re: [sip-overload] Issue: Multiple algorithms -> … Vijay K. Gurbani
- Re: [sip-overload] Issue: Multiple algorithms -> … phil.m.williams
- Re: [sip-overload] Issue: Multiple algorithms -> … Vijay K. Gurbani