From 50db89f3a71a87b096b0994a43a2dce0d251aeec Mon Sep 17 00:00:00 2001 From: Doug A Date: Mon, 14 Aug 2023 13:10:25 -0300 Subject: [PATCH] docs(webrtc): improve `negotiated` documentation (#567) --- webrtc/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/webrtc/README.md b/webrtc/README.md index a44d46495..50011237e 100644 --- a/webrtc/README.md +++ b/webrtc/README.md @@ -132,8 +132,10 @@ real-world experiments. `RTCDataChannel`s are negotiated in-band by the WebRTC user agent (e.g. Firefox, Pion, ...). In other words libp2p WebRTC implementations MUST NOT change the -default value `negotiated: false` when creating a `RTCDataChannel` via -`RTCPeerConnection.createDataChannel`. +default value `negotiated: false` when creating a standard libp2p stream +of type `RTCDataChannel` via `RTCPeerConnection.createDataChannel`. +Setting `negotiated: true` is reserved only for creating Noise handshake channels +under certain protocol conditions. The WebRTC user agent (i.e. not the application) decides on the `RTCDataChannel` ID based on the local node's connection role. For the interested reader see