Right, but they're doing it for reg-events and presence, after the
Registration. During an avalanche, for example, they're implicitly throttled
by the effective registration rates. This config framework is reversing it,
having subscriptions before the registrations. I'm not saying it's not
do-able or won't work, I'm just saying we don't know. (and I'm saying it's
not free, and some folks won't think it's worth the cost)
Avalanche (restart) has its own set of problems - including overwhelming either
the HTTP server, SSP or registrar. (In a draft, we've made proposals how to
address this in some cases, as long as the UA can detect that it is likely part
of an avalanche.) As we've seen from the SIP overload discussion, you can't
rely on the "natural" throttling of the server to nicely space out requests -
the whole thing is much more likely to collapse in a heap, so that no useful
work gets done. This affects registration, subscription and retrieval more or
less equally.
Henning
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf