> -----Original Message----- > From: Adam Roach [mailto:[EMAIL PROTECTED] > Sent: Monday, October 22, 2007 10:56 AM > To: Robert Sparks > Cc: Robert Sparks; sip; Paul Kyzivat; Stucker, Brian > (RICH1:AR00); Michael Procter; Elwell, John > Subject: Re: [Sip] INFO > > 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 for one am all for doing it the right way. I just don't want to muddy up the usage for NOTIFY if at all possible because it frequently takes people awhile to get 3265 right. Usages and dialogs are two areas that people frequently get confused on so the fewer the use cases we have for NOTIFY processing, the better. I'm just asking that a NOTIFY be processed the same no matter how the subscription itself was created. It sounded like this wasn't going to be the case. Regards, Brian _______________________________________________ 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
