[sip-overload] Sec 5 and 6 Re: WG Last Call for draft-ietf-soc-overload-control-12
Janet P Gunn <jgunn6@csc.com> Thu, 07 March 2013 02:07 UTC
Return-Path: <jgunn6@csc.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 71B7121F871C; Wed, 6 Mar 2013 18:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level:
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.300,
BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6,
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 ZG7Oa9kQQTW6;
Wed, 6 Mar 2013 18:07:37 -0800 (PST)
Received: from mail86.messagelabs.com (mail86.messagelabs.com
[216.82.242.179]) by ietfa.amsl.com (Postfix) with ESMTP id B06E221F8732;
Wed, 6 Mar 2013 18:07:30 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-11.tower-86.messagelabs.com!1362622048!38477878!1
X-Originating-IP: [20.137.52.151]
X-StarScan-Received:
X-StarScan-Version: 6.8.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22048 invoked from network); 7 Mar 2013 02:07:29 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151) by
server-11.tower-86.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;
7 Mar 2013 02:07:29 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id
r2727RsC016135; Wed, 6 Mar 2013 21:07:28 -0500 (EST)
In-Reply-To: <51189F14.6050405@ericsson.com>
References: <51110A56.7030402@ericsson.com> <51189F14.6050405@ericsson.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
MIME-Version: 1.0
X-KeepSent: 1EFD032C:5418DF57-85257B27:000B56FE; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF1EFD032C.5418DF57-ON85257B27.000B56FE-85257B27.000B9603@csc.com>
Date: Wed, 6 Mar 2013 21:06:54 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3
HF204|September 20, 2011) at 03/06/2013 09:02:07 PM,
Serialize complete at 03/06/2013 09:02:07 PM
Content-Type: multipart/alternative;
boundary="=_alternative 000B8FC985257B27_="
Cc: sip-overload-bounces@ietf.org, Volker Hilt <volker.hilt@alcatel-lucent.com>,
"sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: [sip-overload] Sec 5 and 6 Re: WG Last Call for
draft-ietf-soc-overload-control-12
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: Thu, 07 Mar 2013 02:07:38 -0000
Sec 5.10.2 Rejecting Requests at an overloaded server. I agree with the concept “It would be fair to devote the same amount of processing at the overloaded server to the combination of rejection and processing from a non-participating client as the overloaded server would devote to processing requests from a participating client.” But how is the server to know how much it “would devote to processing requests from a participating client.” Especially under the loss scheme. It seems to me that it would make more sense to estimate R = ratio of (processing required to reject a request) to (processing required to process a request) Then for the loss algorithm, if the server would have set oc=x, it should reject (1+R)x % of the requests from the non participating client. For the rate algorithm, if the server would have set oc=x, it should reject anything over x/ (1+R) requests per second from the non participating client. Sec 6.2 “some algorithm called "A".” Is there any way to be sure that, when the client says “A” and the server says “A”, they mean the same thing? Janet This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. From: Salvatore Loreto <salvatore.loreto@ericsson.com> To: "sip-overload@ietf.org" <sip-overload@ietf.org> Cc: Volker Hilt <volker.hilt@alcatel-lucent.com> Date: 02/11/2013 02:35 AM Subject: Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12 Sent by: sip-overload-bounces@ietf.org this is just a reminder for this WG Last Call I haven't seen yet any comment or feedback please we really need you spend some time to reading and reviewing the draft thanks a lot Salvatore On 2/5/13 3:34 PM, Salvatore Loreto wrote: Dear WG partecipants, Volker and I would like to initiate a second 2 weeks WG Last Call on draft-ietf-soc-overload-control-12 (" Session Initiation Protocol (SIP) Overload Control") http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt The first WGLC that we run ( http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html ) has produced a significant amount of feedback and comments that have been discussed and addressed in subsequent versions Please send your reviews, as well as expression of support regarding document readiness for IESG (or not) either to the *soc* mailing list ( sip-overload@ietf.org), or directly to the WG chairs (Murray Kucherawy and myself). Comments like "I've read the document and it is Ok to publish" or "I've read the document and it has the following issues" are useful and would be gratefully accepted by chairs. The WG LC will end on Friday, February 19th. Thank you, Salvatore as an SoC co-chair. _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload
- [sip-overload] WG Last Call for draft-ietf-soc-ov… Salvatore Loreto
- Re: [sip-overload] WG Last Call for draft-ietf-so… Salvatore Loreto
- Re: [sip-overload] WG Last Call for draft-ietf-so… bruno.chatras
- Re: [sip-overload] WG Last Call for draft-ietf-so… Atle Monrad
- Re: [sip-overload] WG Last Call for draft-ietf-so… NOEL, ERIC (ERIC C)
- [sip-overload] Introduction - "This document defi… Janet P Gunn
- [sip-overload] Sec 5.8 Re: WG Last Call for draft… Janet P Gunn
- [sip-overload] Sec 5 and 6 Re: WG Last Call for d… Janet P Gunn
- Re: [sip-overload] WG Last Call for draft-ietf-so… Vijay K. Gurbani
- Re: [sip-overload] Introduction - "This document … Vijay K. Gurbani
- Re: [sip-overload] Sec 5.8 Re: WG Last Call for d… Vijay K. Gurbani
- Re: [sip-overload] Sec 5 and 6 Re: WG Last Call f… Vijay K. Gurbani
- Re: [sip-overload] WG Last Call for draft-ietf-so… bruno.chatras
- Re: [sip-overload] WG Last Call for draft-ietf-so… Vijay K. Gurbani
- Re: [sip-overload] WG Last Call for draft-ietf-so… Vijay K. Gurbani
- Re: [sip-overload] WG Last Call for draft-ietf-so… NOEL, ERIC C (ERIC C)