Re: [multipathtcp] Multipath Address Family

Pasi Sarolahti <pasi.sarolahti@iki.fi> Wed, 25 November 2009 02:51 UTC

Return-Path: <pasi.sarolahti@iki.fi>
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 AD1F928C1A8 for <multipathtcp@core3.amsl.com>; Tue, 24 Nov 2009 18:51:14 -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=[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 Bbd6Nz3R+9T3 for <multipathtcp@core3.amsl.com>; Tue, 24 Nov 2009 18:51:13 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 7E60A28C1A3 for <multipathtcp@ietf.org>; Tue, 24 Nov 2009 18:51:13 -0800 (PST)
Received: from [192.168.1.66] (adsl-99-169-80-11.dsl.pltn13.sbcglobal.net [99.169.80.11]) by argo.otaverkko.fi (Postfix) with ESMTP id 294F625ED06; Wed, 25 Nov 2009 04:51:07 +0200 (EET)
Message-Id: <94FFE70B-3CF6-47A7-B29D-40342135E08E@iki.fi>
From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
To: William Herrin <bill@herrin.us>
In-Reply-To: <809D0BC9-83EC-4E42-85DC-BCAB2905F403@iki.fi>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 24 Nov 2009 18:51:04 -0800
References: <E9EE0C1A-C9D3-4EBC-97FD-E1B1628CD2E7@iki.fi> <3c3e3fca0911090542h54e45784qbdbf1f338a4c3e90@mail.gmail.com> <E03D46E1-51EA-4273-A8A7-4F37F88B2E92@iki.fi> <20091123.092214.140617438.nishida@sfc.wide.ad.jp> <48DA092B-F3BC-432E-A199-B265DDED39DA@iki.fi> <3c3e3fca0911240434p4d95ec7an34615ae218faa4f@mail.gmail.com> <809D0BC9-83EC-4E42-85DC-BCAB2905F403@iki.fi>
X-Mailer: Apple Mail (2.936)
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 02:51:14 -0000

On Nov 24, 2009, at 5:52 PM, Pasi Sarolahti wrote:

>> Stupid question time: what makes redefining sockaddr superior to an
>> extended API call that supplants connect() and accepts an array of
>> sockaddrs?
>
> Another question: is it better to have a compile-time error (or  
> segmentation fault) or run-time error code, if application was built  
> with multi-address support, but system was not?

Uh.. forget what I said about compile-time errors... But I would think  
not changing the API would allow for more elegant error handling when  
multi-address apps are run on old systems that do not support the  
feature.

- Pasi