Re: [sip-overload] soc-overload-control-08 released

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Thu, 15 March 2012 18:05 UTC

From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Thread-Topic: [sip-overload] soc-overload-control-08 released
Thread-Index: AQHNAHVuWF9dAd7G8EyDIcfWrgv2i5ZrpVWw
Date: Thu, 15 Mar 2012 18:05:22 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0E1FD200@inba-mail01.sonusnet.com>
References: <4F5E3311.6050907@bell-labs.com>
In-Reply-To: <4F5E3311.6050907@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sip-overload] soc-overload-control-08 released
Precedence: list

Hi Vijay,

1) Sec 9.1.2 Event package mechanism proposes a new event package but it does not provides the exact package for convey the overload information. Please let me whether the intention is to use "oc" parameters in Via of NOTIFY message or implementers has to choose their own event package. IMO, it is better to define some package in the standard rather than just providing the design and implementers choose the proprietary packages.

Some Editorial comments & query

2) Sec 5.4 para 2: whether overload control applies for IP or IP & port. please let me know significance of port in this context

3) Sec 5.6: "SIP server SHOULD strip the" instead "proxy SHOULD strip the"

4) Sec 5.6: Any specific reason for having "SHOULD" instead of "MUST". I'm interested in knowing whether any implementation is interested in forwarding this information to multiple hop using configuration mechanism.

5) Sec 5.7 "2nd line note" shall be added in I-D.noel-soc-overload-rate-control

6) Sec 5.10.1: It may be better to provide the recommendation for "REGISTER" message vs other message like INVITE as well. IMO, REGISTER has to be given higher priority over INVITE message in SIP servers.

Thanks
Partha


>-----Original Message-----
>From: sip-overload-bounces@ietf.org [mailto:sip-overload-
>bounces@ietf.org] On Behalf Of Vijay K. Gurbani
>Sent: Monday, March 12, 2012 11:02 PM
>To: sip-overload@ietf.org
>Subject: [sip-overload] soc-overload-control-08 released
>
>Folks: I have updated soc-overload-control to version -08 [1].
>
>I realize that WGLC does not end until Mar-15 for this draft, but I
>wanted to update the archives to include the discussion on the algorithm
>we had last week on the mailing list [2] and one minor editorial text
>agreed to in [3].
>
>Please take a look at the "Note" at the end of the algorithm in version
>-08; there are a couple of magic numbers buried there that I will like
>to expose to a wider audience to make sure that the defaults chosen
>there are reasonable.
>
>[1] http://tools.ietf.org/html/draft-ietf-soc-overload-control-08
>[2]
>http://www.ietf.org/mail-archive/web/sip-
>overload/current/threads.html#00734
>[3] http://www.ietf.org/mail-archive/web/sip-
>overload/current/msg00757.html
>
>Thanks,
>
>- vijay
>--
>Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>Web:   http://ect.bell-labs.com/who/vkg/
>_______________________________________________
>sip-overload mailing list
>sip-overload@ietf.org
>https://www.ietf.org/mailman/listinfo/sip-overload

[sip-overload] soc-overload-control-08 released Vijay K. Gurbani
Re: [sip-overload] soc-overload-control-08 releas… Ravindran, Parthasarathi