Definitely, unsolicited NOTIFY can not be substituted for presence event where it would make watcher info. subscription to presence event useless but it makes sense of using it for reg, sip-profile or message waiting.
On Tue, May 20, 2008 at 11:57 AM, Vikram Chhibber <[EMAIL PROTECTED]> wrote: > Hi All, > > I would like to emphasize the need for adapting unsolicited NOTIFY as > a standard. We all are aware of so many commercial applications using > this mechanism. Also, for typical features of presence and > call-processing, user-agents make subscriptions for sip-profile, reg > event, presence/RLS, watcher-info, message waiting indication, > xcap-diff events etc. > > There are overheads on both the network and UA for maintaining the > dialog states for all these subscriptions, excessive SIP messaging and > not to mention the high-availability complexities where a network node > has to mirror the dialog information on its peer. > > There are many optimizations like multi dialog usage (RFC 5057) etc > but these lead to inter-operation issues as their implementation > varies vendor to vendor. > > I would like to ask whether there is an effort to address these issues. > > ~Vikram > _______________________________________________ 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
