Re: [multipathtcp] The point about multiple listening sockets at theclient side

Hi Yuri,

The client (in terms of software) does not need to open listening
sockets in this case. But the MPTCP stack itself will be listening on
all interfaces for potential incoming subflows from the server, which
when initiated are joined to the existing connection. The application
does not need to do anything for this to happen (but if an extended API
were in use it could, for example, have callbacks to be informed).

Regards,
Alan

> -----Original Message-----
> From: multipathtcp-bounces@ietf.org
[mailto:multipathtcp-bounces@ietf.org] On
> Behalf Of Yuri Ismailov
> Sent: 10 November 2009 00:50
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] The point about multiple listening sockets at
> theclient side
> 
> Hi all,
> I've got a request to make this point on the list. It might be just
the
> lack of my understanding and there is no any issue around that.
> The simple scenario below:
> A client with let's say 3 interfaces connects to a server through one
of
> them for http download.
> Server decides to use all three interfaces at the client side.
> My question was if the client should open listening sockets for
> accepting server initiated connections over other interfaces?
> 
> Regards
> Yuri
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp