- From: Mészáros Mihály via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Aug 2018 08:41:10 +0000
- To: public-webrtc-logs@w3.org
misi has just created a new issue for https://github.com/w3c/webrtc-pc: == Make possible to select TURN allocataion address familly. (to avoid IPv6 confusion) == Make possible to set TURN client the REQUESTED-ADDRESS-FAMILY attribute to avoid confusion. WebRTC implementations don't send REQUESTED-ADDRESS-FAMILY STUN/TURN attribute. https://tools.ietf.org/html/rfc6156#section-4.1.1 ``` If the REQUESTED-ADDRESS-FAMILY attribute is absent, the server MUST allocate an IPv4-relayed transport address for the TURN client. ``` This way TURN servers will allocate IPv4 address even if the Allocation request sent on IPv6 connection to the TURN server. This may cause confusion in developers, and so we should make it configurable in WebRTC API. **The proposed values of the new knob on turnserver**: - not send any REQUESTED-ADDRESS-FAMILY (Actual behavior) - Request IPv4 family - Request IPv6 family - Dual allocation IPv4 and IPv6 in one shot. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1972 using your GitHub account
Received on Monday, 27 August 2018 08:41:12 UTC