You are not likely to run into this for transfer. I'm not aware of any applications that will exercise this use case today, but I expect someone eventually will come up with something (it might look like referring a UA to multiple MSRP connections or some other conference-like mesh, or somebody may eventually try to use REFER to ask the UA to look at several things over HTTP at once). The id= parameter on the Event header in the notify is there to allow you to tell the subscriptions apart (so you can manage those usages independently). The element accepting the REFERs is required to send it in the NOTIFYs of the second and subsequent subscriptions. Again, I haven't seen attempts to use this capability in applications yet - it would not surprise me if there's something there that turns out to be really hard (like figuring out which of those subscriptions goes with which REFER). RjS On Jul 25, 2008, at 1:06 AM, Vavilapalli Srikanth-A19563 wrote:
|
_______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip