I do not think one can say what the Content-Disposition of a multipart/* body part should be. From RFC 2183:
If a Content-Disposition header is used on a multipart body part, it applies to the multipart as a whole, not the individual subparts. The disposition types of the subparts do not need to be consulted until the multipart itself is presented. When the multipart is displayed, then the dispositions of the subparts should be respected. We already have a compatible-with-MIME solution. Mark the Content-Disposition of the multipart/* as render, session, or inline with the needed handling parameter, and have the Content-Disposition of the sub-parts be whatever they really need to be (if not render). The logic is simply to say what you mean. It really is just a suggestion. If we are talking about a multipart/alternative describing sessions, then the Content-Disposition should be session. Of course, you could have Content-Disposition be foobar (or, better yet, inline), so long as (1) the UAS does not barf and (2) the real Content-Dispositions are present on all of the sub-parts. Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ 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
