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

"Yu, James" <james.yu@neustar.biz> Mon, 22 July 2013 19:18 UTC

Return-Path: <james.yu@neustar.biz>
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 3477F11E80F5; Mon, 22 Jul 2013 12:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 F6CoXJb76lLZ; Mon, 22 Jul 2013 12:18:44 -0700 (PDT)
Received: from neustar.com (mx2.neustar.com [156.154.25.104]) by ietfa.amsl.com (Postfix) with ESMTP id DF5DA11E80AD; Mon, 22 Jul 2013 12:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1374520668; x=1689878326; q=dns/txt; h=From:Subject:Date:Message-ID:Content-Language: Content-Type; bh=bnRHNx6Up/ucrkjjeyq4JO6Ik+pXyXfqsbGssVC92u0=; b=qFaXGKH8l9e9zWOCr7LB5xAVFn6PxWA32PXgn1PdxvVz6jdcvcpzxH2iePVn1B yC1ki1dimixXiqFSSdz2ZHlg==
Received: from ([10.31.58.70]) by chihiron2.nc.neustar.com with ESMTP with TLS id J041123125.22744409; Mon, 22 Jul 2013 15:17:47 -0400
Received: from stntexmb12.cis.neustar.com ([169.254.2.76]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.02.0342.003; Mon, 22 Jul 2013 15:18:12 -0400
From: "Yu, James" <james.yu@neustar.biz>
To: "hgs@cs.columbia.edu" <hgs@cs.columbia.edu>, "vkg@bell-labs.com" <vkg@bell-labs.com>, "volkerh@bell-labs.com" <volkerh@bell-labs.com>
Thread-Topic: [sip-overload] draft-ietf-soc-overload-control-13
Thread-Index: AQHOhxA1oeh2GmM75kOFVkO2B67yLw==
Date: Mon, 22 Jul 2013 19:18:12 +0000
Message-ID: <56FB15AFE08E1242B0736CBDCE6E856108096C00@stntexmb12.cis.neustar.com>
References: <56FB15AFE08E1242B0736CBDCE6E85610808C32F@stntexmb12.cis.neustar.com> <OF5E51912C.2DA069C7-ON85257B98.0069B365-85257B98.006B8697@csc.com> <56FB15AFE08E1242B0736CBDCE6E85610808EF90@stntexmb12.cis.neustar.com>
In-Reply-To: <56FB15AFE08E1242B0736CBDCE6E85610808EF90@stntexmb12.cis.neustar.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.130.24]
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: e4oYRJoSAYfDi/gc24OWOA==
Content-Type: multipart/alternative; boundary="_000_56FB15AFE08E1242B0736CBDCE6E856108096C00stntexmb12cisne_"
MIME-Version: 1.0
Cc: "sip-overload-bounces@ietf.org" <sip-overload-bounces@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: [sip-overload] draft-ietf-soc-overload-control-13
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: Mon, 22 Jul 2013 19:18:56 -0000

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.

James