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.
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.
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.
/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
