Hi, I don't think we should try to specify in detail when one is allowed to use alternative, and one is not allowed, but instead refer to other specifications for specific content types, and say that an implementation shall reject the message if alternative is used in a wrong way (based on those other specs).
I think our main focus should be to describe the expected protocol level behavior of a SIP entity when receiving alternative. Do we have the same issue with mixed, btw? I assume there COULD be cases where the same content type can be used with mixed? Regards, Christer > -----Original Message----- > From: Dan Wing [mailto:[EMAIL PROTECTED] > Sent: 29. toukokuuta 2007 22:38 > To: 'Paul Kyzivat'; Gonzalo Camarillo (JO/LMF) > Cc: 'Francois Audet'; [email protected]; Christer Holmberg (JO/LMF) > Subject: RE: [Sip] Support for Multipart/MIME > > Paul Kyzivat wrote: > ... > > > OPEN ISSUE 2: we know that we do not want two SDPs in a > > > 'multipart/ > > > alternative', but is this valid generally with any > content type? > > > Would it be possible to provide two alternative body > parts using > > > the > > > same format and, thus, the same content type but in, say, > > > different > > > languages? > > > > Its my understanding that the distinction is based on which can be > > understood, relative to Content-Type. It isn't apparent to me that > > making this decision based on other attributes is valid. > For one thing > > the parts are supposed to be ordered by increasing > richness. If they > > differed by language this wouldn't be true. > > Multipart/alternative is the best we have, though. And who > is to say that image/jpeg is richer than image/gif, or that > english is richer than latin? > > Anyway, the following RFCs standardize the use of > Content-Language and refer to using multipart/alternative > when providing support for multiple > languages: > > http://tools.ietf.org/html/rfc3282 > http://tools.ietf.org/html/rfc3066 > > -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
