> -----Original Message----- > From: Adam Roach [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 26, 2007 3:53 PM > To: Hadriel Kaplan > Cc: Stucker, Brian (RICH1:AR00); [email protected] > Subject: Re: [Sip] INFO > > On 9/26/07 3:34 PM, Hadriel Kaplan wrote: > > So I want to send you Info relating to a session but the > details about > > what info are in the content-type. Now I agree that > content-type is > > really not the appropriate header for such generically, > specifically > > because it describes the body content, which may be > ambiguous with usage of the body. > > > > Thank you! That's the key point I'm trying to make.
And I agree with your key point then if this is what you were trying to draw out earlier to me. > > > One > > could argue Info is essentially a Notify, except in a subscription > > implicitly created by, and tied to the dialog from, an Invite. > > > > Now you're just *trying* to push my buttons. :) > > There are certain predictable objections that I would raise > to such a characterization; take them as given. Noted. > > The key point here is that NOTIFY will inherently be > associated with an event package, which provides enough > information for the recipient to know what to do with the > body. INFO, lacking such information, is ambiguous. And, as > before, the hardest problem isn't interpreting what is sent > to you; it is indicating what *can* be sent to you. Yes, INFO is different in that respect from NOTIFY. You don't expect a NOTIFY for something you never explicitly sent a request for that scoped it to an event package...except REFER. But the semantics of REFER are such that it's implied. I think the key point being made on the other side is that there's nothing special about an event package. It is an identifier that disambiguates the NOTIFY. In some cases other header values could serve the same purpose (i.e. content-type w/ DTMF). > > /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
