Hi, > > > > What we really need to say is that > multipart/alternative may be > > > > used only when we > > > > are using alternative payload types for the same > > information. For > > > > example, text/html and > > > > text/xml or whatever. It would be applicable if one day we > > > > re-created another SDPng for example. > > > > > > The perfect example for that is MESSAGE with text/plain and > > text/html, > > > quite analogous to an email message. > > > > That is sufficient justification to include multipart/alternative. > > Exactly what I had in mind. I was suggesting we replace the > SRTP example in the document with this example.
I think the document should also describe SDP, and if someone thinks alternative doesn't work (or that some other mechanism is far better) with SDP it should be described. Also, we now have a number SDP extensions, related to grouping, alternatives and capabilities, so it would probably somehow be a good idea to collect a description/comparition of them in some document. Regards, Chriser _______________________________________________ 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
