Howdy, Inline comments, but also: this seems like going down the road of complexity again. One of the reasons I think people use INFO-dtmf instead of KPML is it's so darn simple/easy. If we want people to change their implementations to support negotiation and explicit content context indication, it should be as trivial as possible, IMHO. No bells, no whistles.
> -----Original Message----- > From: Paul Kyzivat [mailto:[EMAIL PROTECTED] > > Just as there are INVITEs that don't offer SDP (because they don't know > what to offer) there is a need for INVITEs that don't offer events. An > INVITE that contains no Exchange-Events header is not offering any. In > that case the offer of events is in a reliable response and the final > answer about what events will be used is in the ACK or PRACK. (To > indicate that you don't desire to exchange any events, include a > Exchange-Events header with no events listed.) Why do this? What use case is there for not saying what you can do in the Invite? Offer-less Invites cause enough problems. We shouldn't repeat them. > There is a problem if the event type may (or must) use a body in the > subscribe. The kpml package falls into this category. :-( > The body could simply be included in the message carrying the > Exchange-Events header. But that potentially means a bunch of body parts > with the recipient having the problem of deciding how each part should > be matched to a particular event type. That is more or less the same > problem we are trying to solve here, so its not good. Also, it would > seem that every time you send a reinvite or update you might have to > send these again. Ya that's bad. If someone wants to define an info-event that needs such things, they can define it to exchange it in an INFO when they do. -hadriel _______________________________________________ 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
