On 2010-04-14 06:56, Parav Pandit wrote:
So in case of TCP, client which tries to connect to the server, should provide its link-local source address during socket(), bind() calls.
No. On the client side there should be no bind() call, and the socket() call is unaffected since it doesn't take any address parameter. In the connect() call, for the struct sockaddr parameter, the sin6_addr member will contain the server's link-local address and the sin6_scope_id member will contain the scope id of the client's interface on which the server can be reached.
Based on that IPv6 stack will figure out the out-going interface.
There is no need for the stack to "figure out" the outgoing interface since the application tells it plainly in the sin6_scope_id parameter.
Simon -- NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca vCard 4.0 --> http://www.vcarddav.org -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
