On May 12, 2008, at 2:12 AM, Juha Heinanen wrote: > Dean Willis writes: > >> The edge proxy and registrar might collude to set a short >> registration >> interval if they don't know the UA supports keepalives and they know >> the UA is one the wrong side of a NAT. > > this has been discussed at least three times already. in my > opinion, it > is UAs responsibility to choose a short reg int if it behind nat and > does not support CRLF keepalives.
I respectfully disagree: the registrar has control of setting the registration refresh under the protocol. UAs might send them more frequently. And they might get kicked off for generating excessive load on the proxy if they do so needlessly, or in other violation of the proxy's policy. > one more think. if there is an edge proxy between UA and registrar, > isn't it the edge proxy that processes the keep param and not the > registrar? Yes, but nothing keeps the edge proxy from communicating with the registrar to help it set up policy. Note also in the current draft the registrar sees the "keep=yes" via parameter even if the edge proxy doesn't take further action to communicate what is happening with keepalive to the registrar. -- Dean _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
