%% You should probably cite draft-shen-soc-avalanche-restart-overload-07 instead of this revision. @techreport{shen-soc-avalanche-restart-overload-05, number = {draft-shen-soc-avalanche-restart-overload-05}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-shen-soc-avalanche-restart-overload/05/}, author = {Charles Shen and Henning Schulzrinne and Arata Koike}, title = {{A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart Overload Control}}, pagetotal = 10, year = 2013, month = dec, day = 1, abstract = {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.}, }