IETF Logo Mail Archive

Re: [multipathtcp] Multipath Address Family

Christian Vogt <christian.vogt@ericsson.com> Sat, 28 November 2009 08:35 UTC

Return-Path: <christian.vogt@ericsson.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 7F89A3A6979 for <multipathtcp@core3.amsl.com>; Sat, 28 Nov 2009 00:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EBq6hD54Lb3l for <multipathtcp@core3.amsl.com>; Sat, 28 Nov 2009 00:35:24 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id C4D7E3A6974 for <multipathtcp@ietf.org>; Sat, 28 Nov 2009 00:35:23 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id nAS8ZF9c023879; Sat, 28 Nov 2009 02:35:15 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.197]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Sat, 28 Nov 2009 03:35:15 -0500
From: Christian Vogt <christian.vogt@ericsson.com>
To: Pasi Sarolahti <pasi.sarolahti@iki.fi>
Date: Sat, 28 Nov 2009 03:36:29 -0500
Thread-Topic: [multipathtcp] Multipath Address Family
Thread-Index: AcpwBbTFCF5MKLzGQ0yBf6RN7naL4Q==
Message-ID: <6DBE5C9B-1710-4E53-923A-701322A59AF4@ericsson.com>
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> <4B0BB35E.207@uclouvain.be> <6C8C1D51-70E5-4545-8661-196A94CDEA37@iki.fi>
In-Reply-To: <6C8C1D51-70E5-4545-8661-196A94CDEA37@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Olivier.Bonaventure@uclouvain.be" <Olivier.Bonaventure@uclouvain.be>
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: Sat, 28 Nov 2009 08:35:25 -0000

On Nov 24, 2009, Pasi Sarolahti wrote:

> Another question is that even if we had an connect-by-name API, would we
> still need to be able express which address(es) are bound to the socket
> in the API?

Yes.  Whereas the average application using name-based sockets would not
need any information about IP addresses, special applications may.  Hence
even a name-based sockets interface will have to provide hooks through 
which IP address information can be obtained.

- Christian

v2.23.0 | Report a Bug | By Email