[nbs] Fwd:draft-scharf-mptcp-api-03.txt

RJ Atkinson <rja.lists@gmail.com> Wed, 20 October 2010 18:22 UTC

Return-Path: <rja.lists@gmail.com>
X-Original-To: nbs@core3.amsl.com
Delivered-To: nbs@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 3E3BE3A67EF for <nbs@core3.amsl.com>; Wed, 20 Oct 2010 11:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id EdhG3s0CX+oP for <nbs@core3.amsl.com>; Wed, 20 Oct 2010 11:22:13 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com []) by core3.amsl.com (Postfix) with ESMTP id 44A943A681F for <nbs@ietf.org>; Wed, 20 Oct 2010 11:22:13 -0700 (PDT)
Received: by qwc9 with SMTP id 9so2692921qwc.31 for <nbs@ietf.org>; Wed, 20 Oct 2010 11:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:references:to:message-id :mime-version:x-mailer; bh=Zznd6C0Mva1W7PcC/ihH+M9J8BC4VNeMhKPzPnLNAJI=; b=W41FLWcYkUa1RmuMKFLZstw/1Bd291bn9k3aRNDt9jzJ1hfclCIHqvWnzTXlXCOD61 ZJZ3Ttw09hpa7QU7qRYkMZbCG1lh5FZ9xn38neD/J8zWSOoyvwyRjkFMJof0b4GAhhYQ fWA8Y4L2Wz2NrE6eIO/wlYUoMO2/F2ErZaHSQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer; b=HGjKHyxNOK4hDy1wXeQTjMH33vW2xej9kWDsODkm+cS+Mlyfu1Vhzt7JBt8Gy7g5+E K0KFcNcLC22WUHYIxMEqaTcEcwY1XhHfMA5PMyoCHGWmrFQRwvLj/ZAm54iBOZvWrOqY OvhZjuhLRymDJUbttFkUyukFIeGYkMuUCfc6Y=
Received: by with SMTP id x12mr4770887qat.73.1287599026718; Wed, 20 Oct 2010 11:23:46 -0700 (PDT)
Received: from [] (pool-96-225-170-25.nrflva.fios.verizon.net []) by mx.google.com with ESMTPS id s34sm451785qcp.20.2010. (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 11:23:45 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Oct 2010 14:23:43 -0400
References: <20101020173002.14B683A69F4@core3.amsl.com>
To: nbs@ietf.org
Message-Id: <3EE281CA-246F-43C0-A30B-7F2926F2523F@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [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 18:22:14 -0000

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



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