Re: [sip-overload] draft-ietf-soc-overload-control-13

["Vijay K. Gurbani" <[e-mail]>]

James: This is a quick ack of your email.  It is on my list of
things to do.  I will circle back on it sometimes next week.

Cheers,

On 07/22/2013 02:18 PM, Yu, James wrote:
> Hi, Henning, Vijay, Volker,
>
> When I reviewed draft-ietf-soc-overload-rate-control-04.txt, I glanced
> through the syntax in this I-D to understand the oc related parameters.
>
> When looking at “algo-list”, I wonder if there are two “other-algo” such
> as “abc” and “xyz”, ‘abc” and “xyz” won’t be comma-separated based on
> the oc-algo syntax.  It seems that algo-list would be
>
>   algo-list = “loss“/ other-algo
>
> This would ensure that one and only one algorithm is present in
> algo-list.  If there is no algorithm other than “loss”, *(COMMA
> algo-list) would take care of that.
>
> Since algo-list contains a single algorithm, may be it is better to use
> “algo” only.  Or if algo-list contains a list of comma separated
> algorithms, then alog-list and oc-algo can be modified so that oc-algo
> has a single “algo-list”.  The latter may be better because the current
> syntax would allow the same algorithm to appear more than once.

- 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} / [e-mail]
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq