Re: [nbs] Fwd:draft-scharf-mptcp-api-03.txt
"SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com> Wed, 20 October 2010 20:17 UTC
Return-Path: <Michael.Scharf@alcatel-lucent.com>
X-Original-To: nbs@core3.amsl.com
Delivered-To: nbs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 19A093A68F6 for <nbs@core3.amsl.com>;
Wed, 20 Oct 2010 13:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level:
X-Spam-Status: No, score=-6.126 tagged_above=-999 required=5 tests=[AWL=0.122,
BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 KpnR5hTp30+o for
<nbs@core3.amsl.com>; Wed, 20 Oct 2010 13:17:10 -0700 (PDT)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96])
by core3.amsl.com (Postfix) with ESMTP id 3A1EB3A6927 for <nbs@ietf.org>;
Wed, 20 Oct 2010 13:17:00 -0700 (PDT)
Received: from SLFSNX.rcs.alcatel-research.de
(slfsn1.rcs.de.alcatel-lucent.com [149.204.60.98]) by mailrelay2.alcatel.de
(8.14.3/8.14.3/ICT) with ESMTP id o9KKIWnl006859;
Wed, 20 Oct 2010 22:18:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CB7093.F6FFDAF4"
Date: Wed, 20 Oct 2010 22:15:47 +0200
Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C026F6258@SLFSNX.rcs.alcatel-research.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nbs] Fwd:draft-scharf-mptcp-api-03.txt
Thread-Index: Actwg/S8CBki0qBrTTqI5ezM1BqhBAAD6Afa
References: <20101020173002.14B683A69F4@core3.amsl.com>
<3EE281CA-246F-43C0-A30B-7F2926F2523F@gmail.com>
From: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
To: "RJ Atkinson" <rja.lists@gmail.com>, <nbs@ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 149.204.45.73
Subject: Re: [nbs] Fwd:draft-scharf-mptcp-api-03.txt
X-BeenThere: nbs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Name based sockets discussion list <nbs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nbs>,
<mailto:nbs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nbs>
List-Post: <mailto:nbs@ietf.org>
List-Help: <mailto:nbs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nbs>,
<mailto:nbs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:17:12 -0000
Of course, this draft is work in progress. Please let us know if you have any specific suggestions or comments. Thanks Michael -----Ursprüngliche Nachricht----- Von: nbs-bounces@ietf.org im Auftrag von RJ Atkinson Gesendet: Mi 20.10.2010 20:23 An: nbs@ietf.org Betreff: [nbs] Fwd:draft-scharf-mptcp-api-03.txt This new I-D seems like it might be relevant to this list. Given the likely near-term deployment of MP/TCP, it would seem sensible that any API work not preclude interworking of applications using any new abstracted API with MP/TCP underneath. Yours, Ran Begin forwarded message: > From: Internet-Drafts@ietf.org > Date: 20 October 2010 13:30:01 EDT > To: i-d-announce@ietf.org > Subject: I-D Action:draft-scharf-mptcp-api-03.txt > content-type: Multipart/Mixed; Boundary="NextPart" > mime-version: 1.0 > message-id: <20101020173002.14B683A69F4@core3.amsl.com> > x-beenthere: i-d-announce@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > Title : MPTCP Application Interface Considerations > Author(s) : M. Scharf, A. Ford > Filename : draft-scharf-mptcp-api-03.txt > Pages : 25 > Date : 2010-10-20 > > Multipath TCP (MPTCP) adds the capability of using multiple paths to > a regular TCP session. Even though it is designed to be totally > backward compatible to applications, the data transport differs > compared to regular TCP, and there are several additional degrees of > freedom that applications may wish to exploit. This document > summarizes the impact that MPTCP may have on applications, such as > changes in performance. Furthermore, it discusses compatibility > issues of MPTCP in combination with non-MPTCP-aware applications. > Finally, the document describes a basic application interface for > MPTCP-aware applications that provides access to multipath address > information and a level of control equivalent to regular TCP. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-scharf-mptcp-api-03.txt _______________________________________________ nbs mailing list nbs@ietf.org https://www.ietf.org/mailman/listinfo/nbs
- [nbs] Fwd:draft-scharf-mptcp-api-03.txt RJ Atkinson
- Re: [nbs] Fwd:draft-scharf-mptcp-api-03.txt SCHARF, Michael