IETF Logo Mail Archive

Re: [multipathtcp] Multipath Address Family

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Wed, 25 November 2009 00:14 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
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 C93403A67C1 for <multipathtcp@core3.amsl.com>; Tue, 24 Nov 2009 16:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.229
X-Spam-Level: *
X-Spam-Status: No, score=1.229 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
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 bxRKB5HKCkC1 for <multipathtcp@core3.amsl.com>; Tue, 24 Nov 2009 16:14:22 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id F25F43A680E for <multipathtcp@ietf.org>; Tue, 24 Nov 2009 16:14:21 -0800 (PST)
Received: from localhost (cpu.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 68BD04C0D8; Wed, 25 Nov 2009 09:14:14 +0900 (JST)
Date: Wed, 25 Nov 2009 09:14:14 +0900
Message-Id: <20091125.091414.57515028.nishida@sfc.wide.ad.jp>
To: Michael.Tuexen@lurchi.franken.de
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
In-Reply-To: <C622F375-EE67-46AE-AC28-6617CFEF6D12@lurchi.franken.de>
References: <48DA092B-F3BC-432E-A199-B265DDED39DA@iki.fi> <3c3e3fca0911240434p4d95ec7an34615ae218faa4f@mail.gmail.com> <C622F375-EE67-46AE-AC28-6617CFEF6D12@lurchi.franken.de>
X-Mailer: Mew version 6.2 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Multipath Address Family
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: Wed, 25 Nov 2009 00:14:22 -0000

From: Michael Tüxen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [multipathtcp] Multipath Address Family
Date: Tue, 24 Nov 2009 22:07:36 +0100
Message-ID: <C622F375-EE67-46AE-AC28-6617CFEF6D12@lurchi.franken.de>

 > just one note:
 > In SCTP we use sctp_connectx() to connect to multiple addresses.
 > Kacheong pointed a couple of years ago out that a more generic
 > connectx() would make sense to other protocols supporting multihoming
 > as well (but there were no).

Just curiosity, do you know the reason why generic connectx() doesn't exist? 
it make sense to me since the call looks independent from sctp.
Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp

v2.23.0 | Report a Bug | By Email