t;>>> The topic is discussed within draft-shen-soc-avalanche-
> restart-overload;
> >>>> however I don't recall why the draft didn't progress further within
> >>>> soc or
> >>>> dispatch.
> >>>>
> >>>&
further within
>>>> soc or
>>>> dispatch.
>>>>
>>>> -Original Message-
>>>>> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
>>>>> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
>
> [mailto:sip- <mailto:sip->
>> implementors-boun...@lists.cs.columbia.edu
>> <mailto:implementors-boun...@lists.cs.columbia.edu>] On
>> Behalf Of Paul Kyzivat
>> Sent: Wednesday,
Sip-implementors@lists.cs.columbia.edu
<mailto:Sip-implementors@lists.cs.columbia.edu>
Subject: [Sip-implementors] backoff algorithms to
prevent registration
storms?
Strategies for preventing registration stor
;>>> 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.edu
>>
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
0: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., after a major power
outage and recovery) have been discussed from time to time.
Can anyone point me to specific documentation
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 failing that I'll be happy
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? Ideally a
sp
; 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.edu
> Subject: [Sip-implementors] backoff algorithms to prevent registration
> storms?
>
> Strategies for preventing registration storm
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 point me to specific docum
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 em
12 matches
Mail list logo
