Re: [rtcweb] [MMUSIC] Default proto transport in JSEP

[Roman Shpount <[e-mail]>]

Hi Ted,

On Wed, Nov 28, 2018 at 2:01 PM Ted Hardie <[e-mail]> wrote:

> The current pull request resolves the 5.1.2 vs. 5.2.2 ambiguity in line
> with the discussion here:
>
> https://github.com/rtcweb-wg/jsep/issues/394
>
> and then here:
>
> https://mailarchive.ietf.org/arch/msg/mmusic/gR-dYY1GzN3fIA_XlHiX-bB6nLM
>
> I understand from your comments on
> https://github.com/rtcweb-wg/jsep/issues/854 that you disagreed with that
> being the final consensus, and it has since been discussed on the list as
> Justin suggested in that issue.
>
> At the moment I continue to see only you objecting to the combination of
> the current pull and an update to ice-sip-sdp.   Since ice-sip-sdp is in
> MMUSIC, not RTCWEB, it's not up to the RTCWEB chairs to call the final
> consensus here, but I believe my previous statement on the preference for
> RTCWEB remains true.
>
>>
>>
I think at this point it is up to the chairs to decide. Just please keep in
mind that updating ice-sip-sdp and sctp-sdp to be inline with what JSEP is
proposing would be difficult since this will cause backward
compatibility issues with RFC 5245 outside of RTCWEB.

Also, proposed change raises a new issue, which is what values should be
set in c= and m= lines when protocol in m= line does not match the default
candidate.

Regards,
_____________
Roman Shpount