WebRTC Data channel support for outband
Reported by
puneeth....@gmail.com,
May 29 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: Wanted to know support for https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-12 i.e., outband data channel support and subprotocol supported or planned to support What is the expected behavior? WebRTC data channel support outband i.e,, non-DCEP . SDP based negotiation What went wrong? SDP based outband data channel negotiation not supported and plans for same Did this work before? N/A Does this work in other browsers? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0
,
May 31 2017
,
Jun 20 2017
,
Jul 11 2017
The WebRTC 1.0/JSEP standards don't require supporting this, and we don't have any intention to. However, if you were so inclined, I think you could support this in JS with an additional layer on top of WebRTC, since WebRTC *does* support "out-of-band" data channel negotiation (see: https://w3c.github.io/webrtc-pc/#dom-rtcdatachannelinit-negotiated). |
||||
►
Sign in to add a comment |
||||
Comment 1 by jbanavatu@chromium.org
, May 30 2017Components: Blink>WebRTC
Labels: TE-NeedsTriageHelp