Tracking Issue - WebRTC direct in Node.js

[2color]

Background

WebRTC-direct is currently only supported in browsers as mentioned in package.

This is a tracking issue for adding support for WebRTC-direct in Node.js, which would allow browsers to dial Node.js directly (without circuit relay and signalling) without needing for a TLS certificate as in the case of WebSockets.

Dependencies

This require changes to both https://github.com/murat-dogan/node-datachannel and https://github.com/paullouisageneau/libdatachannel to allow SDP Munging.

Related PRs/issues:

Tasks

Beta Give feedback

1. Add support for setting ICE ufrag and pwd paullouisageneau/libjuice#243
   +0
2. Remove checking remote description has different ICE credentials paullouisageneau/libdatachannel#1172
   +0
3. Allow overriding ICE ufrag and pwd fields paullouisageneau/libdatachannel#1201
   +0
4. feat: update current remote description with fingerprint paullouisageneau/libdatachannel#1204
   +0
5. feat: support current remote description murat-dogan/node-datachannel#257
   +0
6. feat: support setting ICE ufrag and pwd, disabling fingerprint validation and specifying certificates murat-dogan/node-datachannel#256
   +0
7. WebRTC-Direct ufrag/STUN username field not prefixed with libp2p+webrtc+v1/ go-libp2p#2827
   +0

[achingbrain]

There is good news when all of the above PRs are applied:

[christroutner]

I am trying to use webRTC in an exclusive node.js environment (no browser nodes). I created issue #2702 and wanted to link to it here, as it might be relevant to this discussion.