WebRTC Transport Implementation & Updates #999
Replies: 5 comments
-
|
@sukhman-sukh , @asmit27rai, @Winter-Soren : kindly comment down your progress, updates, or blockers/issues(if any) to ensure coordination and collaborated timely guidance on each. ccing: @seetadev , @acul71 , @AkMo3 for insighful guidance and rectifications on the same. |
Beta Was this translation helpful? Give feedback.
-
|
@acul71 Raising improvisation issues for webrtc in py-libp2p and updating it here along MajorImprovisation and Tests Needed
Test Discussions |
Beta Was this translation helpful? Give feedback.
-
|
-contains webrtc-direct and webrtc-private-to-private related issues, approach and fixes. |
Beta Was this translation helpful? Give feedback.
-
Screencasts: WebRTC (Direct & Pvt-to-Pvt) Transport in Py-libp2pThese demos showcase the examples chat demo via WebRTC transport. Demo 1Demo 2Demo 3 (Google Drive) |
Beta Was this translation helpful? Give feedback.
-
|
Blog: https://js-libp2p.hashnode.dev/webrtc-transport-in-py-libp2p
|
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion
✅ Core Transport Implementation
Contributors
@Nkovaturient
@sukhman-sukh
@asmit27rai
✅ Accomplished Tasks
WebRTC-Direct ( pvt-to-public)
Webrtc Pvt-to-Pvt
listener & Protocol registration - Refactor WebRTC Private-to-Private Listener to Match js-libp2p Pattern Nkovaturient/py-libp2p#2
Diagram
sequenceDiagram participant a as Browser A participant cr as CircuitRelayV2Peer participant b as Browser B participant stun as STUN Server b->>cr: Establish Relayed Connection (WebTransport, WebRTC) b-->>a: Shares its own relayed webrtc multiaddress (out of band) a->>b: Establishes a relayed connection to Browser 2 a-->>a: Creates RTCPeerConnection with STUN server config, init DataChannel and SDP offer a->>b: Initiates libp2p /webrtc-signaling/0.0.1 protocol stream over relayed conection and sends SDP b-->>b: Creates RTCPeerConnection with STUN server config, sets Browser1's SDP offer, and creates SDP answer b->>a: Sends SDP answer over signaling stream a-->>a: Set SDP answer with RTCPeerConnection.setRemoteDescription a->>+stun: What's my public IP and port stun->>-a: Browser A observed ip and port: 8.8.8.1:63333 b->>+stun: What's my public IP and port stun->>-b: Browser B observed ip and port: 6.6.6.1:52222 b->a: exchange ICE candidates over signalling stream pass to RTCPeerConnection.addIceCandidate() b->a: Establish direct connectionFixes and TODOs:
Transport Interop & Test Plans
Beta Was this translation helpful? Give feedback.
All reactions