[MMUSIC] DECISION: Offerer assigning address:port to multiple m- lines before Answerer has selected that address:port as BUNDLE address?

[Christer Holmberg <[e-mail]>]

Hi,

BUNDLE currently specifies that an Offerer is not allowed to assign an address:port to multiple m- lines before that address:port has been selected as BUNDLE address by the Answerer.

Paul indicated that such rule is ineffective, as it always requires two O/A transactions (one for the negotiation, and another one for the sync) in order to negotiate/re-negotiate a BUNDLE address.

Instead, Paul suggested that an Offerer should be allowed to assign a new address:port to multiple m- lines before the Answerer has selected that address:port as a BUNDLE address.

Paul also suggested that an Offerer should be allowed to do this before the Answerer has sent an SDP Answer, indicating support of BUNDLE.

Q5: Within a SIP session, once both endpoints have indicated support of BUNDLE, do we allow an Offerer to assign an address:port to multiple m- lines, before the Answerer has selected that address:port as a BUNDLE address?

Q6: If Q5, do we allow an Offerer to assign an address:port to multiple m- lines before the Answerer has, within the SIP session, indicated that it supports BUNDLE? A typical example would be assigning an address:port to multiple m- lines already in the initial SDP Offer for a SIP session.

Regards,

Christer