From: [EMAIL PROTECTED] These issues seem to be all related. E-mail Mime can make do with Content-Type because e-mail's sole function is to present information to the user. The only information needed is "What is this?" because "What should I do with this?" is constant.
In SIP, we have the Content-Disposition, with the defined values "session", "render", "alert", and "icon". This answers the question "What should I do with this?", which is independent of "What is this?". We've been quite sloppy about this issue because for most methods "What should I do with this?" is strongly implied by the method or the context or the Content-Type. But with INFO, unless there is a tightly constrained context from some non-SIP feature, there is complete decoupling between "What is this?" and "What should I do with this?". That is, any body part needs a Content-Disposition that identifies what should be done with the information (= what application the information should be delivered to). But we have no method for negotiating what Content-Dispositions are supported by a given SIP UA. So of course it doesn't work well. Dale _______________________________________________ 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 _______________________________________________ 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
