Hi Qian, And sorry for a late answer to your comment. I have been on vacation enjoying the beautiful Finnish summer. ;)
ext Qian Sun wrote: > Hi, I am not sure whether the following description in this draft is > enough for the usage of Entity-tags with filtering. > > "5.1. Generating Entity-tags The views might correspond to different > groups of users that have varying levels of access rights to the > resource state, or to subscribers that have modified their > subscription using event notification filtering [11]." > > My consideration is: If a subscriber has a subscription with filter > F1, the current corresponding entity-tag is E1. Then the same > subscriber MUST NOT send SUBSCRIBE with a new filter F2 and the > entity-tag E1 in the conditional header field. i.e., if a subscriber > changes filter for an event state, the Suppress-XXX-If-Match should > not be used. The client of subscriber has to record the last filter > for event state and compare filters. If I understand your concern correctly, the problem is with filtering and not with subnot-etags. I think a subscription that installs a filter, or disables/removes it could effectively be an action that itself changes the event state, and causes an if-match condition to fail. But this all depends on the actual implementation of the filtering system. In other words, this seems like an implementation detail of the filtering system. At the moment, I am not aware of any existing filtering implementations, so I'm reluctant to adding any specific text to the draft either. If this becomes a problem, we can always write an update to the filtering specifications. Cheers, Aki _______________________________________________ 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
