This depends on the client logic - if the user intends to re-register and revalidate itself with the network (by supplying fresh credentials etc). If the client logic is written in such a way that this happens on receiving a NIDR (nw initiated de-reg), he can still keep keep-alives active. This will save a round-trip in creating fresh bindings etc..
-----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Naarumanchi Kaushik Sent: Wednesday, August 05, 2009 6:26 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Reg. SIP Outbound Draft. Hi All, As per the SIP Outbound draft http://tools.ietf.org/html/draft-ietf-sip-outbound-20, after a succesfull registration we should keep-alive the public binding. And stop the keep-alive when user deregisters. Should we stop the keep-alives even when network deregisters him?(as in case of NOTIFY to reg event package having the registration state as "terminated" and event as "deactivated" or "rejected") Pls Clarify. Regards, N.V.S.Kaushik. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
