On 10/23/07 11:32 AM, Dean Willis wrote:
On Oct 22, 2007, at 10:55 AM, Adam Roach wrote:
Allow me to clarify my position further here.
Robert is right: SUBSCRIBE/NOTIFY is the correct way to address these
issues. If I had my druthers, we'd be using 3265 straight-up for
these applications. My prior message was based on the assumption that
we'd lost the "do this the right way" battle. Taken as a given, the
options I outlined in my earlier note are an attempt at damage control.
I believe that the empirical evidence of a heck of a lot of
implementations indicates that there are use cases where people would
rather not have a full-blown event dialog in parallel to an INVITE
dialog for very good reasons of capacity and complexity, but still
need event passing. The original use of INFO for midcall telephony
signaling is just one example of this.
Right. So, dust off your old INFO package draft and re-issue it. It
appears to address the issue you describe while really only being
objectionable under some relatively fringe objections (mine included).
/a
_______________________________________________
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
