Dale wrote: > On Tue, 2008-12-09 at 15:39 -0500, Paul Mossman wrote: > > I'm looking at XECS-1971, which is to add Require: eventlist to > > non-ACK non-CANCEL messages sent by sipXrls to Resource List > > subscribers, as per RFC 4662 section 4.1. > > Really, it's only for NOTIFYs that we need to add that. > (Although I don't think the RLS generates any other requests > toward subscribers.)
Yes. I need to add the Require header functionality to SipUserAgent though, so the implementation will be more general (RFC 3261 section 8.2.2.3.) > > I see that Supported: eventlist is also included in these messages. > > Is this necessary? > > > But I do not think it is correct for sipXrls to say that it > supports > > eventlist, since it does not create subscriptions for which it is > > willing to process an eventlist. > > I don't remember all the details of which SipUserAgent is > used for what purposes, but there is one which the RLS uses > when it is the subscriber, and one that it uses when it is > the notifier. But there is one design principle, that > SUBSCRIBEs sent to monitored URIs (phones) are *not* supposed > to have "Suppored: eventlist". This ensures that one cannot > accidentally configure an RLS list that contains a URI that > is itself an RLS list. Yes, you are correct. The new behaviour will apply to the notifier user agent, with no change the user agent that sends SUBSCRIBEs. Thanks. -Paul [EMAIL PROTECTED] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
