[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simple] SIP multisubscription



Martin.Hynar at tietoenator.com wrote: 
Hi,


I understand that rfc 3265 does not specify what to do with particular event-template. My problem lies in fact that there is no event-package for working with resource-lists (that is the only AUID I'm supporting). The only possibility is to use the sipping-config which introduces some workaround. The subsequent problem is that on one hand it allows "too much liberty" when selecting the target of subscription and on the other hand it does not specify how to handle it. What I am asking is if there is some way how to solve it now without the specification but complying everything stated in e.g. rfc3261, rfc3265.


Imagine the fundamental problem,

1. user U_1 has three documents with resource-lists AUID
2. another user U_2 subscribes them in one SUBECRIBE request
   ...
   Event: sip-profile;app-id=resource-lists
   ...


This results in *one* subscription.

3. user U_1 deletes one of his documents 

This changes the state of the resource that has been subscribed to.

4. user U_2 is notified with NOTIFY request
   ...
   Event: sip-profile;app-id=resource-lists;document=doc1
   Subscription-State: terminated;reason=noresource

If there were multiple documents subscribed to, then why would this cause the subscription to be terminated? I guess the server can do so if it wants, but it seems like the wrong thing to do. After all, the subscriber could reissue the same subscription request and it would be valid, so it is not the case that the resource is gone. It is only *part* of the resource that is gone.

Questions:
Shall now the user U_2 consider its dialogue as terminated or not,


Given that it received the above response, then yes.

there are still some documents that could be subscribed in this dialogue.
Shall the server consider the dialogue terminated?

I think not. The "resource" that is being subscribed to in this case is determined by the R-URI, the event package, and the event package parameters. If that happened to correspond to a collection of documents, then it is the collection of documents that is the resource.

	Paul

_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple