[MMUSIC] BUNDLE and ZERO PORT VALUE

[Christer Holmberg <[e-mail]>]

Hi,

One of the open issues is the usage of m- lines with port value zero within a BUNDLE group.

As Paul has indicated, RFC 5888 does not currently allow it.

One suggestion has been to update RFC 5888. But, before we go down that path, I think we need to see whether NOT allowing zero port m- lines in BUNDLE groups would work.



So, how would it impact BUNDLE?

Zero port value in answer:

If an m- line in the offer contains a non-zero port value, but the associated m- line in the answer contains a zero port value (read: the answerer rejected the offered media associated with the m- line), the number of m- lines associated with the BUNDLE group would differ in the offer and answer.

As the media is rejected, no matter whether it would be part of a BUNDLE group or not, I can't think of any issues.


Zero port value in offer:

If an m- line in the offer contains a zero port value, the associated m- line in the answer MUST also contain a zero port value.

If the m- line has previously been part of a BUNDLE group, with a non-zero port value, it means that the number of m- lines in the BUNDLE group will be reduced. But, again, as the media is rejected, no matter whether it would be part of a BUNDLE group or not, I can't think of any issues.

Then, if one later wants assign a non-zero value to the m- line, and insert it into a BUNDLE group, the number of m- lines in the BUNDLE group would increase. I don't see any issues as such with that. One question, however, is whether the answerer is allowed to accept the m- line, but reject it being part of a BUNDLE group. But, let's discuss that in a separate thread.


SUGGESTION:

My suggestion is that we do NOT allow m- lines with zero port value in a BUNDLE group. Please indicate whether you are aware of restrictions, or problems, that this would bring, and we will document those.


Regards,

Christer