A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart Overload Control

Document Type Expired Internet-Draft (individual)
Last updated 2014-08-14 (latest revision 2014-02-10)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


When a large number of clients register with a SIP registrar server at approximately the same time, the server may become overloaded. Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests may have similar effects. Such request avalanches can occur, for example, after a power failure and recovery in a metropolitan area. This document describes how to avoid such overload situations. Under this mechanism, a server estimates an avalanche restart backoff interval during its normal operation and conveys this interval to its clients through a new Restart-Timer header in normal response messages. Once an avalanche restart actually occurs, the clients perform backoff based on the previously received Restart-Timer header value before sending out the first request attempt. Thus, the mechanism spreads all the initial client requests and prevents them from overloading the server.


Charles Shen (charles@cs.columbia.edu)
Henning Schulzrinne (hgs@cs.columbia.edu)
Arata Koike (koike.arata@lab.ntt.co.jp)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)