[MMUSIC] 10 BUNDLE questions

[Justin Uberti <[e-mail]>]

The list below is a set of questions (some marked as OPEN ISSUE already)
regarding the new BUNDLE proposal. If you agree with my suggested answers,
I'm willing to contribute text accordingly.

   1. Can you create a BUNDLE with a single m= line? (assuming yes)
   2. Can you create multiple BUNDLEs? (assuming yes)
   3. When creating an initial offer, how should we deal with the case
   where a "null" port is to be used with trickle ICE (since 6.1:1 indicates
   the ports MUST be different)
   4. From 6.1, list 1 - are conditions 2, 5, 7 really necessary? (MUST use
   same c=, add rtcp-mux, same a=fingerprint)
   5. From 6.1, list 2 - is condition 6 right? Why would we use different
   SDES keys for a single RTP session?
   6. If you start with a m= line with one SDES config (e.g. 32-bit MAC),
   and then BUNDLE with another SDES line with a different (non overlapping)
   SDES config (e.g. 80-bit MAC), what happens? (assume fail)
   7. If the BUNDLE mids in the answer doesn't match the BUNDLE mids in the
   offer, what happens? (assume fail)
   8. If you add a m= line to an existing BUNDLE, can the recipient reject
   that BUNDLEing (assume no)
   9. If m= lines are rejected, should their mids show up in the BUNDLE
   answer? (assume yes?)
      1. If not, how does remote side indicate BUNDLE support if it rejects
      the m= lines that are BUNDLEd?
   10. Is there any way, in a single PeerConnection, to unBUNDLE m= lines
   that were previously BUNDLEd (assume no)