> >Unless there is another case that it's useful for SIP, I > >think it could only harm interoperability. > > Like I said, it may be used for transporting ISUP information. Maybe > Francois has more information?
Implementations may well be doing multipart/mixed and including only one bodypart. I completely agree that might be happening. > Also, if a client is going to support multipart anyway, I > don't see how it would harm interoperability. By doing that, you are teasing fate, and you aren't "being conservative in what you send". Afterall, it's the receiver (not the sender) of the MIME that may have difficulties. > I would be very surprised if a client > supports MIME with multiple bodies, but not with a single body... Yep, but it isn't the client that I'm so worried about. I expect if you sent a multipart containing one part (application/sdp), you would find disasterous interoperability. -d _______________________________________________ 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
