Re: [Sip-implementors] backoff algorithms to prevent registration storms?

te wrote: > >>>> > >>>> Hi Paul, > >>>> > >>>> The topic is discussed within draft-shen-soc-avalanche- > restart-overload; > >>>> however I don't recall why the draft didn't progress further within > >>>> s

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

why the draft didn't progress further within >>>> soc or >>>> dispatch. >>>> >>>> -Original Message- >>>>> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- >>>>> implementors-boun...@lists.cs.

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

;mailto:sip-implementors-boun...@lists.cs.columbia.edu> >> [mailto:sip- <mailto:sip-> >> implementors-boun...@lists.cs.columbia.edu >> <mailto:implementors-boun...@lists.cs.columbia.edu>] On >> B

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

To: Sip-implementors@lists.cs.columbia.edu <mailto:Sip-implementors@lists.cs.columbia.edu> Subject: [Sip-implementors] backoff algorithms to prevent registration storms? Strategies for

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

al Message- >>>> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- >>>> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat >>>> Sent: Wednesday, August 10, 2016 10:08 AM >>>> To: Sip-implementors@lists.cs.columbia.ed

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

On Behalf Of Paul Kyzivat > Sent: Wednesday, August 10, 2016 11:01 AM > To: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] backoff algorithms to prevent registration > storms? > > I refreshed my memory on that draft. It proposes a new header field for the

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] backoff algorithms to prevent registration storms? Strategies for preventing registration storms (e.g., after a major power outage and recovery) have been discussed from time to time. Can anyone point me to specific documentation of such schemes

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

Paul Kyzivat writes: > Strategies for preventing registration storms (e.g., after a major power > outage and recovery) have been discussed from time to time. > > Can anyone point me to specific documentation of such schemes? Ideally a > spec that can be referenced, but

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

Subject: [Sip-implementors] backoff algorithms to prevent registration storms? Strategies for preventing registration storms (e.g., after a major power outage and recovery) have been discussed from time to time. Can anyone point me to specific documentation of such schemes? Ideally a spec that can

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

tors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat > Sent: Wednesday, August 10, 2016 10:08 AM > To: Sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] backoff algorithms to prevent registration > storms? > > Strategies for preventing registration storms (e.g., a

Re: [Sip-implementors] backoff algorithms to prevent registration storms?

https://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-overload-01 2016-08-10 17:07 GMT+03:00 Paul Kyzivat : > Strategies for preventing registration storms (e.g., after a major power > outage and recovery) have been discussed from time to time. > > Can anyone

[Sip-implementors] backoff algorithms to prevent registration storms?

Strategies for preventing registration storms (e.g., after a major power outage and recovery) have been discussed from time to time. Can anyone point me to specific documentation of such schemes? Ideally a spec that can be referenced, but failing that I'll be happy with pointers to thorough