IETF Logo Mail Archive

[Sipping] draft-rosenberg-sipping-overload-reqs recovery

Cullen Jennings <fluffy@cisco.com> Sat, 04 November 2006 02:24 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgBCU-0007ad-Ka; Fri, 03 Nov 2006 21:24:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgBCS-0007Zu-QO for sipping@ietf.org; Fri, 03 Nov 2006 21:24:00 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GgBCP-0003EQ-Fp for sipping@ietf.org; Fri, 03 Nov 2006 21:24:00 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 03 Nov 2006 18:23:57 -0800
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAJKIS0WrR7PDh2dsb2JhbACMSwEBAQgOKg
X-IronPort-AV: i="4.09,387,1157353200"; d="scan'208"; a="350001285:sNHT25698404"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA42Nu0e031047 for <sipping@ietf.org>; Fri, 3 Nov 2006 18:23:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA42Nuin015093 for <sipping@ietf.org>; Fri, 3 Nov 2006 18:23:56 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Nov 2006 18:23:56 -0800
Received: from [171.69.133.212] ([171.69.133.212]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Nov 2006 18:23:56 -0800
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <250EF171-D4BB-4650-9C14-B7C8815FB7CE@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: sipping <sipping@ietf.org>, Jonathan Rosenberg <jdrosen@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
Date: Fri, 03 Nov 2006 18:23:59 -0800
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 04 Nov 2006 02:23:56.0402 (UTC) FILETIME=[476CDD20:01C6FFB8]
DKIM-Signature: a=rsa-sha1; q=dns; l=645; t=1162607036; x=1163471036; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:Cullen=20Jennings=20<fluffy@cisco.com> |Subject:draft-rosenberg-sipping-overload-reqs=20recovery; X=v=3Dcisco.com=3B=20h=3Dw6rbjCKbBN1PtvIFNF35HLuwXoQ=3D; b=Jh8W4KK/sk+3jXkv+56OdIalKrT1T+Rh14Tq5OBvvzTrIeG+6Qk4B2Yg4xNl1PjUL+afoC4r TXYD5AJ1LBN8BfDuJC5py2Db0YD3RS8IxjGrDt/utVqdGrO6eexgrj+K;
Authentication-Results: sj-dkim-3.cisco.com; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc:
Subject: [Sipping] draft-rosenberg-sipping-overload-reqs recovery
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

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?

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.



_______________________________________________
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

v2.23.0 | Report a Bug | By Email