> -----Original Message----- > From: Eric Burger [mailto:[EMAIL PROTECTED] > > > There is no separate subscription or timer. The dialog usage is > > refreshed by INVITE or UPDATE in the conventional manner. Events to be > > exchanged are renegotiated from scratch with every reINVITE or UPDATE. > > So what does the NOTIFY put into expires? I hear hk now: "Just stuff it > with 99999." OK, this now adds another hack into send_event(), "If I am a > real SUBSCRIPTION, return the timer; if I am not, return 99999." Just > upped the complexity by 1.
Au contraire. I explicitly noted these types of issues in my emails as an argument for why it should not create a true Subscription in the 3265 sense of the word, and not use the Notify method. We should just exchange the events we support in the Invite/response, and use the already-available Invite dialog and usage, and the already existent Info method to carry the events. -hadriel _______________________________________________ Sip mailing list https://www1.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
