As per RFC 3265 (SIP-Specific Event Notification), NOTIFY sent in immediate response to a SUBSCRIBE contains full state information. Furthermore, if the SUBSCRIBE is for a Resource List, (RFC 4662), this NOTIFY contains full state information for the Resource List with RLMI and state information. Due to this, the size of NOTIFY request may become very large. The RLS may break this large NOTIFY into number of partial NOTIFY requests. In any case, there is always a lot of processing at the RLS end.
Do we have a mechanism by which the watcher can tell the RLS whether a SIP SUBSCRIBE refresh is for querying the full state or just to refresh the subscription duration? We do have distinguish PUBLISH refresh and PUBLISH update. Thanks in advance. ~Vikram _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
