Re: Issue #27: Allow RTP attributes in non-media m= sections

On Thu, Feb 16, 2017 at 9:07 AM, Christer Holmberg <
[email protected]> wrote:

> Hi,
>
>
>
> *>*See:
>
> >https://github.com/cdh4u/draft-sdp-bundle/issues/27
>
> >https://github.com/rtcweb-wg/jsep/issues/528
>
> >
>
> >The basic issue is that it's possible to have a situation where you have
> both
>
> >media and data m= sections but the BUNDLE tag is associated with the data
>
> >m= section and now you need to put the TRANSPORT and IDENTICAL
>
> >attributes somewhere. The JSEP editors discussed this and came to the
>
> >conclusion that it should go with the BUNDLE tag (i.e., in the data m=
> section)
>
> >and that BUNDLE should forbid this, but it requires a change to BUNDLE.
>
>
>
> Did you mean to say that BUNDLE should NOT forbid this?
>
>
>
> Based on your GitHub discussion, my understanding is that you want to
> allow to include RTP-specific parameters (‘rtcp-mux’, ‘rtcp’,
> ‘rtcp-mux-only’ attributes etc) in the data m= section.
>

Yes/


>
>
> To repeat what I said on GitHub:
>
>
>
> This has been discussed in the past, and the outcome has been to now allow
> RTP-specific parameters in non-RTP m= sections.
>

Do you mean "not" rather than now?

-Ekr


>
>
> A solution would be to simply change the bundle tag when the RTP m=
> sections are added.
>
>
>
> …OR, we change the mux category for the RTP-specific parameters. But, that
> of course means they have to be added to every RTP m= section.
>
>
>
> Regards,
>
>
>
> Christer
>

_______________________________________________
mmusic mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mmusic