- From: bdrtc via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 09:14:15 +0000
- To: public-webrtc@w3.org
bdrtc has just created a new issue for https://github.com/w3c/webrtc-extensions:
== support disable ipv6 candidate in RTCConfiguration ==
Ipv6 is enabled by default in some browsers and there are ipv6 candidates generated by default during setup peerconnection call,
but not all webrtc based system support ipv6 now, ipv6 candidates is not nessesary in this case,
What's more, ipv6 candidates in sdp may cause negotiation error when interoperation with some rtc servers which does't support ipv6 address resolution.
Disable ipv6 will reduce the time cost of candidates collection especially when multiple NICs exist.
I sugguest add an IPv6 configuration parameter like below :
`new RTCPeerConnection({}, {mandatory:{IPv6:false}});`
[chrome support this](https://chromestatus.com/feature/5184046454800384) via googIPv6 ever but remove it as it's not standard API.
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/138 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 January 2023 09:14:16 UTC