The problem is that without knowing if the uri is a resource list or not, the subscribe request should not considered valid (the 202 response implies it is valid), since the Accept (must support multipart and rlmi) and Supported (must have eventlist option) headers may be invalid. In a server where PS and RLS fucntions are implemented the UA may be targeting only a normal resource where those header values are not required.
-- Eduardo On Thu, Dec 18, 2008 at 8:42 PM, Dale Worley <[email protected]> wrote: > On Wed, 2008-12-17 at 15:35 +0000, Eduardo Martins wrote: > > my understanding of the RLS specs is that we can't return a 202 > > with pending subscription back to the subscriber > > I don't understand -- the 202 response code is designed for the > situation where the SUBSCRIBE has been processed but the notifier does > not yet know whether the subscription is allowed. (See RFC 3265.) In > that case, the notifier initially sends a NOTIFY with > Subscription-State: pending and body that is empty or contains no > specific information. When the notifier determines the subscription is > valid, it sends another NOTIFY with Subscription-State: active, or if it > is not valid, it sends a NOTIFY with Subscription-State: terminated. > > Dale > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
