Re: [sip-overload] The frequency of re-negotiating overload control schemes

"Vijay K. Gurbani" <vkg@bell-labs.com> Wed, 07 September 2011 19:37 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 8B0E321F8B05 for <sip-overload@ietfa.amsl.com>; Wed, 7 Sep 2011 12:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level:
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UoKjeQNTyUC3 for <sip-overload@ietfa.amsl.com>; Wed, 7 Sep 2011 12:37:52 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id B762421F8AD8 for <sip-overload@ietf.org>; Wed, 7 Sep 2011 12:37:52 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p87JdgpA004858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sip-overload@ietf.org>; Wed, 7 Sep 2011 14:39:42 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p87JdfkT000686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sip-overload@ietf.org>; Wed, 7 Sep 2011 14:39:42 -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 p87Jdf1M004043 for <sip-overload@ietf.org>; Wed, 7 Sep 2011 14:39:41 -0500 (CDT)
Message-ID: <4E67C906.1030909@bell-labs.com>
Date: Wed, 07 Sep 2011 14:41:58 -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.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b2 Thunderbird/3.1.12
MIME-Version: 1.0
To: sip-overload@ietf.org
References: <4E613160.5010701@bell-labs.com> <A7854CEA-AC39-434E-82E6-C9E608B7741B@ntt-at.com> <4E661C01.3010803@bell-labs.com> <BECE4232-9F57-4FDF-9D3F-2D8D29484C75@ntt-at.com> <4E66DB5F.1090205@bell-labs.com> <4E676532.4060408@alcatel-lucent.com> <4E677F4B.4080708@bell-labs.com> <4E677F89.6070000@alcatel-lucent.com>
In-Reply-To: <4E677F89.6070000@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [sip-overload] The frequency of re-negotiating overload control schemes
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: Wed, 07 Sep 2011 19:37:53 -0000

On 09/07/2011 09:28 AM, Volker Hilt wrote:
> I think this is a good case in which the server can switch. Otherwise
> the client forces the server into using a specific algorithm, which it
> may not even support.

True; this is the flip side that I did not consider.  I simply
assumed that the server supported all schemes offered by the client,
and would therefore zero in on the singleton algorithm in the
client's list.

> I think we are talking about a very small list. If you are concerned
> about the Via header length, we can make the identifiers very small.

That is okay.  I do not forsee having too many algorithms here.

On when to do re-negotiation:
> I think it makes sense to specify this for the server side. I.e., give
> recommendations of when the server may consider to change an algorithm.

Hmmm ... I had always assumed that this will be done on the client side.
However, if the client is sending the complete algorithm list in
every request, then it does not make sense to do it there for obvious
reasons.

So it looks like we will have to do it on the server side.  I will
update the draft as such.

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/