Paul Kyzivat wrote:
I'm clearly in the minority here, in preferring NOTIFY over INFO. (Minority of one?)
It's ridiculously rare that I disagree with you, Paul, but I'm afraid I'm going to have to weigh in on the "please don't use NOTIFY" camp. If you go back and read Sumit's message of a few minutes ago, you'll see that proper usage of NOTIFY is a matter is extreme confusion. What you propose will muddy the waters enough that I fear they'll change from "difficult to navigate" to "opaque and impossible to traverse at all."
I also agree that the name of the method is secondary to getting the functionality right. So I am fine with leaving the decision about the method until everything else is worked out.
I completely agree here. In fact, my top preference would be to define a new method for this thing under discussion (paired with a deprecation of the much-abused INFO); with my second choice being a package-based fixup of INFO. Re-using NOTIFY would come in dead last -- by which I mean far behind "let's re-purpose ACK for this new meaning."
So, I think the next question is whether there should be a single event package definition mechanism for this new approach and for the 3265 type of events, or if these should be entirely disjoint. I realize existing event package definitions won't be applicable without at least some tweaks, and not all event types are suitable for both mechanisms. But I do think there are event types that are suitable for both mechanisms (e.g. dtmf and dialog) and it would be better if we didn't require independent definitions for them in both contexts.
I think the similarities are superficial at best. Re-use of the MIME type between these constructs would definitely be useful -- but I can't see what you gain by attempting to re-use more than that. /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
