Re: [dispatch] draft-shen-soc-avalanche-restart-overload

[Charles Shen <[e-mail]>]

Dear all:

As advised by Richard Barnes, I am writing to seek opinion from you about
this draft:

http://datatracker.ietf.org/doc/draft-shen-soc-avalanche-restart-overload/
A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart
Overload Control

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.

The draft has been presented and discussed in IETF meetings since 2010, and
generated interest among the community:

https://encrypted.google.com/search?as_q=draft-shen-soc-avalanche-restart-overload&as_sitesearch=www.ietf.org%2Fmail-archive%2Fweb%2F

I am looking for your kind opinion on what should be the appropriate next
step for this document:

-- Should this draft be dispatched to SOC (and their charter amended)?
-- Should this draft be processed as AD-sponsored?
-- Should this draft be killed (if it is harmful)?

Thank you very much.

Charles