Re: [multipathtcp] [mif] The point about multiple listening sockets at the client side

Lars Eggert <lars.eggert@nokia.com> Tue, 10 November 2009 00:43 UTC

Return-Path: <lars.eggert@nokia.com>
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 4B16D3A6908; Mon, 9 Nov 2009 16:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599]
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 AGKTUIsxkbxA; Mon, 9 Nov 2009 16:43:03 -0800 (PST)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 396243A68B3; Mon, 9 Nov 2009 16:43:03 -0800 (PST)
Received: from host-24-27.meeting.ietf.org (host-24-27.meeting.ietf.org [133.93.24.27]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id nAA0hHjv098744 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 10 Nov 2009 02:43:21 +0200 (EET) (envelope-from lars.eggert@nokia.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/signed; boundary="Apple-Mail-9-333722617"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4AF8945F.2010105@ismailov.eu>
Date: Tue, 10 Nov 2009 09:43:16 +0900
Message-Id: <FE3943E7-B4F9-428C-B0F4-4B85F667C3FC@nokia.com>
References: <4AF8945F.2010105@ismailov.eu>
To: Yuri Ismailov <yuri@ismailov.eu>
X-Mailer: Apple Mail (2.1077)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [195.148.124.194]); Tue, 10 Nov 2009 02:43:23 +0200 (EET)
Cc: "multipathtcp@ietf.org Mailing List" <multipathtcp@ietf.org>, mif@ietf.org
Subject: Re: [multipathtcp] [mif] The point about multiple listening sockets at the client 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 00:43:04 -0000

Hi,

I think you made this comment at the mike in MPTCP, so you probably want to follow up on this on the MPTCP list.

Lars

On 2009-11-10, at 7:14, Yuri Ismailov wrote:

> 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 about 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
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif