Re: [sip-overload] draft-ietf-soc-overload-control-13
Christer Holmberg <christer.holmberg@ericsson.com> Tue, 23 July 2013 03:54 UTC
Return-Path: <christer.holmberg@ericsson.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 7C9AF11E81D5; Mon, 22 Jul 2013 20:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level:
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 282wA7MmVgA8;
Mon, 22 Jul 2013 20:54:49 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by
ietfa.amsl.com (Postfix) with ESMTP id D5A6111E8183;
Mon, 22 Jul 2013 20:54:46 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f0b6d0000002d5-fa-51edfe84dd3a
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by
mailgw1.ericsson.se (Symantec Mail Security) with SMTP id
F2.4E.00725.48EFDE15; Tue, 23 Jul 2013 05:54:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by
ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0328.009;
Tue, 23 Jul 2013 05:54:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Yu, James" <james.yu@neustar.biz>, Janet P Gunn <jgunn6@csc.com>
Thread-Topic: [sip-overload] draft-ietf-soc-overload-control-13
Thread-Index: AQHOhxU3F7sJun9uH0SBY0IRumtD5plw/7kAgACg/lA=
Date: Tue, 23 Jul 2013 03:54:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3FC99D@ESESSMB209.ericsson.se>
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>
In-Reply-To: <56FB15AFE08E1242B0736CBDCE6E856108096C3D@stntexmb12.cis.neustar.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative;
boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3FC99DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGfG3Vrf139tAg4eHGS2u9K1kslg0LcTi
3MMvrBbtF7eyWux/mmDRsEbOYtPyW+wO7B59l108vt46yORx8XqUx5IlP5k8djQ8Zw5gjeKy
SUnNySxLLdK3S+DKWHF4K0vBvquMFTuWTGBtYHxznrGLkZNDQsBEonHlXShbTOLCvfVsXYxc
HEIChxklpn9+DOUsYZS4NH0ZSxcjBwebgIVE9z9tEFNEwFVi3jYLkBJmgUYmifan19lABgkL
2EnMfzoZbKiIgL3Eu+bXLBC2lcTxfxvYQHpZBFQl7nx0AQnzCvhK7GuaArVqK7PE3eu/wFZx
CgRJLFsENpIR6Lbvp9YwgdjMAuISHw5eZ4a4WUBiyZ7zULaoxMvH/1ghbCWJHxsugY1hFsiX
eLRQFWKVoMTJmU9YJjCKzkIyaRZC1SwkVRBhTYn1u/QhqhUlpnQ/ZIewNSRa58xlRxZfwMi+
ipE9NzEzJ73ccBMjMCoPbvmtu4Px1DmRQ4zSHCxK4ryb9M4ECgmkJ5akZqemFqQWxReV5qQW
H2Jk4uCUamA0Xen0Q2Tt3tw5J930w2YI3NxdK5K45kDo0j0nL20W17xX8kn4xKRJ0dKMnAo1
7666H33EnrLo8Nb5rQJ2C1iKd2x46cPT3sPe8qWb9ybH8eiP/31/HPjPx7k5Zf29XdITf89b
Kdv5+fzLyYc/HLlecSWRx3KT+8JMOR85W7VMpaq8yCL9QP7TSizFGYmGWsxFxYkAvIIhdZgC AAA=
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: Tue, 23 Jul 2013 03:54:53 -0000
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] Puolesta Yu, James Lähetetty: 22. heinäkuuta 2013 23:12 Vastaanottaja: Janet P Gunn Kopio: sip-overload-bounces@ietf.org; volkerh@bell-labs.com; vkg@bell-labs.com; sip-overload@ietf.org; 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
- [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