I agree with Dan. I don't understand the use case in SIP of sending a Multipart with only one body.
The mail example makes sense for really dumb implementations that don't support MIME whatsoever, but for SIP, there is no such thing since MIME has been in SIP since day one. > -----Original Message----- > From: Dan Wing [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 31, 2007 10:38 > To: 'Christer Holmberg (JO/LMF)'; [email protected] > Cc: 'Gonzalo Camarillo (JO/LMF)'; Audet, Francois (SC100:3055) > Subject: RE: [Sip] MIME: MIME when only one body type > > > > >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
