W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2018

Re: WebRTC don't send TURN REQUESTED-ADDRESS-FAMILY attribute => Even if TURN allocation sent on IPv6, then an IPv4 address will be allocated.

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 27 Aug 2018 09:38:58 +0200
To: public-webrtc@w3.org
Message-ID: <e31894c9-b897-51f0-bced-2256f2843c9c@alvestrand.no>
Den 22. aug. 2018 16:00, skrev Mészáros Mihály:
> Hi,
> 
> According my experiences WebRTC implementations don't send any
> 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 is completely reasonable behavior when the destination is on an
IPv4 network and the requestor is on an IPv6-only network; it's a way to
do v6/v4 interworking.

> I think this may cause confusion in developers and so we should make it
> configurable in WebRTC API.
> Do you aware of this?
> What is your opinion?

I agree that it should be possible to request the TURN server to
allocate IPv6 addresses, and since this is new behavior, it needs a
control knob.

> 
> Thanks,
> Misi
> 
> 
> 
Received on Monday, 27 August 2018 07:39:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:43 UTC