WebRTC Standards & Implementation Q&A - All You Wanted to Know About W3C TPAC & WHATWG Streams with RTCDataChannel
1 like284 views
The document is a summary of a webinar discussing WebRTC standards, including updates on specifications and use cases presented at TPAC 2018. Key topics include planned developments for the WebRTC 1.0 specification, enhancements in data channel interactions, and the adoption of scalable video coding extensions. The document also addresses various decisions made regarding existing issues, testing protocols, and the push for end-to-end encryption in media over QUIC.
![WebRTC TPAC 2018 Decisions 1/2. Questions?
mediacapture-* Decided
* Fullscreen is info, not normative language
* Spec for constraints will be merged
* We will not allow URL white/blacklists in screenshare
* Propose removing the “surface type” constraint
* Remove MUST NOT on change sources
* Move getDisplayMedia to mediaDevices
* Not decided
* Exclude own audio - maybe “echoCancellation”?
webrtc-pc
* Stop saying anything about track.id mapping
* Rename transport.transport to transport.iceTransport
* Set [[direction]] when SRD(answer)
* Clarifications to codec parameters accepted
* SetCodecPreferences remains on transceiver. Orphis to write tests.
* Use order in answer as preference
* Make codecPayloadType read-only (may be reconsidered)
Non-decisions:
* SelectedCandidatePair needs further work (do candidates go away?)
* codecPayloadType in addTransceiver: further discussion (hbos/aboba)](https://image.slidesharecdn.com/webrtcstandardslivesession29-181029185413/85/WebRTC-Standards-Implementation-Q-A-All-You-Wanted-to-Know-About-W3C-TPAC-WHATWG-Streams-with-RTCDataChannel-7-320.jpg)
WebRTC Standards & Implementation Q&A - All You Wanted to Know About W3C TPAC & WHATWG Streams with RTCDataChannel
- 1. WebRTC Standards Webinar & Q&A Amir Zmora TheNewDialTone Jan-Ivar Bruaroey Mozilla
- 2. Watch video recording of this session http://ccst.io/e/webrtcstandards29
- 3. Session sponsored by WebRTC.ventures is a custom design and development shop dedicated to building WebRTC based applications for web and mobile. We have built end-to-end broadcast solutions for events and entertainment clients, telehealth solutions for multiple clients, live support tools, as well as communication tools for a variety of other applications. WebRTC.ventures is a recognized development partner of TokBox and has also built native WebRTC solutions
- 4. We use CrowdCast….It’s WebRTC
- 5. All You Wanted to Know About W3C TPAC & WHATWG Streams with RTCDataChannel
- 6. WebRTC TPAC 2018 Agenda. Questions? • Existing github issues: getDisplayMedia, setSinkId, stats, webrtc- pc. • WPT & Kite testing, Simulcast Playground testing maybe in wpt • WebRTC 1.0 & a few extension specs ◦ Next Steps toward bringing WebRTC-PC to PR (1.0) ◦ WebRTC-ICE extension ◦ Data Channel and WHATWG Streams • WebRTC NV • NV use cases https://w3c.github.io/webrtc-nv-use-cases/ (any of these of interest to you?) • Scalable Video Coding Extension for WebRTC • Access to Raw Media • QUIC and WHATWG Streams • Second Screen WG • Workers and Worklets • End-to-End Encryption Media over QUIC
- 7. WebRTC TPAC 2018 Decisions 1/2. Questions? mediacapture-* Decided * Fullscreen is info, not normative language * Spec for constraints will be merged * We will not allow URL white/blacklists in screenshare * Propose removing the “surface type” constraint * Remove MUST NOT on change sources * Move getDisplayMedia to mediaDevices * Not decided * Exclude own audio - maybe “echoCancellation”? webrtc-pc * Stop saying anything about track.id mapping * Rename transport.transport to transport.iceTransport * Set [[direction]] when SRD(answer) * Clarifications to codec parameters accepted * SetCodecPreferences remains on transceiver. Orphis to write tests. * Use order in answer as preference * Make codecPayloadType read-only (may be reconsidered) Non-decisions: * SelectedCandidatePair needs further work (do candidates go away?) * codecPayloadType in addTransceiver: further discussion (hbos/aboba)
- 8. WebRTC TPAC 2018 Decisions 1/2. Questions? WPT * We will have a regular WPT review meeting * Chairs, editors, Youenn and Karthik have volunteered * We will create per-spec WPT directories * We will aim for a simulcast VI in January * We will aim for a hackathon in March (IETF) use-cases * Adopt document as WG document webrtc-ice * We can change iceCandidatePair to interface * Peter will consult with CDN folks on forking * We will use NetworkInformation to represent network information (not define our own type) svc * We will adopt this document now. (To be verified on mailing list.) audio: * Consult with WebAudio WG * Consult with ML CG about what they need
- 9. WebRTC TPAC 2018 Decisions 2/2. Questions? stream Decision: New APIs need to be Streams-based Non-decision: either adopt stream-messages or need more info Decision: Need advice from Streams folks about how to get processing off the main thread in the best way. <AI: Peter> datachannel We will add an “onclosing” event. stats * STUN server stats acceptable. * Add .mid to senders and receivers. * Add streamIdentfiers to senders, obsolete stream stats object * Stats stay around except when ended (Jan-Ivar to write PR) * Do not remove “track” stats at this time. It’s not mandatory. * Expose IP addresses only if and as seen in addCandidate() * Copy size stats to outbound-rtp. Remove on sender. Discuss details on PR. No consensus: * Leave networkType in the spec or take it out.
- 10. WebRTC TPAC 2018 Decisions 2/2. Questions? Workers We wish to pursue Option 2 - Datachannel in service workers based on webrtc-ice. Youenn offers to specify this when there’s developer interest. This work has lower priority than WebRTC 1.0 and webrtc-ice. E2EE The WG adopts the E2E use case where we trust the application, but not the relay. (to be verified on the list) The WG is still considering the generic “access to encoded data” use case. The WG recommends basing API on TransformStreams QUIC/BYOT The WG will ask the list if we should adopt WEBRTC-QUIC API The WG encourages turning the “streams-based” slideware into a proposal. It doesn’t take a position on adoption yet.
- 11. TPAC WebRTC Monday slides bit.ly/2JmO5IK TPAC WebRTC Tuesday slides bit.ly/2EQGO5E RTCDataChannel w/WHATWG streams presentation: bit.ly/2COcC8G
- 12. ?
- 14. WebRTC Standards Webinar & Q&A Amir Zmora TheNewDialTone Jan-Ivar Bruaroey Mozilla