> -----Original Message-----
> From: Christer Holmberg (JO/LMF)
> [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 13, 2007 22:42
> To: Audet, Francois (SC100:3055); Dan Wing; Paul Kyzivat
> Cc: [EMAIL PROTECTED]; [email protected]
> Subject: RE: [Sip] Support for Multipart/MIME
>
> 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.
This document should say that multiple SDPs with multipart/alternative
are NOT
allowed.
It should probably refer to RFC 2046 that explains pretty clearly what
Alternative means, i.e., Multiple version of the SAME information
using different MIME bodies. See 5.1.4/RFC 2046.
E.g., SDP vs SDPv2/NG/whatever-comes-up-next
text/plain, text/html
> 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.
Agreed.
That's probably the job of Flemming's capability negotiation draft in
MMUSIC.
I think he's got some wording on it already.
> 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
