Hi, >>> For *offers and answers* you find the part by looking for the one with >>> Content-Disposition:session. If there is a part with no C-D header then >>> one with a C-T of application/sdp defaults to "session". So its all >>> about C-D. (In theory, application/sdp is just one of the C-Ts that >>> might be used to encode offers and answers.) >> >> I am not sure what you mean by "body part". Is this a problem if we only >> allow a single info-package per message? > >I mean, even with INFO the body may contain more than the info package, >or it may contain something that is not the info package and contain >*no* info package. For instance, it might contain a body that is >referenced via a CID: URI in some header in the message, that serves >some incidental purpose. > >The body could be a multipart/mixed, and one part could contain the info >package, and some other part could contain the info package. > >Thinking that the body must contain only the info package is failing to >remember the lessons we have already learned with INVITE and other messages. > >So no, this has nothing to do with multiple info packages per message. I >have stopped talking about that.
So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)? Example: Content-Type:multipart/mixed Info-Package: foo --boundary foo data --boundary some other (non-info package) data --boundary-- Regards, Christer _______________________________________________ Sip mailing list https://www.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
