On Thu, 2008-12-18 at 21:15 +0000, Eduardo Martins wrote: > 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.
True... But it's almost the same thing to respond 202, and then after a few seconds terminate the subscription with a NOTIFY with "Subscription-State: terminated;reason=rejected" as it is to respond 4xx in the first place. (Since a subscriber should be specifying parallel forking.) Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
