inline
Dean Willis wrote:
On Oct 16, 2007, at 6:08 PM, Paul Kyzivat wrote:
The "bundled subscriptions" need to be negotiated in both directions.
That means something like:
INVITE must contain:
- these are the events I am willing to send
- these are the events I desire to receive
Do we need that first line ? Or do we just need "These are the events
I'm willing to receive. If I get them, great. If I don't, well, I don't
care, I'll assume that sending them wasn't important to you."
I think the first line is needed, so that the UAS will know whether it
will be getting what it wants this way. It needs to know that so it
doesn't fall back to "plan B" - generating an explicit subscription.
response must contain:
- these are the events I will send (subset from invite)
Same here. I don't think the receiver needs to know what events will be
sent. They already know that any events that will be sent will be a
subset of the events they've said they're ready to handle.
Same answer here. If I want DTMF, I might prefer to get it this way, but
if that doesn't work out I will then probably send an explicit
subscription for it.
Paul
- these are the events you should send (subset from invite)
Let's take for example DTMF. If you tell me you can receive DTMF events,
I might send you some. If you don't, I won't send you any. If you tell
me you can receive DTMF events and I don't send any, do you care whether
it's because I don't know how or because I don't have any to send you?
Is there a use case for turning this into a full bidirectional
offer-answer? If so, it's starting to sound a lot more like an
event-media session (described in SDP and negotiated by offer-answer)
than what I'm thinking would be appropriate for INVITE-bounded
notification. Or maybe its should be a pair of SUBSCRIBE-bounded
opposing dialogs.
--
Dean
_______________________________________________
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
_______________________________________________
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
