IETF Logo Mail Archive

[multipathtcp] API: which address to use

Pasi Sarolahti <pasi.sarolahti@iki.fi> Mon, 09 November 2009 10:48 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 E923428C1E9 for <multipathtcp@core3.amsl.com>; Mon, 9 Nov 2009 02:48:57 -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 1QcrHCPjmuMN for <multipathtcp@core3.amsl.com>; Mon, 9 Nov 2009 02:48:57 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 1893E28C18F for <multipathtcp@ietf.org>; Mon, 9 Nov 2009 02:48:57 -0800 (PST)
Received: from host-24-222.meeting.ietf.org (host-24-222.meeting.ietf.org [133.93.24.222]) by argo.otaverkko.fi (Postfix) with ESMTP id A3A7725ED1C for <multipathtcp@ietf.org>; Mon, 9 Nov 2009 12:49:21 +0200 (EET)
Message-Id: <E9EE0C1A-C9D3-4EBC-97FD-E1B1628CD2E7@iki.fi>
From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
To: multipathtcp@ietf.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 09 Nov 2009 19:49:16 +0900
X-Mailer: Apple Mail (2.936)
Subject: [multipathtcp] API: which address to use
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: Mon, 09 Nov 2009 10:48:58 -0000

Hi,

This problem was just discussed in the meeting. Could one possible  
solution to the getsockname semantics problem be to use a separate  
address family for multipath connections? It could be similarly  
structured to the traditional AF, but from the different AF the app  
would know the semantics are different.

Separate AF also explicitly tells that multipath TCP is enabled.

This would not be fully backwards compatible with legacy apps, though,  
which I guess was one of the design goals.

- Pasi

v2.23.0 | Report a Bug | By Email