Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSEP/WebRTC mismatch on empty remote MID #698

Closed
burnburn opened this Issue Jun 9, 2016 · 3 comments

Comments

Projects
None yet
5 participants
@burnburn
Copy link
Contributor

burnburn commented Jun 9, 2016

In the description for the mid attribute of RTCRtpTransceiver it says "If there is no MID value in the remote SDP, and no MID value was previously assigned, a random value will be created for the mid as described in [JSEP] (section 3.5.2.1.) when the remote SDP is set".
The text in that section of JSEP (https://rtcweb-wg.github.io/jsep/#rfc.section.3.5.2.1) doesn't talk about assignment of a random value.

@stefhak

This comment has been minimized.

Copy link
Contributor

stefhak commented Jun 9, 2016

Related to #578

@adam-be

This comment has been minimized.

Copy link
Member

adam-be commented Sep 15, 2016

I can't seem to find any text in JSEP about generating an mid. I did however find the text below in the section about generating an initial answer.

Each m= section MUST include the following:

  • If and only if present in the offer, an "a=mid" line, as specified in [RFC5888], Section 9.1. The "mid" > value MUST match that specified in the offer.

I'll bring this up in JSEP

@alvestrand

This comment has been minimized.

Copy link
Contributor

alvestrand commented Oct 6, 2016

Not yet linked to a released JSEP's section number. Leaving open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.