From f7e746e75f1aa9fd43c0e6ccf2f6512ea7f8de29 Mon Sep 17 00:00:00 2001 From: Alex Potsides Date: Tue, 14 Mar 2023 20:51:38 +0100 Subject: [PATCH] fix: Rename webrtc-w3c to webrtc and webrtc to webrtc-direct Following on from https://github.com/multiformats/multiaddr/pull/150 and an replacement for https://github.com/multiformats/multiaddr/pull/151 Renames: - `/webrtc-w3c` -> `/webrtc` - AKA browser to browser - `/webrtc` -> `/webrtc-direct` - AKA browser to server Discussion: - This option was mentioned in #150 and seemed to have a reasonable amount of support but seemed to get lost amongst the other options - The differences in the protocols is mentioned in the table comments --- protocols.csv | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protocols.csv b/protocols.csv index 23a1522..b6ca5f2 100644 --- a/protocols.csv +++ b/protocols.csv @@ -35,7 +35,7 @@ code, size, name, comment 277, 0, p2p-stardust, 275, 0, p2p-webrtc-star, 276, 0, p2p-webrtc-direct, -280, 0, webrtc, ICE-lite webrtc transport -281, 0, webrtc-w3c, webrtc transport where connection establishment is according to w3c spec +280, 0, webrtc-direct, ICE-lite webrtc transport with SDP munging during connection establishment and without use of a STUN server +281, 0, webrtc, webrtc transport where connection establishment is according to w3c spec 290, 0, p2p-circuit, 777, V, memory, in memory transport for self-dialing and testing; arbitrary