Especially if we mandate support for multipart MIME in modern Info-package.
On Aug11 2008 20:15 , "Eric Burger" <[EMAIL PROTECTED]> wrote: > But on the serious side, my guess is the chance of a UA that > understands "modern" Info-Packages but does not understand multipart/* > will approach zero. Especially if Info-Packages mandates support of > multipart. > > On Aug 11, 2008, at 10:28 PM, Dean Willis wrote: > >> >> On Aug 11, 2008, at 9:27 PM, Eric Burger wrote: >> >>> What is at Steak here [sic] is not whether an Info-Package can be a >>> multipart MIME type. That (almost, but clearly I guess I need to >>> include such text) goes without saying (but will in the future). >>> >>> The question is if I will eat Steak, and I will eat Lobster, is it >>> OK for me to receive an INFO that has a multipart/mixed with one >>> part being Steak and another (theoretically unrelated) part being >>> Lobster? >> >> Clearly, any client that doesn't understand multipart will be left >> asking "Where's the beef?" >> >> -- >> Deab > > _______________________________________________ > 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 _______________________________________________ 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
