I wonder how implementations understand the following from RFC 3265: 3.1.6.2. Confirmation of Subscription Creation/Refreshing
Upon successfully accepting or refreshing a subscription, notifiers MUST send a NOTIFY message immediately to communicate the current resource state to the subscriber. This NOTIFY message is sent on the same dialog as created by the SUBSCRIBE response. If the resource has no meaningful state at the time that the SUBSCRIBE message is processed, this NOTIFY message MAY contain an empty or neutral body. See section 3.2.2. for further details on NOTIFY message generation. What is the definition of *immediately* here? Will implementations be broken if the server will wait with the NOTIFY or subscribe refreshes? The redundant refreshes that are required by RFC 3265 can create a serious degradation in the performance of any SIP presence servers... --Avshalom _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
