RE: [Sipping] Re: draft-rosenberg-sipping-overload-reqs recovery
"Michael Hammer \(mhammer\)" <mhammer@cisco.com> Wed, 08 November 2006 23:15 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhwdO-0005oC-Ui; Wed, 08 Nov 2006 18:15:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhwdM-0005aD-S6 for sipping@ietf.org; Wed, 08 Nov 2006 18:15:04 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhwdL-0002qz-Dr for sipping@ietf.org; Wed, 08 Nov 2006 18:15:04 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 08 Nov 2006 18:15:03 -0500
X-IronPort-AV: i="4.09,401,1157342400"; d="scan'208"; a="109174019:sNHT62377080"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA8NF3CH019496; Wed, 8 Nov 2006 18:15:03 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA8NF3DM012182; Wed, 8 Nov 2006 18:15:03 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Nov 2006 18:15:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Re: draft-rosenberg-sipping-overload-reqs recovery
Date: Wed, 08 Nov 2006 18:15:00 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3022DADC9@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Re: draft-rosenberg-sipping-overload-reqs recovery
Thread-Index: AccDUlAgQ2uV64mZSYiP1ab6r1f0DAAMCPGwAAJHsKA=
From: "Michael Hammer (mhammer)" <mhammer@cisco.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>, Volker Hilt <volkerh@bell-labs.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-OriginalArrivalTime: 08 Nov 2006 23:15:02.0866 (UTC) FILETIME=[B82D4320:01C7038B]
DKIM-Signature: a=rsa-sha1; q=dns; l=6055; t=1163027703; x=1163891703; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mhammer@cisco.com; z=From:=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com> |Subject:RE=3A=20[Sipping]=20Re=3A=20draft-rosenberg-sipping-overload-reqs=20reco very |To:=22Jean-Francois=20Mule=22=20<jf.mule@cablelabs.com>, =0A=20=20=20=20=20= 20=20=20=22Volker=20Hilt=22=20<volkerh@bell-labs.com>, =0A=20=20=20=20=20=20 =20=20=22Cullen=20Jennings=20\(fluffy\)=22=20<fluffy@cisco.com>; X=v=3Dcisco.com=3B=20h=3Dc/tyx/3xJgsZiNZXdPN2zHnNVok=3D; b=GrjMCuU6owTZUF5PHgTDAl2oFYoJq+EhTJCky7RqdLQ1yh+jtVIpUVWwILz1TlOjNdwntXt5 ImAoFgfy+lbwl0Hv9X8OMOYSALzWn8/Q/mCHgD+rPxulF4mYZC9ULilZ;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=mhammer@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org
So the requirement is to get damped versus undamped oscillations. Mike > -----Original Message----- > From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com] > Sent: Wednesday, November 08, 2006 5:42 PM > To: Volker Hilt; Cullen Jennings (fluffy) > Cc: sipping > Subject: RE: [Sipping] Re: > draft-rosenberg-sipping-overload-reqs recovery > > > Volker wrote: > > I think that stability of overload control is an important > requirement. > > We certainly want to avoid building something that starts > to oscillate > > once it reaches overload state. > > Oscillations are often unavoidable in overload conditions, > it's the characterization of these oscillations (amplitude, > duration, frequency, > ...) that may lead to instability. > > > Cullen wrote: > > >>> A possible additional requirement.... > > >>> Imagine a system (perhaps a single proxy) that could do > 100cps. It > > >>> is in steady state doing 80cps with very few > retransmission. Then > > >>> for 5 minutes the incoming requests goes to 500cps then drops > > back > > >>> to an incoming call rate of 80cps. The question is, how long > > before > > >>> the system gets back to the state where it if is successfully > > >>> processing all the 80cps? > > Volker added: > > It may be somehow implicit to REQ 1 > > since an unstable system will hardly be able to maintain > the overall > > useful throughput at a high level. > > Following in Cullen's example, I interpret requirement #1 to > mean: out of the 500 cps, the system under load should pick > up the *useful* transactions to keep the using applications happy. > > May be a way to help formulate Cullen's example is to > introduce some wording or requirements around oscillations or > the characteristics of the overload, and say something around > the recovery time like: > the overload control mechanism should help predict the time a > system will take to recover based on the characterization of > the overload? > > Jean-Francois. > > > -----Original Message----- > > From: Volker Hilt [mailto:volkerh@bell-labs.com] > > Sent: Wednesday, November 08, 2006 9:18 AM > > To: Cullen Jennings > > Cc: sipping > > Subject: Re: [Sipping] Re: draft-rosenberg-sipping-overload-reqs > > recovery > > > > I think that stability of overload control is an important > requirement. > > We certainly want to avoid building something that starts > to oscillate > > once it reaches overload state. It may be somehow implicit to REQ 1 > > since an unstable system will hardly be able to maintain > the overall > > useful throughput at a high level. > > > > Volker > > > > > > > > Cullen Jennings wrote: > > > Clearly this was a long way from the text for a requirement but, > yes, > > I > > > was proposing that this be added as one of the > requirements. I don't > > > feel strongly about this and if we can't figure out how to express > > this > > > as a requirement that is useful, I can certainly live with not > > adding it. > > > > > > The reason I think it is a requirement is I can easily > imagine that > > the > > > mechanism for doing overload push-back causes the systems > to fail in > > the > > > way I described below (i.e. never recover back to steady state). > > > > > > > > > On Nov 6, 2006, at 11:17 AM, Jonathan Rosenberg wrote: > > > > > >> > > >> > > >> Cullen Jennings wrote: > > >> > > >>> A possible additional requirement.... > > >>> Imagine a system (perhaps a single proxy) that could do > 100cps. It > > >>> is in steady state doing 80cps with very few > retransmission. Then > > >>> for 5 minutes the incoming requests goes to 500cps then drops > > back > > >>> to an incoming call rate of 80cps. The question is, how long > > before > > >>> the system gets back to the state where it if is successfully > > >>> processing all the 80cps? > > >> > > >> As soon as it can. Are you suggesting a requirement here? Seems > > like > > >> this is an implementation thing and wouldn't impact any protocol > > >> mechanisms. > > >> > > >>> I have seen systems that never recover - that is bad. I > think one > > of > > >>> the design goals is that it is at least possible to build to > > systems > > >>> that recover back to steady state relatively quickly after an > > >>> overload impulse. > > >> > > >> Sure; but I'm not sure I see the protocol requirement. > > >> > > >> -Jonathan R. > > >> > > >> > > >> > > >> --Jonathan D. Rosenberg, Ph.D. 600 > Lanidex Plaza > > >> Cisco Fellow Parsippany, NJ > > 07054-2711 > > >> Cisco Systems > > >> jdrosen@cisco.com FAX: (973) 952- > > 5050 > > >> http://www.jdrosen.net PHONE: (973) 952- > > 5000 > > >> http://www.cisco.com > > > > > > _______________________________________________ > > > Sipping mailing list > https://www1.ietf.org/mailman/listinfo/sipping > > > This list is for NEW development of the application of SIP Use > > > sip-implementors@cs.columbia.edu for questions on current sip Use > > > sip@ietf.org for new developments of core SIP > > > > > > _______________________________________________ > > Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping > > This list is for NEW development of the application of SIP Use > > sip-implementors@cs.columbia.edu for questions on current sip Use > > sip@ietf.org for new developments of core SIP > > > > _______________________________________________ > Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use sip-implementors@cs.columbia.edu for questions on current > sip Use sip@ietf.org for new developments of core SIP > _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] draft-rosenberg-sipping-overload-reqs r… Cullen Jennings
- RE: [Sipping] draft-rosenberg-sipping-overload-re… Poretsky, Scott
- [Sipping] Re: draft-rosenberg-sipping-overload-re… Jonathan Rosenberg
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Spencer Dawkins
- [Sipping] Re: draft-rosenberg-sipping-overload-re… Cullen Jennings
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Volker Hilt
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Jean-Francois Mule
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Janet P Gunn
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Michael Hammer (mhammer)
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Michael Hammer (mhammer)
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Albrecht.Schwarz
- [Sipping] SIP Malformed messages SUNIL J. KUMAR
- RE: [Sipping] SIP Malformed messages Geneiatakis Dimitris
- RE: [Sipping] SIP Malformed messages Gaurav Kheterpal
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Jonathan Rosenberg
- [Sipping] proxy in DMZ while B2BUA as an ALG SUNIL J. KUMAR
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Volker Hilt
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Albrecht.Schwarz
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Dolly, Martin C, ALABS
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Widjaja, Indra (Indra)
- RE: [Sipping] Re: draft-rosenberg-sipping-overloa… Albrecht.Schwarz
- Re: [Sipping] Re: draft-rosenberg-sipping-overloa… Cullen Jennings