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

Scott Brim <scott.brim@gmail.com> Thu, 12 November 2009 01:46 UTC

Return-Path: <scott.brim@gmail.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 0935B28C18E for <multipathtcp@core3.amsl.com>; Wed, 11 Nov 2009 17:46:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 LUbpoWa8VNHg for <multipathtcp@core3.amsl.com>; Wed, 11 Nov 2009 17:46:19 -0800 (PST)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id B33CB28C17B for <multipathtcp@ietf.org>; Wed, 11 Nov 2009 17:46:18 -0800 (PST)
Received: by yxe30 with SMTP id 30so1826811yxe.29 for <multipathtcp@ietf.org>; Wed, 11 Nov 2009 17:46:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=6+MuFAAz1/zaaO82uDykLqrIX4PHoTTMlxVdYls+xgg=; b=iwVYMKx43jMqWvNC5mLfgSBa0iaxYXoZgqlIpXGhV3Y+L8Q8pW/UvWuN2FC4v/alsB emGcVrjmD6zTZcbyO2zTDeYQ8FJxFiAMn3QtXEf6ESXCpyF5gT8kthgssssQ2xKKndeq BE08+byk9jDsn/ntz0NP/dlm/5gixtflVk2VI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=JhkGpUOR5wRdJ6EBb/NUlRm3UsMynjhYh6O5TINNnvCr8Ah8cEFMakdpuIODQPhskv PoIGRh1tBOqX8/GKBSD0Tx8FcsFAfgFPfFRK8Q7FIt/aAMfJ6PiaJcA7vMGqgnv41a9i VEKG2+8YK+zDnYwy4DZd4Af/ylx/qwCy31xYY=
Received: by 10.150.243.5 with SMTP id q5mr4170433ybh.13.1257990402942; Wed, 11 Nov 2009 17:46:42 -0800 (PST)
Received: from host-24-56.meeting.ietf.org (host-24-56.meeting.ietf.org [133.93.24.56]) by mx.google.com with ESMTPS id 16sm10991gxk.11.2009.11.11.17.46.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Nov 2009 17:46:42 -0800 (PST)
Message-ID: <4AFB68FE.2040606@gmail.com>
Date: Thu, 12 Nov 2009 10:46:38 +0900
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Ford, Alan" <alan.ford@roke.co.uk>
References: <4AF8B8A5.4040602@ismailov.eu> <2181C5F19DD0254692452BFF3EAF1D6808D7BB53@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <2181C5F19DD0254692452BFF3EAF1D6808D7BB53@rsys005a.comm.ad.roke.co.uk>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Thu, 12 Nov 2009 01:46:20 -0000

Ford, Alan allegedly wrote on 11/10/2009 10:06 AM:
> 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, 

All or some, which can be a local config option.  In any case it's not
something the app has to be involved in.  (The app _could_ be involved.)