On Oct 14, 2007, at 4:35 PM, Paul Kyzivat wrote:
Christer Holmberg wrote:
I haven't thought about this proposal in detail yet, but we would
also
need to take the the dialog-reuse spec (which proposes NOT to mix
dialog
usages) into consideration. But, if we somehow could bind the
subscription lifetime to the dialog lifetime I think that at least
some
of the issues in that spec would be solved.
The lifetime of a dialog isn't an independent variable - it ends
when the last dialog usage ends.
If you are really talking about implicit *subscriptions*, then you
either must explicitly end them, or else define their *implicit*
end in terms of something that has an explicit endpoint.
I expect that you are talking about something that either shares
the invite dialog usage, or else a distinct dialog usage that
implicitly starts and stops concurrently with the invite dialog usage.
I believe we're talking about something that explicitly shares the
INVITE dialog usage. Once a BYE transaction has been processed, it's
over with. Yeah, you get all the usual dialog-usage termination race
conditions (like BYE overlaps) but that's just the way it is with
dialogs. Heck, that's the way it is with any session-oriented
protocol, even TCP.
--
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
