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

"Ford, Alan" <alan.ford@roke.co.uk> Tue, 10 November 2009 01:06 UTC

Return-Path: <alan.ford@roke.co.uk>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D6693A69F5 for <multipathtcp@core3.amsl.com>; Mon, 9 Nov 2009 17:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.478
X-Spam-Level:
X-Spam-Status: No, score=-3.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqCVSSUu4-5G for <multipathtcp@core3.amsl.com>; Mon, 9 Nov 2009 17:06:05 -0800 (PST)
Received: from rsys002x.roke.co.uk (rsys002x.roke.co.uk [193.118.201.109]) by core3.amsl.com (Postfix) with ESMTP id 4A1783A69F2 for <multipathtcp@ietf.org>; Mon, 9 Nov 2009 17:06:04 -0800 (PST)
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id nAA16Oo3029342; Tue, 10 Nov 2009 01:06:24 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Nov 2009 01:06:32 -0000
Message-ID: <2181C5F19DD0254692452BFF3EAF1D6808D7BB53@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <4AF8B8A5.4040602@ismailov.eu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [multipathtcp] The point about multiple listening sockets at theclient side
Thread-Index: Acphn8m32o0zihtfT7KRtvMq0jbVfQAAcq2w
References: <4AF8B8A5.4040602@ismailov.eu>
From: "Ford, Alan" <alan.ford@roke.co.uk>
To: "Yuri Ismailov" <yuri@ismailov.eu>
X-roke-co-uk-MailScanner-ID: nAA16Oo3029342
X-roke-co-uk-MailScanner: Found to be clean
X-roke-co-uk-MailScanner-SpamCheck:
X-roke-co-uk-MailScanner-From: alan.ford@roke.co.uk
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] The point about multiple listening sockets at theclient side
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 01:06:06 -0000

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