On 7/26/07 8:59 AM, Dean Willis wrote:
Well, personally I'm in the "reuseable primitives" camp, and I believe you are too (as 3265 is a shining example of this approach). But other people have very different beliefs.
Actually, if I knew then what I knew now, I'd probably have proposed doing things completely differently. I have come to believe that a far cleaner approach would have been to use INVITE to set up a stream of state change notifications -- it would have prevented this "multiple usages in a dialog" mess; it would have prevented the bizarre forking SUBSCRIBE problem; it would have made unsolicited NOTIFYs impossible... the whole setup would have been much cleaner.
And, as we all know by now, every time you send an unsolicited NOTIFY, the terrorists win.
/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
