Re: [sip-overload] draft-ietf-soc-overload-control-13
"Yu, James" <james.yu@neustar.biz> Wed, 31 July 2013 18:05 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 95ADE11E819F; Wed, 31 Jul 2013 11:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level:
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.092, 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 QBvEW9w0ZsHG; Wed, 31 Jul 2013 11:05:52 -0700 (PDT)
Received: from neustar.com (mx2.neustar.com [156.154.25.104]) by ietfa.amsl.com (Postfix) with ESMTP id 58BFF11E8186; Wed, 31 Jul 2013 11:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1375293849; x=1690650383; q=dns/txt; h=From:Subject:Date:Message-ID:Content-Language: Content-Type; bh=A/ubhWAKANqZo27F2emU9QfpM/VgAAWisrIbiGJBtVw=; b=m6H3eZpJIIxSfMiu/jwjDZqCKuBeo10mr4sQJ6wXl1OVHgKJEQhQReNP0x6953 mipiwrTtbT12Og+SgmUxZD9A==
Received: from ([10.31.58.70]) by chihiron1.nc.neustar.com with ESMTP with TLS id J041123128.21809743; Wed, 31 Jul 2013 14:04:07 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.95]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.02.0342.003; Wed, 31 Jul 2013 14:05:26 -0400
From: "Yu, James" <james.yu@neustar.biz>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [sip-overload] draft-ietf-soc-overload-control-13
Thread-Index: AQHOh1hieKRy9s++6U21x6LAxw4G95l+2MqAgABVToD///QlMA==
Date: Wed, 31 Jul 2013 18:05:26 +0000
Message-ID: <56FB15AFE08E1242B0736CBDCE6E8561080A51DC@STNTEXMB10.cis.neustar.com>
References: <56FB15AFE08E1242B0736CBDCE6E85610808C32F@stntexmb12.cis.neustar.com> <OF5E51912C.2DA069C7-ON85257B98.0069B365-85257B98.006B8697@csc.com> <56FB15AFE08E1242B0736CBDCE6E85610808EF90@stntexmb12.cis.neustar.com> <56FB15AFE08E1242B0736CBDCE6E856108096C00@stntexmb12.cis.neustar.com> <OF1E1E4629.9430E707-ON85257BB0.006CEB61-85257BB0.006D574F@csc.com> <56FB15AFE08E1242B0736CBDCE6E856108096C3D@stntexmb12.cis.neustar.com> <7594FB04B1934943A5C02806D1A2204B1C3FC99D@ESESSMB209.ericsson.se> <56FB15AFE08E1242B0736CBDCE6E8561080A4D90@STNTEXMB10.cis.neustar.com> <7594FB04B1934943A5C02806D1A2204B1C41581A@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C41581A@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.31.33.140]
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: sM9GhtFENKVUki6eshSViA==
Content-Type: multipart/alternative; boundary="_000_56FB15AFE08E1242B0736CBDCE6E8561080A51DCSTNTEXMB10cisne_"
MIME-Version: 1.0
Cc: "sip-overload-bounces@ietf.org" <sip-overload-bounces@ietf.org>, "volkerh@bell-labs.com" <volkerh@bell-labs.com>, "vkg@bell-labs.com" <vkg@bell-labs.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>, "hgs@cs.columbia.edu" <hgs@cs.columbia.edu>
Subject: Re: [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: Wed, 31 Jul 2013 18:05:56 -0000
I agree with the change. James From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] Sent: Wednesday, July 31, 2013 10:47 AM To: Yu, James Cc: sip-overload-bounces@ietf.org; volkerh@bell-labs.com; vkg@bell-labs.com; sip-overload@ietf.org; hgs@cs.columbia.edu Subject: VS: [sip-overload] draft-ietf-soc-overload-control-13 Hi, >Sorry for a late reply. I was just back from vacation. > >I am wondering if it should be > > algo-value = “loss” / other-algo > > where algo-value would only contain a single algorithm value such as “loss” or something else. Keep in mind that the definition of other-algo is only a single character. But, we can change other-algo to: other-algo = 1*(%x41-5A / %x61-7A / %x30-39) …which probably clarifies even further. Regards, Christer From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] Sent: Monday, July 22, 2013 11:55 PM To: Yu, James; Janet P Gunn Cc: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; volkerh@bell-labs.com<mailto:volkerh@bell-labs.com>; vkg@bell-labs.com<mailto:vkg@bell-labs.com>; sip-overload@ietf.org<mailto:sip-overload@ietf.org>; hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu> Subject: VS: [sip-overload] draft-ietf-soc-overload-control-13 Hi, I don’t think the current ABNF allows a list without comma separation. Keep in mind that “algo-list” does not represent the list, only a single value in the list. But, I understand your confusion, and in fact I think ”algo-list” is a little misleading. I think it would be better to call it “algo-value”, or something similar. oc-algo = "oc-algo" EQUAL DQUOTE algo-value *(COMMA algo-value)DQUOTE algo-value = "loss" / *(other-algo) other-algo = %x41-5A / %x61-7A / %x30-39 Regards, Christer Lähettäjä: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> [mailto:sip-overload-bounces@ietf.org] Puolesta Yu, James Lähetetty: 22. heinäkuuta 2013 23:12 Vastaanottaja: Janet P Gunn Kopio: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; volkerh@bell-labs.com<mailto:volkerh@bell-labs.com>; vkg@bell-labs.com<mailto:vkg@bell-labs.com>; sip-overload@ietf.org<mailto:sip-overload@ietf.org>; hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu> Aihe: Re: [sip-overload] draft-ietf-soc-overload-control-13 Janet, My comment is not on having multiple algorithms in the via header but on the syntax in the current I-D that could allow multiple algorithms that are not separated by “,”. Please check the syntax by having “rate” and “foo”. James From: Janet P Gunn [mailto:jgunn6@csc.com] Sent: Monday, July 22, 2013 3:54 PM To: Yu, James Cc: hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu>; vkg@bell-labs.com<mailto:vkg@bell-labs.com>; volkerh@bell-labs.com<mailto:volkerh@bell-labs.com>; sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; sip-overload@ietf.org<mailto:sip-overload@ietf.org>; sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> Subject: Re: [sip-overload] draft-ietf-soc-overload-control-13 There is at least one "other-algo", "rate". When algo-list is included in the Via headers of a message sent by the client to the server, it may have multiple algorithms included in the algo-list - all the algorithms supported by the client. When algo-list is included in the Via headers sent from the server to the client, it should have " one and only one algorithm" in the list. Janet From: "Yu, James" <james.yu@neustar.biz<mailto:james.yu@neustar.biz>> To: "hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu>" <hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu>>, "vkg@bell-labs.com<mailto:vkg@bell-labs.com>" <vkg@bell-labs.com<mailto:vkg@bell-labs.com>>, "volkerh@bell-labs.com<mailto:volkerh@bell-labs.com>" <volkerh@bell-labs.com<mailto:volkerh@bell-labs.com>> Cc: "sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>" <sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>>, "sip-overload@ietf.org<mailto:sip-overload@ietf.org>" <sip-overload@ietf.org<mailto:sip-overload@ietf.org>> Date: 07/22/2013 03:19 PM Subject: [sip-overload] draft-ietf-soc-overload-control-13 Sent by: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> ________________________________ 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_______________________________________________ sip-overload mailing list sip-overload@ietf.org<mailto:sip-overload@ietf.org> https://www.ietf.org/mailman/listinfo/sip-overload ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2013.0.2904 / Virus Database: 3204/6510 - Release Date: 07/22/13 ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2013.0.2904 / Virus Database: 3209/6536 - Release Date: 07/30/13 ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2013.0.2904 / Virus Database: 3209/6536 - Release Date: 07/30/13
- [sip-overload] draft-ietf-soc-overload-rate-contr… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Janet P Gunn
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Janet P Gunn
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… DRAGE, Keith (Keith)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… DRAGE, Keith (Keith)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Christer Holmberg
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Christer Holmberg
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] draft-ietf-soc-overload-rate-c… Christer Holmberg
- [sip-overload] draft-ietf-soc-overload-control-13 Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… Janet P Gunn
- Re: [sip-overload] draft-ietf-soc-overload-contro… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-contro… Christer Holmberg
- Re: [sip-overload] draft-ietf-soc-overload-contro… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-contro… Christer Holmberg
- Re: [sip-overload] draft-ietf-soc-overload-contro… Yu, James
- Re: [sip-overload] draft-ietf-soc-overload-contro… Vijay K. Gurbani
- Re: [sip-overload] draft-ietf-soc-overload-contro… Christer Holmberg