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

selectedCandidatePair once stop() has been called #11

Closed
steveanton opened this issue Jun 12, 2018 · 2 comments
Closed

selectedCandidatePair once stop() has been called #11

steveanton opened this issue Jun 12, 2018 · 2 comments
Assignees
Labels
PR needed A pull request is needed.

Comments

@steveanton
Copy link
Collaborator

When stop() is called, should selectedCandidatePair be cleared to null or retained at whatever its last value was?

@aboba
Copy link
Contributor

aboba commented Jun 12, 2018

In ORTC (see: http://draft.ortc.org/#dom-rtcicetransport-getselectedcandidatepair ) it says:

"If there is no selected pair yet, or consent [RFC7675] is lost on the selected pair, NULL is returned."

Based on the above, I'd say that once stop() is called, consent will expire and selectedCandidatePair will be cleared to null.

@aboba aboba added the PR needed A pull request is needed. label Jun 12, 2018
@steveanton
Copy link
Collaborator Author

Since getSelectedCandidatePair is described in WebRTC-PC and affects the WebRTC 1.0 RTCIceTransport, I've opened a spec issue there: w3c/webrtc-pc#1981

Closing in favor of that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR needed A pull request is needed.
Projects
None yet
Development

No branches or pull requests

2 participants