- From: bdrtc via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 11:43:32 +0000
- To: public-webrtc-logs@w3.org
> The right place to filter ipv6 candidates is at the receiving end - the sender can't know if ipv6 candidates might be useful - the recipient can. > > @bdrtc do you have any timings on the delay caused by creating ipv6 candidates ? when we use full ice case, offer sdp will wait for full ice gather end then send out , disable not used NICs/Transport type/Address type will speed up the candidate collection time. i ever test an old sip server support webrtc, but it dose not support ipv6 candidate exist in sdp which cause sdp negotiation failed, and resolved it by disabled ipv6 candidate collection via googIPv6, but it's removed after 108, from the descrition of remove resean is its private opt. then, open it here for discussion, maybe other users have same requirment. -- GitHub Notification of comment by bdrtc Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/138#issuecomment-1377131549 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 11:43:34 UTC