Re: [tram] IPv4 and IPv6 allocations

[Simon Perreault <[e-mail]>]

Le 2014-02-19 10:31, Mallinath Bareddy a écrit :
> Hi All,
> 
>>From RFC 5766, 
>      Both the server and client keep track of a value known as the
> 
>    5-TUPLE.  At the client, the 5-tuple consists of the client's host
>    transport address, the server transport address, and the transport
>    protocol used by the client to communicate with the server.  At the
>    server, the 5-tuple value is the same except that the client's host
>    transport address is replaced by the client's server-reflexive
>    address, since that is the client's address as seen by the server.
> 
> 
> 
> I have a scenario where Turn client is sending IPv4 and a IPv6 (using REQUESTED-ADDRESS-FAMILY attribute) allocation requests from the same host transport address. The reason to send IPv6 allocation request is to connect to a IPv6 only client.
> 
> 
> 
> From above definition both allocation requests will result in same 5-tuple at the server.

No. There can be only one allocation per 5-tuple.

> How does TURN server demux requests from client, leading to the proper allocation object?

Have the client use a different source port.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca